Is the fix to usermod -s /sbin/nologin for each of these?
ebuild log for sys-apps/baselayout-2.0.1 on evolone.org
WARN: postinst
The following users have non-existent shells!
apache - /usr/sbin/nologin
cron - /usr/sbin/nologin
ldap - /usr/sbin/nologin
postfix - /usr/sbin/nologin
sshd - /usr/sbin/nologin
--
|\ /| | | ~ ~
| \/ | |---| `|` ?
| |ichael | |iggins \^ /
michael.higgins[at]evolone[dot]org
Do not make any changes, this is correct. System users should not have a
shell, as the account is never used to log in (not the same thing as dropping
privileges to the UID of the account).
This is a prime example of a daft ebuild. The ebuild should have checked that
a) the account does not have a shell and
b) the account uid falls in the range of system accounts as per login.defs and
c) therefore issued no postinst
You should file a bug.
--
alan dot mckinnon at gmail dot com
> Am Dienstag 30 Juni 2009 19:54:23 schrieb Michael Higgins:
>
> > Can anyone speculate as to why this error?
>
> Because it's /sbin/nologin.
Indeed.
>
> > Is the fix to usermod -s /sbin/nologin for each of these?
>
> Yes. Or vipw.
Very useful tool I never knew about. Thanks.
It gets more interesting, since viewing with that tool, the passwd file shows all the shells look right, pointing to /sbin/nologin. So, where did the incorrect values come from, I wonder?
I'll file a bug against the ebuild.
Cheers,