Date: Tue, 06 Jul 1999 08:06:26 +0200 From: Sheldon Hearn <sheldonh@uunet.co.za> To: Nik Clayton <nik@nothing-going-on.demon.co.uk> Cc: hackers@freebsd.org Subject: Re: docs/12377: doc patch for login_cap. Message-ID: <93215.931241186@axl.noc.iafrica.com> In-Reply-To: Your message of "Mon, 05 Jul 1999 23:56:17 %2B0100." <19990705235617.T71138@catkin.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 05 Jul 1999 23:56:17 +0100, Nik Clayton wrote:
> I'm unfamiliar with the ins and outs of the login_cap system. Could
> someone who is versed in it please take a look at this PR (text included)
> and let me know whether or not the suggested patch is correct.
Quite often, we receive requests to improve documentation that are born
out of a failure to read that documentation correctly. I think this PR
might be one of those cases. Have a look at the login_cap(3) manpage,
into which I suspect the submitter may not have dug deeply enough:
The functions login_getpwclass(), login_getclass() and
login_getuserclass() retrieve the applicable login class
record for the user's passwd entry or class name by calling
login_getclassbyname(). On failure, NULL is returned. The
difference between these functions is that login_getuserclass()
includes the user's overriding .login_conf that exists in the
user's home directory, login_getpwclass,() and login_getclass()
restricts loookup only to the system login class database
in /etc/login.conf. login_getpwclass() only differs from
login_getclass() in that it allows the default class for user
'root' as "root" if none has been specified in the password
database. Otherwise, if the passwd pointer is NULL, or the user
record has no login class, then the system "default" entry is
retrieved.
Regards,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?93215.931241186>