Hello. The hushlogin attribute doesn't work when it is added to "me" record of ~/.login_conf or to "default" record of /etc/login.conf. However, having ~/.hushlogin file does its job well. Is it a bug or am I missing something?> uname -aFreeBSD saturn 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Fri Dec 3 13:57:01 IST 2004 root@saturn:/usr/obj/usr/src/sys/MYKERNEL i386 __________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250
--- Rostislav Krasny <rosti_bsd@yahoo.com> wrote:> Hello. > > The hushlogin attribute doesn't work when it is added to "me" record of > ~/.login_conf or to "default" record of /etc/login.conf. However, having > ~/.hushlogin file does its job well. Is it a bug or am I missing > something? > > > uname -a > FreeBSD saturn 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Fri Dec 3 > 13:57:01 IST 2004 root@saturn:/usr/obj/usr/src/sys/MYKERNEL i386If I run 'cap_mkdb /etc/login.conf' after the /etc/login.conf was changed the hushlogin attribute works. But I can't find any way to make hushlogin attribute work from the ~/.login_conf. Running 'cap_mkdb ~/.login_conf' doesn't help. Is it possibly to make the hushlogin attribute work from ~/.login_conf file? P.S. IMHO the login.conf(5) manual page should say something about the /etc/login.conf.db file and its preferable usage by login(1). __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail