🚀 go-pugleaf

I am not writing in any official capacity for Concurrent so what I am
about to say should not be taken as company policy or anything, but I
am familiar with the status of syslog and I may be able to shed some
light on the situation.  Syslog was originally ported to Masscomp so
that we could run sendmail.  RTU is basically a System V kernel and
not a Berkeley kernel so it doesn't use sockets for inter process
communications or pipes.  For the sendmail case it was figured that all
sendmail users would have an ethernet so all we would have to do is
change the Unix domain sockets that sendmail uses to communicate to
syslog to internet domain sockets and everything would be fine.  Well
it worked  but sendmail was never considered to be a decent mail
transport facility and Masscomp decided to offer MMDF for it's real
product.  Sendmail was never a supported product.  With the demise of
sendmail the need for syslog dissappeared and it was removed from the
product line.  The fact that some mention of syslog remaind in the
documentation  is an unfortunate consequence probably resulting from
the fact that since sendmail was unsupported nobody owned it so nobody
cleaned up when it went away. Sorry.

If somebody really really wants syslog then they may be able to beg a
copy of the old sendmail UNSUPPORTED software kit.  Just don't bother
us if you have any problems with it.  I haven't tried it but there
shouldn't be any reason that it can't run on any release of RTU but
you will need to have the Ethernet software.  (Used to be sp-70 now
it's rt-Net-TCP/IP or something).  As usual with RTU any Unix domain
sockets must be changed to Internet domain sockets.

[ This person asked not to be identified and works for the Company...
(no, not THAT Company)....]



Articles to: concurrent@soma.bcm.tmc.edu or uunet!soma.bcm.tmc.edu!concurrent
Administrative stuff: concurrent-request@soma.bcm.tmc.edu
Stan Barber, Moderator