Yesterday I was attempting the reconfiguration that the 'chrome' browser
recommends in order for using it effectively in OpenBSD 4.9. Namely, I
attempted to follow the following instructions:
-=-=-=-=-=-
You should make the following changes for your login class in
/etc/login.conf
(you will need to logout and login for these to take effect).
- increase datasize-max to at least 716800.
- increase openfiles-max to at least 400.
Do you want to run Chromium anyway?
(If you don't increase these limits, Chromium might fail to work properly.)
-=-=-=-=-=-
After the changes, the following is what I ended up with in my
/etc/login.conf:
-=-=-=-=-=-
contract:~$ cat /etc/login.conf
#datasize-max=768M:\
datasize-max=716800:
:datasize-cur=512M:\
:maxproc-max=256:\
:maxproc-cur=128:\
:openfiles-cur=128:\
:stacksize-cur=4M:\
:localcipher=blowfish,6:\
:ypcipher=old:\
:tc=auth-defaults:\
:tc=auth-ftp-defaults:\
:openfiles-max=400:
#
# Settings used by /etc/rc and root
# This must be set properly for daemons started as root by inetd as well.
# Be sure reset these values back to system defaults in the default class!
#
daemon:\
:ignorenologin:\
:datasize=infinity:\
:maxproc=infinity:\
:openfiles-cur=128:\
:stacksize-cur=8M:\
:localcipher=blowfish,8:\
:tc=default:
#
# Staff have fewer restrictions and can login even when nologins are set.
#
staff:\
:datasize-cur=512M:\
:datasize-max=infinity:\
:maxproc-max=512:\
:maxproc-cur=128:\
:ignorenologin:\
:requirehome@:\
:tc=default:
#
# Authpf accounts get a special motd and shell
#
authpf:\
:welcome=/etc/motd.authpf:\
:shell=/usr/sbin/authpf:\
:tc=default:
-=-=-=-=-=-
After making the preceding changes, I attempted to log in on a console tty
and ended up with a 'failure to retrieve default class' at the login: prompt
immediately after entering my login name. Logins by ssh, as well, are not
working, although it fails through a different set of steps; mainly,
public-key authentication fails, and then the password is not recognized at
the failthrough password prompt.
As I am sure you can understand, I would like to be able to login to my
machine, especially before there is a power outage or some other cause that
forces me to reboot at which point I can only assume I will be locked out of
the machine and that it will be even more difficult to recover from. I am
also eager to have 'chrome' working correctly, but I assure you that is a
distant second at this point.
Can anybody help me with some steps that can return login functionality to
this machine and possibly even help me make the configuration changes that
chrome was talking about in a manner that doesn't make my machine impossible
to log in to?
Thank you very much in advance. Also, the last few thousand lines of my
/var/log/messages contains the following if this is helpful at all:
-=-=-=-=-=-
Aug 19 00:31:21 contract inetd[21573]: /usr/libexec/comsat: exit status 1
Aug 19 00:31:21 contract inetd[13153]: daemon: couldn't resolve 'tc'
Aug 19 00:31:21 contract inetd[13153]: comsat/udp: setusercontext: No such
file or directory
Aug 19 00:31:21 contract inetd[21573]: /usr/libexec/comsat: exit status 1
Aug 19 00:31:21 contract inetd[22957]: daemon: couldn't resolve 'tc'
Aug 19 00:31:21 contract inetd[22957]: comsat/udp: setusercontext: No such
file or directory
Aug 19 00:31:21 contract inetd[21573]: /usr/libexec/comsat: exit status 1
Aug 19 00:31:21 contract inetd[4550]: daemon: couldn't resolve 'tc'
Aug 19 00:31:21 contract inetd[4550]: comsat/udp: setusercontext: No such
file or directory
Aug 19 00:31:21 contract inetd[21573]: /usr/libexec/comsat: exit status 1
Aug 19 00:31:21 contract inetd[21573]: comsat/udp server failing (looping),
service terminated
Aug 19 07:32:56 contract sshd: staff: couldn't resolve 'tc'
Aug 19 07:32:56 contract sshd: staff: couldn't resolve 'tc'
Aug 19 07:32:59 contract sshd: default: unknown class
Aug 19 07:33:19 contract last message repeated 2 times
-=-=-=-=-=-
Thanks again.
-Damon Getsman
P.S. I noted the lack of a \ at the end of the first line of my
/etc/login.conf after typing this message. Unable to sudo, as well, I
switched to a console that was already sudo su'ed, and added that
backslash. I am still receiving the same errors.
