Path: utzoo!attcan!uunet!bu.edu!att!rutgers!cunixf.cc.columbia.edu!cs.columbia.edu!abrams From: abrams@cs.columbia.edu (Steven Abrams) Newsgroups: comp.sys.hp Subject: syslogd on client 9000s300 Message-ID: Date: 12 Nov 90 17:55:16 GMT Sender: news@cs.columbia.edu (The Daily News) Distribution: na Organization: Columbia University Department of Computer Science Lines: 33 I hoped someone "out there" might be able to help. I just inherited the management of a cluster of diskless 320's being served by a 350, running HP-UX 7.0. The problem is that the syslogd's on the clients are continuously spitting out informative messages of the form, "Nov 12 12:50:44 chamonix syslogd: select: Invalid argument" Note, chamonix is the name of the diskless node and select is the name of the server. This, of course, may be a coincedence and the message could be refering to the select system call. The syslog.conf file looks like: *.info /usr/adm/syslog *.alert /dev/console *.alert root *.emerg * I temporarily solved the problem by sending *.info messages to /dev/null, but this chewed up tons of CPU time. I have shut down the syslogd on the clients, but would prefer to keep it running if possible Anyone have any clues? Thanks, ~~~Steve -- /************************************************* * *Steven Abrams abrams@cs.columbia.edu * **************************************************/ #include #include