On Fri, Sep 29, 2000 at 03:29:39PM -0400, Pierre Abbat wrote:
> On Fri, 29 Sep 2000, Daniel Veillard wrote:
> >I just upgraded to rsync 2.4.6 on rpmfind.net
> >
> >I got surprized by the following in the log:
> > Sep 29 19:30:05 rufus rsyncd[14552]: max connections (50) reached
> >
> >While a "ps auxwwww | grep rsync" only showed up a single connection active
> >This problem may not be easy to spot if the rsync process is always
> >relaunched from inetd but in my case I have rsync running as a server in
> >a continuous way :-)
>
> Try running "tcpdump port 873" (you have to be root to run this). This shows
> all packets on the rsync port, and you can see how many different hosts are
> using it. Also try netstat.
Hum ... did rsync model changed that much ?
Until now (i.e. up to 2.4.1 in my experience) rsync server was forking
for each client ... If it's still the case then counting the rsync running
gives the number of clients. If it's not the case anymore then I'm concerned
because sometimes I want to serve as root and sometimes as nobody (and
I was under the impression that this was working).
If you really want to know preciasely what process uses port 873 under
linux then the right way is "lsof -i tcp:873" . But it's not what I was
asking, I still believe rsync forks for each client. Back to the initial
question, assuming I had only one client served, how come rsyncd refused a
new connection logging to syslog "max connections (50) reached" ?
Daniel
--
[EMAIL PROTECTED] | W3C, INRIA Rhone-Alpes | Today's Bookmarks :
Tel : +33 476 615 257 | 655, avenue de l'Europe | Linux XML libxml WWW
Fax : +33 476 615 207 | 38330 Montbonnot FRANCE | Gnome rpm2html rpmfind
http://www.w3.org/People/all#veillard%40w3.org | RPM badminton Kaffe
