pwck: warnings and "no changes" on clean files, nothing after problems
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 54/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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).
- Dominant language
- Rust
- Stars
- 17
- Forks
- 10
- Avg merge
- 18h 30m
- Merged PRs (30d)
- 24
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uutils/shadow
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
usermod: -u and -g exit 0 on a symlinked home, GNU exits 12Possibly taken @pierre-warnier claimed this 1 day ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
usermod: -m/--move-home is not implementedPossibly taken @jayhemnani9910 claimed this 3 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Dependency DashboardOpen
Difficulty 3/5 1-2 days Newbie friendliness 20/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
status:untriaged
Difficulty 1/5 Under an hour Newbie friendliness 72/100
midnightntwrk/midnight-zk#592 ·
Maintainers usually reply within 3 days
-
QuartoHub: have the Document name before the filename in the browser tabPossibly taken @cscheid claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
quarto-dev/q2#930 · 1 comment ·
Maintainers usually reply within 1 day
-
muse P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
HerringtonDarkholme/hd-lang#923 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day