[Pkg-shadow-devel] Bug#374525: Bug#366546: Mail delivery failed:
returning message to sender
cperciva at freebsd.org
Wed Jul 5 13:31:08 UTC 2006
Christian Perrier wrote:
> As a first reaction and as one of the shadow maintainer, I'm now
> inclined to agree with the choice of the FreeBSD team here.
> The rationale is clear...
> I'd like to hear the one from OpenBSD to put nologin in /sbin
> though.. they might have a different definition of what goes in /sbin
FWIW, nologin was in /sbin in BSD 4.4; this is almost certainly why
OpenBSD still has /sbin/nologin.
I moved FreeBSD's nologin to /usr/sbin two years ago, because
1. nologin needs to be statically linked to avoid linker environment
2. logging attempts to log in to a nologinned account requires that
syslog code be pulled in (which significantly increases the size of
a statically linked binary),
3. we like to keep the root filesystem small, and
4. Since nologin is intended for use in multiuser mode, there's no
reason for it to be on the root filesystem -- in single user mode,
users who aren't supposed to be allowed to login will never get to
the point of running a shell (nologin or otherwise).
In short, under the BSD hierarchy rules, nologin should be in /usr/sbin;
any systems behaving otherwise are doing so for historical reasons only.
More information about the freebsd-arch