Ralph Shumaker wrote:
Carl Lowenstein wrote:
On Wed, Jun 11, 2008 at 12:49 PM, Lan Barnes <[EMAIL PROTECTED]> wrote:
On Wed, June 11, 2008 12:46 pm, Carl Lowenstein wrote:
By the way, the "locate" command is really helpful in cases like this,
if the locate database has been built on your system, normally it is
re-built around 4AM on a system that is running.
... as is tab completion. But that depends on having /sbin and /usr/sbin
in your path ... IOW, being root.
As I recall, the origin of this thread was "bash: useradd: command not
found"
which is nearly always an indication of a path problem if you haven't
misspelled the command name.
Locate(1) tends to locate things by name regardless of where they
might happen to be. Just now, as a non-privileged user, running on
Fedora 9, "locate useradd" found a number of things.
/usr/sbin/useradd as expected, but also /usr/sbin/luseradd. For
adding lusers, I suppose.
carf
lusers like carf? ;)
All joking aside, luseradd is part of the libuser package and does
different things than the useradd command which is part of the
shadow-utils package. In particular, skeleton file setup (the bare bones
of a user directory) are done with luseradd and not with useradd. See
the man pages for additional info.
Gus
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
