Ptoblem for update 2.4.1 -> 2.4.6

2001-11-13 Thread Eugene Frolenkov 

After installing nevest version of sync 2.4.6 from 2.4.1,

sync --daemon  wrote to logfile:

2001/11/13 12:27:46 [12261] rsyncd version 2.4.6 starting
2001/11/13 12:27:46 [12261] bind failed on port 873
2001/11/13 12:27:46 [12261] transfer interrupted (code 10) at
socket.c(233)

sync 2.4.1 worked normally...

My question:   Where i can find "WATHSNEW" or "CHANGES" documentations
any versions of rsync? Required rsync-2.4.6 newest version of bind?

Sys: RedHat
Knl: 2.2.14
bind: 8.2.3

--
W.B.R., Evgeny Frolenkov

Re: Ptoblem for update 2.4.1 -> 2.4.6

2001-11-13 Thread Dave Dykstra 

On Tue, Nov 13, 2001 at 12:41:10PM +0300, Eugene Frolenkov wrote:
> After installing nevest version of sync 2.4.6 from 2.4.1,
> 
> sync --daemon  wrote to logfile:
> 
> 2001/11/13 12:27:46 [12261] rsyncd version 2.4.6 starting
> 2001/11/13 12:27:46 [12261] bind failed on port 873
> 2001/11/13 12:27:46 [12261] transfer interrupted (code 10) at
> socket.c(233)
> 
> sync 2.4.1 worked normally...

Chances are another process is still holding port 873 open, or you're
not running as root.


> My question:   Where i can find "WATHSNEW" or "CHANGES" documentations
> any versions of rsync?

Unfortunately there's no long-running file like that for rsync.  I see for
the next release the new maintainer has added a file called NEWS so maybe
it will be coming.


> Required rsync-2.4.6 newest version of bind?
> 
> Sys: RedHat
> Knl: 2.2.14
> bind: 8.2.3

It has nothing do with the program called bind, it is the system call bind(2).

- Dave Dykstra

Re: Ptoblem for update 2.4.1 -> 2.4.6

2001-11-13 Thread tim . conway 

The bind mentioned in the second line refers not to Berkely Internet Name 
Domain, but to socket binding.  I suspect that your old daemon is still 
running.
ps ax |grep rsync will show it if that's it.
Alternately, if you were running the daemon from inetd, you'll just need 
to make rsync available at the location pointed to by /etc/inetd.conf... 
inetd will be holding port 873, so you won't be able to start --daemon 
without reconfiguring inetd.
One other possibility.  port 873 >1025, so if you're not root, you can't 
bind to that port.

List:  did i miss anything?

Tim Conway
[EMAIL PROTECTED]
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(, 
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), 
".\n" '
"There are some who call me Tim?"




Eugene Frolenkov <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
11/13/2001 02:41 AM
Please respond to abyhan

 
To: [EMAIL PROTECTED]
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject:Ptoblem for update 2.4.1 -> 2.4.6
Classification: 



After installing nevest version of sync 2.4.6 from 2.4.1,

sync --daemon  wrote to logfile:

2001/11/13 12:27:46 [12261] rsyncd version 2.4.6 starting
2001/11/13 12:27:46 [12261] bind failed on port 873
2001/11/13 12:27:46 [12261] transfer interrupted (code 10) at
socket.c(233)

sync 2.4.1 worked normally...

My question:   Where i can find "WATHSNEW" or "CHANGES" documentations
any versions of rsync? Required rsync-2.4.6 newest version of bind?

Sys: RedHat
Knl: 2.2.14
bind: 8.2.3

--
W.B.R., Evgeny Frolenkov