Re: Need syslog(3) functions

Article View: comp.sys.concurrent

Article #92

Back to comp.sys.concurrent Previous Next

#92

From: dale chayes
Date: Sun, 07 Apr 1991 01:06

52 lines
2840 bytes

In article, uuomar@venus.lerc.nasa.gov (Omar Syed) writes:
> 
> We are trying to compile a program that makes calls to 
> openlog(3), syslog(3) and closelog(3).  Unfortunately
> Concurrent does not support these functions which seem
> to be fairly standard on other systems. 
> 
> So has anyone written these functions for Concurrent 
> RTU 5.0B, or does anyone know another way to work around
> it.  If so your reply will be greatly appreaciated.

Well, some time ago (perhaps as long ago as RTU 4.0 or 4.1 I too had
this problem and when I could not find the functions, and could not
get syslog to work, I filed an SCR/SQR (Software Quality Report.)  It
turns out that it is one of the few that got a semi-serious answer.

The answer is "...we don't see the need for this and since we don't
support it, we won't include it any more..."  I subsequently tried to
get them to see that this really is an important part of networked
life and would they please re-consider.

At least part of the companies (the Masscomp, now Concurrent's) reason
was that these are Berkleyisms....  Well, they are, but they sure are
useful especially in a distrubuted, networked computer environment.

Causual inspection of the /etc/net/services file (under RTU 5.0 and
IRIX 3.3.1, and Sun-OS 4.0.3c) all indicate that syslogd is a UDP
service at port 514. UDP is a reasonably simple  protocol, in fact I
have code that broadcasts UDP datagrams which I will give to any
responsible party that wants persue this issue.

I'm (almost) sure that there is an RFC documenting the syslog
protocol.

Dale
============
-- 
Dale Chayes Lamont-Doherty Geological Observatory of Columbia University
Route 9W, Palisades, N.Y.  10964	dale@lamont.ldgo.columbia.edu
voice:	(914) 359-2900 extension 434	fax: (914) 359-6817

[Actually, this is no RFC about syslog. It is a BSDism. It is very simple
as some have said. There is a "fake" version included with nntp. I think there
is also a real version (for System V like machines) in the comp.sources.unix
or comp.sources.misc archives on uunet. -- sob]

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

Technical Details

Message-ID: <5072@gazette.bcm.tmc.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!bcm!soma!concurrent-request

References: <5056@gazette.bcm.tmc.edu> (The moderator)

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!bcm!soma!concurrent-request
From: dale@lamont.ldgo.columbia.edu (dale chayes)
Newsgroups: comp.sys.concurrent
Subject: Re: Need syslog(3) functions
Summary: Lets try again
Message-ID: <5072@gazette.bcm.tmc.edu>
Date: 7 Apr 91 01:06:22 GMT
References: <5056@gazette.bcm.tmc.edu>  (The moderator)
Sender: usenet@bcm.tmc.edu
Organization: Lamont-Doherty Geological Observatory N.Y.
Lines: 52
Approved: concurrent@soma.neusc.bcm.tmc.edu
Nntp-Posting-Host: cortex.neusc.bcm.tmc.edu

Reply to Parent Message