Art Ross wrote:
I run a Fundamentals of Linux class which is using RH7.3.  I was
teaching the installation and configuration of Samba last night and
encountered a problem on some machines when the students restarted their
super daemon 'xinetd'.  This only occurs on a couple of machines and
before I begin digging deeper, I was wondering if you could point in the
direction of some troubleshooting resources or what you might suspect is
the problem.
  After installing Samba including the samba-swat package, I have each
adminstrator change the disable key in /etc/xinetd.d/swat file to
'disable = no'.  They must then restart the xinetd daemon to make these
changes take effect.  Well, it doesn't on a couple of machines.
  Any help is appreciated.
  Thanks,
  Art

Oddly - xinetd doesn't appreciate malformed config entries - double-check all xinetd configs - perhaps diff them against a different machine and see what's different. I remember with a recent upgrade of xinetd, the new version no longer appreciated a method of logging I had chosen. Changing some punctuation in the statement solved the problem. Might be something to go on...


And of course, are there any log entries in /var/log/messages?

-Rick
--
Rick Johnson, RHCE #807302311706007 - [EMAIL PROTECTED]
Linux/WAN Administrator - Medata, Inc. (from home)
PGP Public Key: https://mail.medata.com/pgp/rjohnson.asc




-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to