On 09/12/12 19:44, Sverre Froyen wrote: [---] > Turns out the issue was "cap_mkdb /etc/login.conf" command. If the file > /etc/login.conf.db exists, cap_mkdb reads that file (ignoring > /etc/login.conf) > and generates a new /etc/login.conf.db from the old /etc/login.conf.db. Seems > to me this is counter intuitive, if not a bug. If I remove /etc/login.conf.db > before running cap_mkdb, everything works as expected. I'm sure I've seen this before. Ah, yes: http://gnats.netbsd.org/41660 If I recall correctly, someone went through the ~same process as you before they filed that PR, and I can't recall anyone making any argument against the "it's a bug" claim. -- Kind regards, Jan Danielsson
Attachment:
signature.asc
Description: OpenPGP digital signature