RE: error starting client-server protocol (code 5)

2002-09-06 Thread tim . conway
get pid of inetd kill -HUP that pid some systems have handy killers, like killall on linux, and pkill on solaris. be sure what it does. first time i tried to use killall on solaris, i found that it wasn't what I expected. Example: CTools@willy /users/Tools>ps -ef |grep inetd root 194

Mp3 lere..

2002-09-06 Thread Onur Kokcu
3mp3.net haber listesinden: Yerli ve yabanci albümler tamamen yenilendi. Artik istediginiz mp3 leri zip olarakta sitemizden indirebilirsiniz. Dosya indirme hizi yaklasik 2.5 kat artti. Boylece kisa zamanda tam albümlere sahip olacaksiniz. Istekleriniz dogrultusunda Top25 yenilendi. Bekle

[PATCH] Patches to rsync-2.5.5 for Stratus VOS

2002-09-06 Thread Paul_GreenVOS
I had to make some patches to rsync to get it to build on VOS. We are a POSIX-96 (but not Unix) system. Here is the subset of the patches that I think are general to all platforms. I have tested these here. I was surprised that CPPFLAGS is not available to the compilation rules in the Makefile.

Re: Error on Solaris 9 (2.5.5)

2002-09-06 Thread Adrian Ho
On Fri, Sep 06, 2002 at 10:25:47AM -0600, [EMAIL PROTECTED] wrote: > That is done by using a passprhaseless key. Or ssh-agent for those who're more comfortable with passphrase-protected keys. - Adrian -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before post

RE: Error on Solaris 9 (2.5.5)

2002-09-06 Thread tim . conway
That is done by using a passprhaseless key. It's been a common topic of discussion. ssh won't take plain stdin for the password, I think. Somebody on the list had another agent that could handle it. Maybe he'll speak up. Of course, if you have something on your system that can give the pas

RE: error starting client-server protocol (code 5)

2002-09-06 Thread Doug Schasteen
I fixed it. I misread the man pages about the line to put in inetd.conf. It DID tell me to put an rsyncd, but I didn't see it because it goes BEFORE the --daemon. So for anyone in the future that has this same problem (mistake), make sure you have the following line in your inetd, WITH "rsyncd" BE

RE: error starting client-server protocol (code 5)

2002-09-06 Thread Doug Schasteen
Ok, I played around with it some more and I found that if I run rsync as a standalone daemon, it works fine. So it appears the problem I was having was with inetd, specially my inetd.conf file. I’d still rather run this thing through inetd so I’m going to keep trying to get this to work. When I fi

Re: error starting client-server protocol (code 5)

2002-09-06 Thread tim . conway
Yes, send the conf. It sounds like it's running, but has nothing to say. Tim Conway [EMAIL PROTECTED] 303.682.4917 office, 303.921.0301 cell Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, caesupport2 on AIM "T

Re: Error on Solaris 9 (2.5.5)

2002-09-06 Thread tim . conway
Try this commandline: ssh vortac which rsync You'll get "no rsync in /bin /usr/bin", probably. Link it into something in the minimal path, or use "--rsync-path=" to specify where to invoke it from. Tim Conway [EMAIL PROTECTED] 303.682.4917 office, 303.921.0301 cell Philips Semiconductor - Long

error starting client-server protocol (code 5)

2002-09-06 Thread Doug Schasteen
  I’m running FreeBSD 4.6.2 on two different machines. Both machines have rync installed by way of the ports library, but one of them is running it as a server. I followed the directions in the man pages for running the server using inetd.   Here is what happens:   rsync rsync:[EMAIL