Re: inetd Messages
Ulrich Windl (Ulrich.Windl@rz.uni-regensburg.de)
Fri, 22 Mar 1996 08:11:33 +0100
On 21 Mar 96 at 11:26, Alex Krimkevich wrote:
[empty lines compacted a bit]
> Andrew C. Esh writes:
> > > David Lynes writes:
> > > > Could someone please tell me what the following message in the syslog
> > > > file means?
> > > > inetd[44]: /usr/sbin/nmbd: exit status 0x1
> > > > [last message repeated 26 times.]
> Andrew C. Esh writes:
> > The three answers to this message I saw were not as helpful as I think they
> > could have been. I'd rather teach you to fish, than throw you some fluff
> > answer, like "Delete some lines out of your inetd.conf".
> I figure, I'll stick with your "fishing" format for now.
> Fishing tip #1: When you assume such a patronizing tone, make sure you
> know what you are talking about.
> > In particular, the "nmbd" is a netbios nameserver. It's part of a package
> > called "Samba", and is used to deal with drives and printers being shared
> > by the Windows for Workgroups, Win95, and Windows NT operating systems. This
> > package normally is installed by root, so you should be aware of it. First
> > fishing tip: Read the manual page. Do a "man nmbd".
> >
> > Specifically what we should know about this error message is that the file
> > "/usr/sbin/nmbd" does exist, but it's exiting with a non-zero result. This
> > means "nmbd" can't run for some reason. Fishing tip number two: Try running
NO, sorry, you are wrong! It's the TCP wrapper that fails to exec().
Inetd knows about ENOENT, but once TCP wrapper (or however it's
called in Linux) is up and running, inetd only sees the exit status.
It seems Slackware 2.4 installs things like this.
Maybe the main point is that TCP wrapper does not provide an error
message.
[skipping the rest]
------------
Ulrich Windl Klinikum der Universitaet Regensburg
Rechenzentrum DV-med Franz-Josef-Strauss-Allee 11
Tel: +49 941 944-5879 D-93053 Regensburg
FAX: +49 941 944-5882
Just imagine my mail address were <Ulrich.Windl@rz.uni.r.de>...