Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!unmvax!ariel.unm.edu!nmsu!dante!rocks
From: rocks@nmsu.edu (Dave Rocks)
Newsgroups: comp.sys.next
Subject: syslogd service
Keywords: syslogd
Message-ID: <286@opus.NMSU.Edu>
Date: 9 Nov 90 16:21:05 GMT
Sender: news@NMSU.Edu
Lines: 24


	I just corrected a long standing error on my Next system that I had
	not seen discussed anywhere else. When I boot my system, I get a
	message "syslogd: unknown service syslog/udp". I didn't know its
	cause and didn't work very hard at correcting it. It has stayed at
	the bottom of the list, but today I finally spent some time to
	figure it out. The Next documentation on Yellow Pages Installation
	and Administration says that /etc/services is no longer referenced
	after netinfo and YP are running and that you can safely delete the
	file if you are running as a YP client on a mixed network. I renamed
	my /etc/services file rather than deleting it and moved happily on.
	But syslogd no langer ran. I didn't connect the two events until
	today. What the documentation fails to tell you is that the RC
	script tries to start syslogd before either netinfo or YP. Since I
	didn't have a /etc/services file and neither netinfo or YP is
	running at the time, the start fails. Simple right? If I was a unix
	guru, I would have figured it out right away. Who says we don't need
	administrative frontends to unix. A keyboard and 2 fingers are all
	thats needed.


					Dave Rocks
					New Mexico State University
					rocks@nmsu.edu