I'm chasing down a syslogd problem on a 3.4-R box, only to discover
that I'm being bit (still!) by a PR I submitted two years ago:
<http://www.FreeBSD.org/cgi/query-pr.cgi?pr=8865>
I'm responsible for a wad of machines hanging off of a terminal server.
- I wanted syslog messages reported to the console, for revealing
critical errors.
- Due to cabling and the terminal server itself, using Big Digi
hardware, I need to have getty running off of cuaa0, not ttyd0.
Apparently, in three versions of FreeBSD, this is _still_ a problem.
Does anyone have any insight on this?
--
Brian 'you Bastard' Reichert <[EMAIL PROTECTED]>
37 Crystal Ave. #303 Daytime number: (603) 434-6842
Derry NH 03038-1713 USA Intel architecture: the left-hand path
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
