uuomar@venus.lerc.nasa.gov (Omar Syed) (04/05/91)
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. Thanks, Omar Syed Computer Services Div. NASA Lewis Research Center 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
dale@lamont.ldgo.columbia.edu (dale chayes) (04/07/91)
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
uuomar@mars.lerc.nasa.gov (Omar Syed) (05/04/91)
Thank you for responding to my earlier posting. We have had a recent favorable response from Concurrent concerning support for syslog(3). It is not yet clear how they will support syslog(3) functionality, only that they are working on the problem. I might add, that they have been very courteous over the telephone and seem concerned. Further developments will be promptly posted. Omar Syed Computer Services Div. NASA Lewis Research Center 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
hank%westford.ccur.com@relay.cs.net (05/04/91)
In article <5072@gazette.bcm.tmc.edu> you write: > >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. >> >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. > Stan, This has come up before but some things keep coming back. :^) Syslog was included in MASSCOMP's sendmail non-product. When the company adopted MMDF there was no need to continue to keep syslog around. If people want syslog they may be able to get a copy of the old sendmail kit through their sales rep although I wouldn't bet on it. I think that sendmail might have been put into the user's library if so then syslog will be there as well. Hank Cohen Concurrent Nippon Corp. Tokyo Japan. 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
john@bu.edu (John Robert LoVerso) (05/04/91)
In an article, Dale Chayes writes: > I'm (almost) sure that there is an RFC documenting the syslog protocol. > > [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] There is, of course, no RFC on syslog. Not only is the "protocol" simple, but the implementation is readily available. I.e., from uunet: /usr/spool/ftp/bsd-sources/usr.sbin/syslogd: total 34 -r--r--r-- 1 archive 25042 Jun 29 1990 syslogd.c -r--r--r-- 1 archive 169 Jun 29 1990 Makefile -r--r--r-- 1 archive 5247 Jun 27 1990 syslogd.8 -r--r--r-- 1 archive 1216 Jun 1 1990 pathnames.h This is the 4.3-reno version, and with a few changes it should work under RTU. Minor other work would be required to make a libsyslog.a and the user-level "logger" program. Of course, this wouldn't give you support of the BSD-like /dev/klog, and I'm not (personally) sure how RTU's /dev/log and /dev/klog work. I'm not sure why syslog isn't supported under RTU, other than there just hasn't been someone to do the work. This is really almost "just an afternoons" effort. Syslog is not always the best mechanism for things. Messages can get lost and all that other nonsense as to why it's not a good solution. Never-the- less, it does a good 80% of the job and it's there for free. It was actually long ago at another company that didn't provide a reasonable syslog that I cleaned up NNTP's "fake" version to work exactly like the 4.3 version of syslog. That was, of course, before syslog was freely redistributable. All of this is of course completely my own opinion. John -- John Robert LoVerso, Concurrent Computer Corp, loverso@westford.ccur.com [to reach ME, not the corporate puppet: john@loverso.leom.ma.us] 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