Mark Post wrote:
syslogd 13827 root 23w REG 94,1 91442612 29065
/dev/tty7
That looks like your problem. The "REG" says that it is a "regular file" when it should
be "CHR." What distribution is this? I know that syslogd isn't a userid shipped with SLES9 or
SLES10.
Err..
1st output field of 'lsof' isn't a userid.. it's rather looks like the
basename of the exec()'d image for the process.. (image is 'syslogd',
the pid is 13827, the user is 'root' - which I am sure *does* ship with
SLES9/10 <g>, the file descriptor for that process is 23, it is opened
in write mode, it's a REGular file on block device 94,1 - has a size of
91442612, has inode number 29065 on that fs and is named /dev/tty7).
However, I agree about "REG" being wrong here.. apparently, it seems the
syslogd.conf contains entry from an intel based system (or at least one
which has virtual consoles). On s390, I would suggest exmining the
/etc/syslogd.conf file to make sure it doesn't contain entries that are
specific to an implementation.
--Ivan
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
