Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

pwck: warnings and "no changes" on clean files, nothing after problems

未关闭
#364 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@jayhemnani9910 已经在做这个了。

开始于 2026年10月27日。

  • #366 来自 @jayhemnani9910 —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
54/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
rust
领域
cli

调研方向

Start at the pwck command entry point and trace the checks that emit ID-range warnings and the logic that prints “no changes”; the issue does not name source files or tests. Compare pwck -r on clean files and files with a problem against the GNU behavior shown here. Done means clean files produce no warning or “no changes” line, while problematic files report the problem and print “no changes” to stdout, including with -q.

由索引模型根据 Issue 内容生成。

描述

On a stock Ubuntu 26.04 /etc where GNU pwck 4.17.4 prints nothing and exits 0, pwck -r prints:

pwck: warning: user 'sync': GID 65534 is outside the normal range (> 60000)
pwck: warning: user '_apt': GID 65534 is outside the normal range (> 60000)
pwck: warning: user 'nobody': UID 65534 is outside the normal range (> 60000)
pwck: warning: user 'nobody': GID 65534 is outside the normal range (> 60000)
pwck: no changes

65534 is nobody/nogroup on Debian and Ubuntu, and pwck(8) lists no ID range check; GNU pwck warns about none of these (also not for a user with UID 70000).

The "no changes" line is the other way round from GNU: GNU prints pwck: no changes on stdout after it has reported a problem (also with -q) and nothing on clean files. Here it goes to stderr on clean files, and is missing after problems:

# echo 'ghost:x:3000:3000::/:/bin/sh' >> /etc/passwd
# pwck -r          GNU: ... "add user 'ghost' in /etc/shadow? No" / "pwck: no changes", exit 2
                   here: the problems, no "no changes", exit 2

Checked on main 7a84527 in ubuntu:26.04 (GNU passwd 1:4.17.4-2ubuntu3).

主要语言
Rust
星标
17
派生
10
平均合并
19 小时 18 分钟
30 天内合并 PR
23

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

uutils/shadow 的其他 Issue

查看 uutils/shadow 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。