Gary, not sure what your problem is here, but here are a few
thoughts:
* Read the manpage on xinetd and xinetd.conf - they describe
the limits that can be placed on services running under
xinetd, and the 'default' limits for those services located
in xinetd.conf.
* If your question hasn't been answered, post it to the rsync
users mailing list - you can find that list on the rsync
home page 'http://rsync.samba.org/' - click on 'mailing lists'
at the top.
HTH.
--
Hardy Merrill
Senior Software Engineer
Red Hat, Inc.
Gary Chan [EMAIL PROTECTED] wrote:
> Then how can I count the number of concurrent xinetd process in the server? I want
> to know what the limit is in the server. Since I have two server box with the same
> xinetd services. But that server does not have problem at all. I think it may due to
> the hardware limitation such as RAM and CPU. Thanks!
>
>
>
> -----Original Message-----
> From: Jeff Kinz [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 10, 2003 2:33 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Rysnc Problem
>
>
> On Mon, Mar 10, 2003 at 02:23:07AM +0800, Gary Chan wrote:
> > Dear all,
> >
> > I run rsync to sync the data between two linux box. That is the master Server is
> > Linux A and the slave server is Linux B. Linux B would get the updated data from
> > Linux B. I run the cronjob everyday to do the job. However, just few day ago, I
> > found that the file cannot be synchronized and the error log obtain as below:
> >
> > >From Linux B (slave):
> > [EMAIL PROTECTED] usermgm]$ ./.sasldb_sync.sh
> > poll: protocol failure in circuit setup
> > rsync: connection unexpectedly closed (0 bytes read so far)
> > rsync error: error in rsync protocol data stream (code 12) at io.c(151)
> >
> > >From Linux A (master):
> > [EMAIL PROTECTED] log]# cat secure.2|grep "FAIL: shell"|more
> > Feb 25 11:14:57 LinuxA xinetd[659]: FAIL: shell service_limit from=192.168.160.10
>
>
> Its a xinetd problem, not an rsync problem:
> >From the xinted man page:
>
> Possible reasons for failure are:.....
> service_limit
> the allowed number of server instances for this service would be exceeded
>
>
> Your xinetd process may have been receiving too many requests at the same
> time, or the rsunc process was receiving too many requests at the same?
>
> --
> Jeff Kinz, Open-PC, Emergent Research, Hudson, MA. [EMAIL PROTECTED]
> copyright 2003. Use is restricted. Any use is an
> acceptance of the offer at http://www.kinz.org/policy.html.
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
