1832973 Members
2399 Online
110048 Solutions
New Discussion

syslog error

 
SOLVED
Go to solution
Umapathy S
Honored Contributor

syslog error

hi
I get the following errors frequenty in my syslog. What may be the fault. Any pointers, docs are welcome. Thanks in advance

Apr 29 22:11:19 hpk220 syslog: getty: cannot open "tty0p3". errno: 6 Apr 29 22:11:19 hpk220 syslog: getty: cannot open "tty0p2". errno: 6 Apr 29 22:11:32 hpk220 syslog: getty: cannot open "tty0p4". errno: 6 Apr 29 22:11:37 hpk220 syslog: getty: cannot open "tty0p5". errno: 6

cheers
Umapathy
Arise Awake and Stop NOT till the goal is Reached!
7 REPLIES 7
S.K. Chan
Honored Contributor
Solution

Re: syslog error

Check /etc/inittab file for tty0p2->5 and they might be set to "respawn", that is why you get thee messages in syslog.
Turn them off (edit the file /etc/inittab and change "respawn" to "off" for the tty entries) and run ..
# init q
and it'll stop the "un-needed" logging.

S.K. Chan
Honored Contributor

Re: syslog error

I got mine commented as such ..

#ttp1:234:respawn:/usr/sbin/getty -h tty0p1 9600
#ttp2:234:respawn:/usr/sbin/getty -h tty0p2 9600
#ttp3:234:respawn:/usr/sbin/getty -h tty0p3 9600
#ttp4:234:respawn:/usr/sbin/getty -h tty0p4 9600
#ttp5:234:respawn:/usr/sbin/getty -h tty0p5 9600
Umapathy S
Honored Contributor

Re: syslog error

thanks a lot Chan. May I know what is the reason behind this.

cheers
Umapathy S
Arise Awake and Stop NOT till the goal is Reached!
S.K. Chan
Honored Contributor

Re: syslog error

Back in 10.x time (I think even 10.20) the OS installation leaves behind these entries in /etc/inittab uncommented and naturally if respawn is enable on tty that doesn't even exist it'll generate tons of error message in syslog file. If you check on your system..

# cd /dev
# ls -lR | grep tty0

You should only see tty0p0 I think and the rest doesn't exist by default.
Umapathy S
Honored Contributor

Re: syslog error

I see those tty's causing errors are owned by root:bin and not bin:bin as other ttys. Is this a cause of error messages to be thrown?

crw--w--w- 1 bin bin 193 0x000e00 Mar 1 2000 tty0p14 crw--w--w- 1 bin bin 193 0x000f00 Mar 1 2000 tty0p15 crw--w--w- 1 root bin 193 0x000200 Mar 1 2000 tty0p2 crw--w--w- 1 root bin 193 0x000300 Mar 1 2000 tty0p3 crw--w--w- 1 root bin 193 0x000400 Mar 1 2000 tty0p4 crw--w--w- 1 root bin 193 0x000500 Mar 1 2000 tty0p5 crw--w--w- 1 bin bin 193 0x000600 Mar 1 2000 tty0p6 crw--w--w- 1 bin bin 193 0x000700 Mar 1 2000 tty0p7 crw--w--w- 1 bin bin 193 0x000800 Mar 1 2000 tty0p8

cheers
Umapathy
Arise Awake and Stop NOT till the goal is Reached!
S.K. Chan
Honored Contributor

Re: syslog error

In your case ownership doesn't matter because the permission is all set to w for owner,group and others. The getty entries that are in /etc/inittab are the ones that get thrown into the syslog.
Umapathy S
Honored Contributor

Re: syslog error

Thank you very much for your help and time Chan.

cheers
Umapathy
Arise Awake and Stop NOT till the goal is Reached!