Date: Thu, 18 Mar 1999 14:36:29 +0200 From: Sheldon Hearn <sheldonh@iafrica.com> To: hackers@freebsd.org Subject: login_cap(3) waxing or waning? Message-ID: <81574.921760589@axl.noc.iafrica.com>
index | next in thread | raw e-mail
Hi folks, I've added the following command-line option to ftpd(8): -n If /var/run/nologin does not exist, also check for the specified file and, if it exists, display it and exit. I need this work-around because ftpd does not honour the login_cap(3) capabilities ``nologin'' and ``ignorenologin''. I would have preferred to add the following to login.conf(5): ftp:\ :nologin=/var/run/nologin.ftp:\ :tc=default: Is login_cap going to be around long enough for it to be worthwhile investing time in teaching ftpd to respect its ``nologin'' and ``ignorelogin'' capabilities? The alternative is for me to man-handle ftpd into testing for /var/run/nologin.curname, but if login_cap is going to stick around, I'd like to do this properly. As an aside, is curname (see ftpd.c:755) restricted to 10 characters instead of MAXLOGNAME for reasons instrinsic to the FTP protocol, or was it simply not updated when MAXLOGNAME was born? Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?81574.921760589>