Re: multiple daemons on the same port

2005-08-02 Thread Hari Krishna Dara
On 8/1/05, Wayne Davison <[EMAIL PROTECTED]> wrote: > On Mon, Aug 01, 2005 at 02:59:30PM -0700, Hari Krishna Dara wrote: > > Where is the log file located, I couldn't find any after searching the > > entire cygwin installation for "*rsync*". > > That depends on how you have it configured. By defa

Re: multiple daemons on the same port

2005-08-01 Thread Wayne Davison
On Mon, Aug 01, 2005 at 02:59:30PM -0700, Hari Krishna Dara wrote: > Where is the log file located, I couldn't find any after searching the > entire cygwin installation for "*rsync*". That depends on how you have it configured. By default, it uses syslog, so you'd probably want to add a "log file

Re: multiple daemons on the same port

2005-08-01 Thread Hari Krishna Dara
On 8/1/05, Wayne Davison <[EMAIL PROTECTED]> wrote: > On Fri, Jul 29, 2005 at 06:28:03PM -0700, Hari Krishna Dara wrote: > > I thought if a daemon is already running on the default port, I > > thought the additional ones started on the same port will result > > in an exit with error > > It certain

Re: multiple daemons on the same port

2005-08-01 Thread Wayne Davison
On Fri, Jul 29, 2005 at 06:28:03PM -0700, Hari Krishna Dara wrote: > I thought if a daemon is already running on the default port, I > thought the additional ones started on the same port will result > in an exit with error It certainly works that way on all the Unix-like OSes I know. The error i

Re: multiple daemons on the same port

2005-08-01 Thread Hari Krishna Dara
On 7/31/05, alok barnwal <[EMAIL PROTECTED]> wrote: > Hi Hari, > Your observations is very true. > And you cannot have 2 processess running on same port. > Such problem is being faced when you try to restart > particular service and found that previous instance is > not properly stopped and hence p

multiple daemons on the same port

2005-07-29 Thread Hari Krishna Dara
I thought if a daemon is already running on the default port, I thought the additional ones started on the same port will result in an exit with error, but somehow it seems to work just fine. If I kill the first process, the second process seems to take control of the port. As far as I know you can