similar to: RSYNC Hangs on large file counts and xinetd

Hi ! I wonder if the R application is capable of utilizing more than one CPU. I need to know since we run it on a SunFire 3800 with 8 750 USIII cpu:s and on a E420R with 4 USII cpu:s and we don't feel like we get the performance we could expect. I've seen some old discussions claiming that it isn't. With kind regards Lennart Araskoug

I've got a puzzling issue, thought I'd ask to see if anyone else has had a similar problem. We have two machines that are synchronizing directories one way - the data files are being pushed from the source to the destination. On the destination system, I have multiple (6) modules set up to receive data based on type. The source system is running rsync 2.6.2, the destination is running

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

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

--------------------------------------------------------------------- Red Hat, Inc. Red Hat Security Advisory Synopsis: Updated xinetd package available for Red Hat Linux 7 and 7.1 Advisory ID: RHSA-2001:109-05 Issue date: 2001-08-31 Updated on: 2001-09-07 Product: Red Hat Linux Keywords: xinetd memset segfault audit Cross

I just submitted a PR for this (haven't even gotten the confirmation email), but since not everyone tracks the GNATS CVS distribution, I figured that I'd send it here as well. -----Forwarded Message----- > From: Steve Grubb <linux_4ever@yahoo.com> > To: bugtraq@securityfocus.com > Subject: Xinetd 2.3.10 Memory Leaks > Date: 18 Apr 2003 16:18:36 +0000 > > >

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

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

On Thu, May 28, 2020 at 04:46:34PM +0100, Gary Stainburn wrote: > > 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 >

In article <202005281646.34790.gary.stainburn at ringways.co.uk>, Gary Stainburn <gary.stainburn at ringways.co.uk> wrote: > 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

https://bugzilla.mindrot.org/show_bug.cgi?id=3717 Bug ID: 3717 Summary: Stricter sshd absolute path requirement breaks xinetd Product: Portable OpenSSH Version: 9.8p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at

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

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

CentOS Errata and Bugfix Advisory 2012:0409 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-0409.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b8e851bd220e6e7c3dd7a8b09526c78b10fc5cbcf977b5d42ebc097043fcca27 xinetd-2.3.14-34.el6.i686.rpm x86_64:

CentOS Errata and Bugfix Advisory 2012:1162 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1162.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1c846cf57186bdf96378409e312b03918b043422c731d0a6e6102e24bc53a95f xinetd-2.3.14-35.el6_3.i686.rpm x86_64:

CentOS Errata and Security Advisory 2013:1409 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-1409.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8b6ca635bdd172d22ee9f2eaef989e27df95e80151e9a9c7f4062afc71941140 xinetd-2.3.14-39.el6_4.i686.rpm x86_64:

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

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