Bruno> I manage about 30 SGI machines. The OS varies from 4.0.5, 5.2
Bruno> and some machines under 5.3.
Bruno> The machine that is are primary "syslogd" server runs
Bruno> under 5.3 and syslogd is running. All our other scripts
Bruno> reports to that machines.
Bruno> My problem right now, is that when I try to connect to this
Bruno> machine, using port 514 (stardard syslog port in /etc/services) and
Bruno> specifying the file /var/adm/SYSLOG and connection to the server, I
Bruno> always get a message that tkined cannot connect using port 18XX.
Bruno> The XX are actually incrementing each time I try to connect to
Bruno> this machine. Even changes the defaults in the script itself for the
Bruno> defaults but still tries to connect to an ever growing port number.
The 514/udp syslog port is used to write messages to a syslog
daemon. There is no standard way to read messages received by a
syslogd daemon via the network.
If you want to have this additional feature, you will have to install
a replacement for your syslogd which listens on a TCP port (usually
18XX) for syslog clients.
An implementation is available from ftp.ibr.cs.tu-bs.de in
/pub/local/tkined/contrib/syslogd+tcp-0.4.tar.gz
Juergen
-- Juergen Schoenwaelder schoenw@cs.utwente.nl http://www.cs.utwente.nl/~schoenw Computer Science Department, University of Twente, (Fax: +31-53-489-3247) P.O. Box 217, NL-7500 AE Enschede, The Netherlands. (Tel. +31-53-489-3678)