From: Henry N. <Henry.Ne@Arcor.de> - 2004-11-24 11:48:38
|
Milind Kamble wrote: > Appreciate your efforts to help me Holger. > > I tried another experiment: upgrade my colinux from > snapsot 20041007 to 20041024. Now I get the following > message in the log file created by cygrunserv: > Cooperative Linux Daemon, 0.6.2-pre6 > Compiled on Sun Oct 24 21:49:13 2004 > > daemon: exit code 84a08401^M > daemon: error - CO_RC_ERROR_ERROR, line 33, file > colinux/os/current/user/file.o (37) > > Indicates the error to be at line 33 in file.c > So I looked at the files in colinux-20041024.tar.gz. > Turns out there are 2 files: > src/colinux/os/linux/user/file.c and > src/colinux/os/winnt/user/file.c > > Since I am running colinux on Windows XP-Pro, I > guessed the colinux/os/current/user/file.o means the > file src/colinux/os/winnt/user/file.c > The contents of this file around line 33 are: > 32 if (handle == INVALID_HANDLE_VALUE) { > 33 rc = CO_RC(ERROR); > 34 co_debug("Error opening file > (%s)\n", pathname); > 35 goto out; > > So there is a possibility of finding out which file is > being tried to be opened by pathname. > > Can someone help me figure out how to use the > colinux-debug-daemon to get this information? > How do the 2 executables : colinux-daemon.exe and > colinux-debug-daemon.exe interact? Via installed driver (linux.sys). Run first debug in other command prompt, than run colinux-daemon.exe This prints all debugs. At end, you must CTRL-C to and this. colinux-debug-daemon.exe -d -p -s prints=255,misc=1,messages=255 >msg.log If you not see your line with "Error opening file (...)", set the size of lines very bit in XP-command prompt and run without redirection. > > Thanks > > --- Holger Krull <hol...@gm...> wrote: > > >>>well, first you should run it successfully from >> >>the console. >> >>>only when that works you can add it as service, >> >>and set the >> >>>appropriate dependencies (winpcap+bridge or just >> >>tap). >> >>According to the description the problem is not >>running colinux but installing the service. >>The original error message was about the windows >>service controller. And that usually only appears on >>heavily overloaded machines (swapping all the time) >>or if another programm installing a services or >>trying to start/stop one at exactly the same time. >> >>Maybe an antivirus program of some kind is prevent >>its own deinstallment? >> >>I'm out of ideas now. >> >> >> > > ------------------------------------------------------- > >>SF email is sponsored by - The IT Product Guide >>Read honest & candid reviews on hundreds of IT >>Products from real users. >>Discover which products truly live up to the hype. >>Start reading now. >>http://productguide.itmanagersjournal.com/ >>_______________________________________________ >>coLinux-users mailing list >>coL...@li... >> > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > > > __________________________________ > Do you Yahoo!? > Meet the all-new My Yahoo! - Try it today! > http://my.yahoo.com > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > -- Henry Nestler |