You don't say how you updated to current. If you updated without a snapshot, it is possible you got caught up in a strange malloc change.
it is also possible that some unveil / pledge things have broken your strange usage case, for instance maybe "lo" doesn't work anymore due to changes. You can try to insert ktrace -di at a higher level to determine the failure condition. > I just updated to -current. It had been about 2-3 months since I last > updated. > I have been doing so since (about) 5.9 or so. > > Anyway, way back then, I wanted to be able to login on a local serial terminal > without entering a password (yes, I know that there may be disagreement about > the wisdom of this, but, it's what I wanted). > > So, to do this, I edited the appropriate terminal line in /etc/ttys to a > custom > entry defined in /etc/gettytab; then added an entry to /etc/gettytab, using > 'lo:' to point to a ksh script which (basically) looks at the input given to > getty, and if it contains a specific username, runs "/usr/bin/login -f root" - > if the user name entered is something different, the ksh script runs -> exec > /usr/bin/login "$@" <- which allows any other user to login with a password. > > Anyway, this has worked without an issue until today. > > After the update to current, I cannot login on the serial console. This is > true > regardless of whether I use the "specific name" or any other user name on the > system. Basically, after entering any user name at the login prompt, there > is a > delay, and then the login prompt reappears (it appears getty just restarts). > > If I return /etc/ttys to a "default" entry (with the "lo:" option removed, so > that the default /usr/bin/login is run), I can login with any username on the > system, using a password. > > I have checked the man pages for ttys, getty, gettytab, init, ksh, and login, > and can't find anything that has changed. > > I am wondering if something has changed, and, if so, what that may be? > > Thanks > Ted > >
