Menu
▾
▴
colinux-users
|
From: Guy Gascoigne-P. <gu...@wy...> - 2004-05-23 20:20:26
|
Hmm, new install on a new box, and all sorts of things that worked on box 1 don't seem to want to work on box 2 :( I can run coLInux directly with no issues, it starts nice and quickly and runs really nicely. However when I try to run it as a service it just fails, and I can't see any sign of any way to find out what's going wrong. Here's the trace: C:> ./colinux-daemon.exe --install-service -c ./default.colinux.xml Cooperative Linux Daemon, 0.6.1 Compiled on Fri May 21 20:46:24 2004 daemon: installing service 'Cooperative Linux' daemon: service command line: "C:\Program Files\coLinux\colinux-daemon.exe" --run-service "Cooperative Linux" -d -c "./default.colinux.xml" daemon: setting restart options daemon: service installed. C:> net start "Cooperative Linux" The Cooperative Linux service is starting. The Cooperative Linux service could not be started. The service did not report an error. More help is available by typing NET HELPMSG 3534. Without a console of some kind there doesn't appear to be any way to get access to any log messages, is there some hidden paramter perhaps that will caluse coLinux to log to a file so that we can see what's going wrong? Or am I missing something obvious? Guy |
|
From: A. A. A. <alp...@tt...> - 2004-05-24 05:55:08
|
On Sun, May 23, 2004 at 01:20:20PM -0700, Guy Gascoigne-Piggford wrote: > Hmm, new install on a new box, and all sorts of things that worked on > box 1 don't seem to want to work on box 2 :( > > I can run coLInux directly with no issues, it starts nice and quickly > and runs really nicely. However when I try to run it as a service it > just fails, and I can't see any sign of any way to find out what's going > wrong. > > Here's the trace: > > C:> ./colinux-daemon.exe --install-service -c ./default.colinux.xml First off, please specify the version of colinux you're using in advance. Secondly, Windows is not a POSIX system, hence forward slashes should not be used as path separators. |
|
From: Guy Gascoigne-P. <gu...@wy...> - 2004-05-24 07:29:41
|
Sorry, but the version was in the first email: Cooperative Linux Daemon, 0.6.1 Compiled on Fri May 21 20:46:24 2004 Secondly, whilst windows isn't a posix system, it's only the shell itself that objects to forward slashes, so if you are simply passing the filename through to a lower level API call, the forward slashes work just fine. That aside, I tried what I'd been doing with normal dos style slashes just in case, but it made no difference, same failure, but no message hinting to the problem. Guy A. Alper Atici wrote: >On Sun, May 23, 2004 at 01:20:20PM -0700, Guy Gascoigne-Piggford wrote: > > >>Hmm, new install on a new box, and all sorts of things that worked on >>box 1 don't seem to want to work on box 2 :( >> >>I can run coLInux directly with no issues, it starts nice and quickly >>and runs really nicely. However when I try to run it as a service it >>just fails, and I can't see any sign of any way to find out what's going >>wrong. >> >>Here's the trace: >> >>C:> ./colinux-daemon.exe --install-service -c ./default.colinux.xml >> >> > >First off, please specify the version of colinux you're using in advance. > >Secondly, Windows is not a POSIX system, hence forward slashes should not be >used as path separators. > > > > >------------------------------------------------------- >This SF.Net email is sponsored by: Oracle 10g >Get certified on the hottest thing ever to hit the market... Oracle 10g. >Take an Oracle 10g class now, and we'll give you the exam FREE. >http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click >_______________________________________________ >coLinux-users mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-users >. > > > |
|
From: A. A. A. <alp...@tt...> - 2004-05-24 09:58:54
|
On Mon, May 24, 2004 at 12:29:31AM -0700, Guy Gascoigne-Piggford wrote: > Sorry, but the version was in the first email: > > Cooperative Linux Daemon, 0.6.1 > Compiled on Fri May 21 20:46:24 2004 > It would be better if you explicitly specified as 0521-services-fix version. Other than that: Got any problems during tapdrv update? Any unknown net device in Device Mgr? (is this an XP? 2K?) |
|
From: Guy Gascoigne-P. <gu...@wy...> - 2004-05-24 16:17:32
|
This is with snapshot 0521-services-fix, though I was getting the same behavior with vanilla 0521. This is on XP, I'm using the internal bridge support using WinPcap (since this seems to muck with my machines IP address so very much less than the XP Network Bridge support). As far as I can tell, you don't actually need a Tap adapter installed in this configuration, so I removed it and have been running the non-service version quite happily since. Guy A. Alper Atici wrote: >On Mon, May 24, 2004 at 12:29:31AM -0700, Guy Gascoigne-Piggford wrote: > > >>Sorry, but the version was in the first email: >> >>Cooperative Linux Daemon, 0.6.1 >>Compiled on Fri May 21 20:46:24 2004 >> >> >> > >It would be better if you explicitly specified as 0521-services-fix version. > >Other than that: >Got any problems during tapdrv update? Any unknown net device in Device Mgr? >(is this an XP? 2K?) > > > > >------------------------------------------------------- >This SF.Net email is sponsored by: Oracle 10g >Get certified on the hottest thing ever to hit the market... Oracle 10g. >Take an Oracle 10g class now, and we'll give you the exam FREE. >http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click >_______________________________________________ >coLinux-users mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-users >. > > > |
|
From: Dan A. <da...@co...> - 2004-05-24 21:14:59
|
On Sun, May 23, 2004 at 01:20:20PM -0700, Guy Gascoigne-Piggford wrote: > Without a console of some kind there doesn't appear to be any way to get > access to any log messages, is there some hidden paramter perhaps that > will caluse coLinux to log to a file so that we can see what's going > wrong? Or am I missing something obvious? Do you see anything related in the event log? -- Dan Aloni da...@co... |
|
From: Guy G. - P. <gu...@wy...> - 2004-05-24 21:28:20
|
No, just three messages, one saying that it was sent a start, one saying that it started, immediately followed by one saying that it has entered the stopped state. Guy Dan Aloni wrote: >On Sun, May 23, 2004 at 01:20:20PM -0700, Guy Gascoigne-Piggford wrote: > > > >>Without a console of some kind there doesn't appear to be any way to get >>access to any log messages, is there some hidden paramter perhaps that >>will caluse coLinux to log to a file so that we can see what's going >>wrong? Or am I missing something obvious? >> >> > >Do you see anything related in the event log? > > > |
Thanks for helping keep SourceForge clean.
X