On Tue, May 15, 2007 at 04:36:46PM +0200, Ernest Sales wrote: > On Tuesday, May 15, 2007 1:18 PM, Christopher Illies wrote: > > > On Tue, May 15, 2007 at 12:27:10PM +0200, Ernest Sales wrote: > > > On Tue, 15 May 2007 09:14:42 +0200, Christopher Illies wrote: > > > > > > > The locale settings in my .login_conf are ignored: > > > > > > > > ; cat .login_conf > > > > # $FreeBSD: src/share/skel/dot.login_conf,v 1.3 > > 2001/06/10 17:08:53 > > > > # ache Exp $ > > > > # > > > > # see login.conf(5) > > > > # > > > > me:\ > > > > :charset=UTF-8:\ > > > > :lang=en_US.UTF-8: > > > > > > > > ; env | egrep -i 'lang|charset' > > > > LANG=en_US.ISO8859-1 > > > > MM_CHARSET=iso-8859-1 > > > > ; ls -l .login_conf > > > > -rw-r--r-- 1 chris chris 146 May 15 08:26 .login_conf > > > > ; uname -r > > > > 6.2-STABLE [...] > > > Never had to deal with ~/.login_conf files, but what > > cap_mkdb manpage seems > > > to say > > > is that you have to concatenate all sources in one run, i.e. > > > > > > cap_mkdb /etc/login.conf /home/user1/.login.conf > > /home/user2/.login.conf ... > > > > > > HTH > > > > > > Ernest > > > > Thanks, unfortunately no success. > > > > When I concatenate all ~/login_conf files with /etc/login.conf I get > > the following warning message: > > cap_mkdb: ignored duplicate: me > > So I was mistaken. Try compiling just your ~/login_conf, make sure a > ~/login_conf.db file appears. > > Ernest
Thanks, that has worked! Before I always used cap_mkdb /etc/login.conf plus all the user's $HOME/.login_conf, but just using it on my ~/.login_conf did the trick. A ~/.login_conf.db file has appeared. I feel a bit silly for not having come up with it myself. I guess what confused me was that on another user's account the cap_mkdb compiling wasn't neccessary, but I don't need to understand that now that it works for me. Thanks again. Christopher _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"