similar to: Starting smbd & nmbd from xinetd ?

Hello, I've succefuly installed samba 2.2.2 on my Linux box. I can share between Linux and MS boxes, but I want to start samba from xinetd. In /etc/xinetd.d/ I have this: #/etc/xinetd.d/netbios-ns service netbios-ns { disable = no socket_type = dgram protocol = udp port = 137 user = root wait

hi, i upgraded to samba 2.2.7 and since this nmbd (configured to start from xinetd) doesn't start! i sent SIGHUP to xinetd and can see that configuration is ok (netbios-ns is readjusted) but nmbd doesn't start!! when i start nmbd by hand with "-D" i see many messages from xinetd in /var/log/secure: Dec 3 12:05:39 atpcw6yc xinetd[1724]: START: netbios-ns pid=1973

Hi, We've got a fresh CentOS 5.4 box, and the only glitch so far is that /etc/init.d/smb doesn't start smbd. It claims it does - shows "[ok]" - but only nmbd ends up running. Even setting a higher debugging level in the smbd flags, nothing logs or shows on the console as to why smbd is immediatly quitting. To make it stranger, doing this works fine: . /etc/init.d/functions

Hi, I'm fairly new to both linux and samba. I'm running RH8 with Samba 2.2.7a. Samba's installed and is basically working, but can anyone tell me how I can get samba to start when linux boots up? I'm currently having to start it by running the following commands; ./usr/local/samba/sbin/smbd -D ./usr/local/samba/sbin/nmbd -D I've got the Using samba book from o'reilly, but

Hi, I've been running Samba successfully for several years. I tried running Samba on a new computer under Redhat 7.3 using a test smb.conf where testparm shows no errors. Running "smb start" runs properly i.e. starts smbd and nmbd, but after a few seconds both programs stop running (running "ps aux| grep smbd" shows job running, running "ps...." again shows

I am using centos 5.1 x86_64 I am wanting to restart xinetd when I do "service xinetd restart" it says xinetd unrecognized service when I do "/etc/init.d/xinetd restart" I get no such file or directory. How does one restart xinetd? THanks, Jerry

Staging for a rollout of EL 6, and ran into a very strange permissions issue with xinetd that defies all (my) logic. It's a script called "spfiled" that we use for messaging between our server cluster servers. I'm trying to get it to run with "least permissions necessary". Because it reads/writes files in conjunction with a web-based service, it runs as user

I am interested in opinions regarding the use of xinetd versus the use of tcp wrappers. The two programs have similar functionality, but I find xinetd suits my needs better. The biggest problem is the age of xinetd, and AFAIK it is no longer being kept up. Are there any known security issues with xinetd? Another issue is that xinetd makes use of a non-standard inetd.conf layout, but

One thing I have noticed on CentOS6 is that rsync via xinetd never works after a reboot. It always takes an additional, post-reboot service xinetd restart to get it going. That has been the same for all revisions up to and including 6.5, and I've seen it on more than just machine. While I don't see such a message on other problem machines, the latest reboot gave me a clue: Dec 9

I can run nmbd successfully, but smbd dies almost immediately when I run it, the smbd.log file has the message "bind failed on port 139 socket_addr = 0.0.0.0.". When I do a netstat -an | grep 139, it shows that tcp is listening on port 139. How do I resolve this conflict between tcp and smbd?

Is this the best way to get dovecot's pop3 process to run under xinetd? This is what I did after I installed postfix and dovecot. I am using Debian. I am using the dovecot local delivery agent. ---------first the dovecot configuration and version information------------------ dovecot -n output: # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 pop3s

Hi, I hate to have my first post be a bug, but this drove me crazy for a while. I compiled the latest version from source and followed the instalation instructions. I then copied the xinetd.d entries from the Wiki and proceded to test. No matter what I did I could not log on. I found that while I was editing /usr/local/etc/dovecot.conf, nothing was hapening. I then started it manualy and found

I'm trying to set up xinetd to run an asterisk console on a tcp port. So far I've added a file in /etc/xinetd.d/ like: service actl { disable = no socket_type = stream protocol = tcp port = 1234 wait = no user = root server = /usr/sbin/asterisk

_________________________________________________________________ http://redirect.gimas.net/?n=M0906xWLM2009 Neu: Messenger 2009! Hier kostenlos downloaden!

Good day, Just a quick question- could someone please confirm that this is the correct xinetd configuration (or not) for hpa-tftp? We've noticed that, when under moderate load hpa-tftpd resides in memory, even after there are no connections or even if xinetd is shut down. Under light load the server goes away after each connection, as desired. Thanks in advance! service tftp {

Hello, I would like to have the following line (among others) in my /etc/xinetd.d/rsync file : server_args = --daemon --address=<ipaddress_eth0> --log-file=/var/log/rsyncd.log To this end, i am using the camptocamp rsyncd module available from git. Everything works except this line. I thought it was, perhaps, a questions of spaces (this has been discussed on the list before),

Hi all, I can't believe that I can't find the answer to this one. I have a perl script which is called by xinetd. I want that perl script to be able to detect the remote IP address of the caller. I presumed that it would be an environment variable but I could be wrong. I've found reference to the ENV and PASSENV arguments for xinetd.conf but no examples, and no indication of what

Hey folks, When I run rsyncd from xinetd and try to rsync I will get permission denied error: rsync: chdir /home/test failed : Permission denied (13) If I shutdown xinetd and start standalone daemon ( rsync --daemon --config /etc/rsyncd.conf) everything works as expected. This is my xinetd config for rsync: service rsync { disable = no socket_type = stream wait

I'm attempting to port an existing xinetd service from CentOS 6 to something equivalent with systemd for CentOS 7 The existing xinetd config uses the attributes 'only_from' to limit connections from a limited set of remote hosts and 'banner_fail' to print a suitable error message when access is denied However, I can't find suitable 'equivalents' with systemd

Hi all Does anyone have a config file for stunnel, to work with /etc/xinetd.d? Stunnel's man page does mention it can work with xinetd, but there's no sample configuration for it. -- Kind Regards Rudi Ahlers