search for: log_on_failure

Hi all, OS: suse 9 samba ver: 3.0.2 linux:/etc/xinetd.d # cat swat service swat { port = 901 socket_type = stream wait = no only_from = localhost 10.1.1.10 user = root server = /usr/sbin/swat log_on_failure += USERID # disable = yes linux:/etc # cat inetd.conf swat stream tcp nowait.400 root /usr/sbin/swat swat linux:/etc # cat services | grep 901 swat 901/tcp # CONFLICT, not official assigned! #smpnameres 901/tcp # SMPNAMERES #smpnameres 901/udp # SMPNA...

...ks fine on my Debian system. The only real difference that I can think of is inetd vs xinetd. Here is my xinetd config for swat: service swat { socket_type = stream wait = no user = root server = /usr/local/samba/bin/swat log_on_failure += USERID disable = no } What else could be wrong? -- James Bagley | CDI Innovantage james_bagley@non.agilent.com | Technical Computing UNIX Admin Support DON'T PANIC | Agilent Technologies IT --

...connect to port 901 with your favorite web browser. service swat { disable = no port = 901 socket_type = stream wait = no only_from = 127.0.0.1 user = root server = /usr/sbin/swat log_on_failure += USERID } TIA, Kenny Sanders

...ct localhost:901" My config files look like this: --/etc/xinetd.conf-- # # Simple configuration file for xinetd # # Some defaults, and include /etc/xinetd.d/ defaults { instances = 60 log_type = SYSLOG authpriv log_on_success = HOST PID log_on_failure = HOST cps = 25 30 } includedir /etc/xinetd.d swat stream tcp nowait.400 root /usr/sbin/swat swat ---------------------------------------------------- --/etc/xinetd.d/swat---- # default: off # description: SWAT is the Samba Web Admin Tool. Use swat \ # to configure your Samba server. T...

...# samba swat [root@ibmapt root]# cat /etc/xinetd.conf # # Simple configuration file for xinetd # # Some defaults, and include /etc/xinetd.d/ defaults { instances = 60 log_type = SYSLOG authpriv log_on_success = HOST PID log_on_failure = HOST cps = 25 30 } includedir /etc/xinetd.d [root@ibmapt root]# cat /etc/xinetd.d/swat ## /etc/xinetd.d/swat service swat { disable = no port = 901 socket_type = stream wait = no only_from = localhost...

...ke to run swat. The /etc/xinetd.d/swat file contains: service swat { disable = no port = 901 socket_type = stream wait = no only_from = 127.0.0.1 user = root server = /usr/sbin/swat log_on_failure += USERID } When I try to start the service my message log contains: xinetd[1695]: bind failed (Address already in use (errno = 98)). service = swat xinetd[1695]: Service swat failed to start and is deactivated. Any clues, I just can't get the service to start. thanks, ed

...rexec(3) routine. The server \ # provides remote execution facilities with authentication based \ # on user names and passwords. service exec { socket_type = stream wait = no user = root log_on_success += USERID log_on_failure += USERID server = /usr/sbin/in.rexecd disable = no } /etc/xinetd.d/rsh:: # default: on # description: The rshd server is the server for the rcmd(3) routine and, \ # consequently, for the rsh(1) program. The server provides \ # remote execution...

...connect to port 901 with your favorite web browser. service swat { port = 901 socket_type = stream wait = no only_from = 127.0.0.1 user = smbuser server = /usr/sbin/swat log_on_failure += USERID disable = no } #cat /etc/hosts.deny ALL:ALL #cat /etc/hosts.allow swat: 127.0.0.1 192.168.0. #killall -HUP xinetd ------------- And somewhere along the line, the file /etc/samba/smbuser was created (Linuxconf?)... #cat /etc/samba/smbuser #Unix_name = SMB_name1 SMB...

...= REUSE socket_type = stream port = 5666 wait = no user = nagios group = nagios server = /usr/local/nagios/bin/nrpe server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd log_on_failure += USERID disable = no only_from = 127.0.0.1 xx.xx.xx.xx # <- representing my real nagios server IP } And I have my default security group for that host open on port 5666 to the world for this experiment. I plan on locking that down again to the single IP of...

I have got now Redhat 7.0 and when I want to install Swat I need to edit the file /etc/inetd.conf but in Redhat 7.0 the file is named to /etc/xinetd.conf and /etc/xinetd.d can you help me ? (In Redhat 6.1 it worked alright) Greetz Rob op den kelder -------------- next part -------------- HTML attachment scrubbed and removed

...er is RH7.2, Samba 2.2.3a, following file "swat" is in /etc/xinetd.d/ ## /etc/xinetd.d/swat service swat { port = 901 socket_type = stream wait = no # only_from = localhost user = root server = /usr/local/samba/bin/swat log_on_failure += USERID disable = No } Thanks, Nick Ruth --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.377 / Virus Database: 211 - Release Date: 7/15/2002

...e.... this time swat is not working !!! I have checked the etc/services file and swat 901/tcp is in there and I have a text file named swat in etc/xinetd.d directory containing the following... service swat { port = 901 socket_type = stream wait = no user = root server = /usr/local/samba/bin/swat log_on_failure +=USERID disable = no } I can't access is from either the browser on my PC or from KDE's Konqueror Have I missed some vital step ? It all worked last week when I first/second/third installed everything but I've been busy installing M$ Windoze 2000 for a few days and my brain is addle...

...au sujet de swat bonjour, je vous ?cris car je n'arrive pas ? me connecter ? swat alors que le fichier est configurer normalement.Voici mon fichier swat, a tout hasard: service swat { port = 901 socket_type = stream wait = no only_from = 127.0.0.1 user = root server = /usr/sbin/swat log_on_failure += USERID disable = no } Je n'accede a swat que depuis mon serveur. Par ailleur j'utilise red hat 8.0 d'o? la version des packages samba est 2.2.5-10. Pouvez-vous m'aidiquer les rectification que je devrais faire afin que cela fonctionne. Merci d'avance car c'est u...

...ort 901 with your favorite web browser. service swat { disable = no port = 901 socket_type = stream wait = no only_from = 127.0.0.1 user = root server = /usr/sbin/swat log_on_failure += USERID ================================================================= I have restarted xinetd. Should I be able to see swat in the process list? # ps ax|grep swat 24560 pts/1 S 0:00 grep swat When I go to a browser and go to: http://<serverip>:901 nothing happens at all....

I am inquiring about setup of the SWAT utility I have installed Red Hat 7.0 with samba installed during the initial setup of Redhat. I have two network cards installed in my Server and I am connected to the internet via a Cable Modem. When I try to start SWAT netscape displays the message that it cannot find the local host on port 90. I have downloaded the book over samba and I have also tried to

I've looked in /usr/local/samba/swat for help and even the samba source docs and can't find anything on setting up swat. I've also looked at samba.org/samba/docs, but can find a swat setup doc. Can some please point me in the right direction? thanks, daniel

I have tried everything that I know of. I have reviewed the services file and the swat file in xinetd.d a tun of times. It appears, via netstat that swat is listening on port 901. However when I attempt to access it via the Mozilla browser on my Fedora server (with 127.0.0.1:901 or localhost:901) nothing happens. It just sits there. However, if I access it via webmin (which has swat stored

hello, i'm having a wierd problem with 0.31 tftpd-hpa. i'm using xinetd, with this config: service tftp { disable = no socket_type = dgram wait = yes user = root log_on_failure += USERID bind = 10.13.0.254 server = /usr/sbin/in.tftpd nice = 5 instances = UNLIMITED per_source = UNLIMITED cps = 200 20 server_a...

I was playing with this on my test machine, (redhat 5.2, samba 2.0.3) worked great, and I was really impressed. So I decided to install this on my office machine. (redhat 4.2, samba 2.0.3) and the only significant difference is that on the office machine, I use encrypted passwords. I cannot get swat to authenticate on the second machine. That is, no matter what account, password combination

...tp server, as it \ # allows crc checksumming etc. service rsync { disable = no # *** disable = yes socket_type = stream wait = no user = root server = /usr/bin/rsync server_args = --daemon log_on_failure += USERID } How does rsync check permissions ??? is it ACL compatible ? thanks for advice Please cc me (thierry.itty@besancon.org) I'm not subscribed