Hi folks,
My SCO Openserver 5.0.5 seems hang on telnet and ping very frequently but I can't trace what the error message come out in the /var/adm/syslog file. When I looked at the /etc/syslog.conf, it only contains one line:
[tt]*.debug /usr/adm/syslog[/tt]
I thought it is not enough to trace errors so I modified it into:
[tt]*.debug;*.notice;*.info /usr/adm/syslog
*.alert;*.crit;*.err /usr/adm/errlog
*.warning /usr/adm/warnlog[/tt]
Then I killed syslogd and run it again and even reboot the box after. But the syslog.conf file looks like not working at all, no new log file created in /var/adm directory (/usr/adm is a soft link to /var/adm) after the telnet hang problem happened again. Should I touch these two new log files before? Does SCO Unix syslog.conf work the same as SUN Solaris one?
My SCO Openserver 5.0.5 seems hang on telnet and ping very frequently but I can't trace what the error message come out in the /var/adm/syslog file. When I looked at the /etc/syslog.conf, it only contains one line:
[tt]*.debug /usr/adm/syslog[/tt]
I thought it is not enough to trace errors so I modified it into:
[tt]*.debug;*.notice;*.info /usr/adm/syslog
*.alert;*.crit;*.err /usr/adm/errlog
*.warning /usr/adm/warnlog[/tt]
Then I killed syslogd and run it again and even reboot the box after. But the syslog.conf file looks like not working at all, no new log file created in /var/adm directory (/usr/adm is a soft link to /var/adm) after the telnet hang problem happened again. Should I touch these two new log files before? Does SCO Unix syslog.conf work the same as SUN Solaris one?