similar to: EL6, xinetd, and permissions. What am I missing?

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

James Pearson wrote: > > 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 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

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

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 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

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

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 {

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

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 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

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 have a Trixbox server (CentOS derivative) from which our Cisco IP phones get their config files via TFTP. I have noticed that when I run the TFTP server via "service xinetd start", I am not able to get files via TFTP. I have tested it by doing a manual transfer via a TFTP client from another machine. When I try to run the TFTP service manually by doing

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

Hi there, Just experimenting with Samba (latest version) running on RH 7.2 Everything seems to be OK, got it running and can access shares but... smbd and nmbd have to be started manually ! ( using # /usr/local/samba/bin/smbd -D and then # /usr/local/samba/bin/nmbd -D ). Any idea how I set it to start at bootup ? It doesn't show up in the services configuration under the RH

Hello dovecot, Help me running imapd & pop3d server on xinetd. My file: # cat /etc/xinetd.d/pop-3 service pop3 { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/libexec/dovecot/pop3-login } ####################################### # cat /etc/xinetd.d/imap service imap {

Hello, I was using dovecot 1.2.x via xinetd with a setup like http://wiki.dovecot.org/InetdInstall Since I upgraded to Debian Wheezy, shipping dovecot 2.x, it no longer works. At best, I end up with stuff like Error: net_connect_unix(anvil) failed: No such file or directory Fatal: Couldn't connect to anvil Any clues? Regards, (add me in Cc in replies, I'm not suscribed to the list)

Since I've upgraded to Redhat 7.2 I cannot get swat to work, I am using the 2.4.7-10 kernal with samba 2.2.7 installed. I have checked all the applicable files, edited them accordingly as per Gary Fournerat's excellent How-to. No joy. I am pretty certain this is an xinetd issue. I never had this difficulty with inetd. I know that SAMBA is running as I can see the server from this

Got a weird one, wondering if anyone has any ideas Running an RSYNC 2.6.3pre1 server on Solaris 9 (Single USIII CPU, 1 GB RAM, SAN Disk), client is 2.6.3pre1 on Solaris 8 (Dual USII CPUs, 2 GB RAM, SAN Disk). In between the two is a Solaris 9 (Single USIIi CPU 1 GB RAM, Local Disk) system using xinetd to forward traffic from the client to the server on port 873. The client is configured to push

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