xinetd and swat issues - SMB

This is a discussion on xinetd and swat issues - SMB ; swat is sending all connection messages to /var/log/messages through xinetd. (See below). What do I change to make them stop? The configure PC has FC6 and Samba 3.0.23c-2. Dec 9 20:02:04 linux xinetd[8402]: EXIT: swat status=0 pid=8596 duration=2(sec) Dec 9 ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: xinetd and swat issues

  1. xinetd and swat issues

    swat is sending all connection messages to /var/log/messages through xinetd.
    (See
    below). What do I change to make them stop? The configure PC has FC6
    and Samba 3.0.23c-2.

    Dec 9 20:02:04 linux xinetd[8402]: EXIT: swat status=0 pid=8596
    duration=2(sec)
    Dec 9 20:02:04 linux xinetd[8402]: START: swat pid=8603
    from=192.168.0.110
    Dec 9 20:02:04 linux xinetd[8402]: START: swat pid=8604
    from=192.168.0.110
    Dec 9 20:02:04 linux xinetd[8402]: START: swat pid=8605
    from=192.168.0.110
    Dec 9 20:02:04 linux xinetd[8402]: EXIT: swat status=0 pid=8603
    duration=0(sec)
    Dec 9 20:02:04 linux xinetd[8402]: EXIT: swat status=0 pid=8602
    duration=1(sec)
    Dec 9 20:02:04 linux xinetd[8402]: EXIT: swat status=0 pid=8604
    duration=0(sec)
    Dec 9 20:02:04 linux xinetd[8402]: EXIT: swat status=0 pid=8605



  2. Re: xinetd and swat issues

    On Sun, 10 Dec 2006 06:45:07 -0500, in comp.protocols.smb ,
    "linux-tek" wrote:

    >swat is sending all connection messages to /var/log/messages through xinetd.
    >(See
    >below). What do I change to make them stop?


    to point swat at a different logfile, read the manpage and then edit
    /etc/xinetd.d/swat appropriately (look at other files in xinet.d to
    see the format etc).
    --
    Mark McIntyre

  3. Re: xinetd and swat issues


    Mark McIntyre wrote:
    > On Sun, 10 Dec 2006 06:45:07 -0500, in comp.protocols.smb ,
    > "linux-tek" wrote:
    >
    > >swat is sending all connection messages to /var/log/messages through xinetd.
    > >(See
    > >below). What do I change to make them stop?

    >
    > to point swat at a different logfile, read the manpage and then edit
    > /etc/xinetd.d/swat appropriately (look at other files in xinet.d to
    > see the format etc).
    > --
    > Mark McIntyre



    The man page makes reference to SWAT configuration in "inetd". Not
    true in FC6 which uses xinetd.d. So, I think the man page is dated
    even though I have latest version of the utility.

    >>>

    DESCRIPTION
    This tool is part of the samba(7) suite.

    swat allows a Samba administrator to configure the complex
    smb.conf(5) file via a Web browser. In addition, a
    swat configuration page has help links to all the configurable
    options in the smb.conf file allowing an admin-
    istrator to easily look up the effects of any change.

    swat is run from inetd
    <<<

    I tested this parameter "options=--debuglevel=0" in the swat config
    file but the results were the same. Every time I click on something in
    the swat browser interface it logs the START/EXIT messages to
    /var/log/messages. Don't know if this a bug but it seems to be strange
    that swat needs to log these messages. I've never seen this in any
    preivous version of smb/swat.


  4. Re: xinetd and swat issues

    On 10 Dec 2006 10:47:49 -0800, in comp.protocols.smb , "lnx"
    wrote:

    >The man page makes reference to SWAT configuration in "inetd".


    Yes. However....

    >Not
    >true in FC6 which uses xinetd.d. So, I think the man page is dated
    >even though I have latest version of the utility.


    .... application of a little thought will reveal how to configure
    xinetd.d/swat so that you get what you want. Like I said, read a few
    of the other config files to get the idea.

    >I tested this parameter "options=--debuglevel=0" in the swat config


    You can't add unexpected new lines to the xinetd config files. As I
    mentioned, if you read a few of the other config files you will see
    what you need to do - I'm sure you will have at least one service that
    requires some extra server_args.

    You might also find man xinetd.conf useful.

    I'm not trying to be obtuse by the way, I just feel its better to
    learn for oneself.
    --
    Mark McIntyre

  5. Re: xinetd and swat issues


    Mark McIntyre wrote:
    [snip]
    >
    > You might also find man xinetd.conf useful.
    >
    > I'm not trying to be obtuse by the way, I just feel its better to
    > learn for oneself.
    > --


    Well, the light came on. Doing the man on xinetd.conf did the trick as
    you said. Thanks for being obtuse. I needed the kick in the rear end
    to get me started. The answer was very simple. Added one line to the
    swat configuration file: [ log_on_success = ]. I left the value empty,
    restarted xinetd and went to my swat web pages. No START, EXIT, etc
    entries are present in the messages log now.


  6. Re: xinetd and swat issues

    On 23 Dec 2006 06:09:14 -0800, in comp.protocols.smb , "lnx"
    wrote:

    >Thanks for being obtuse. I needed the kick in the rear end
    >to get me started.


    Always glad to render assistance :-)
    --
    Mark McIntyre

+ Reply to Thread