Cooperative Linux

hi, 
I think you should start it by typing
net start colinuxarch
or run it from services.msc

On Mon, 22 Nov 2004 11:09:14 -0800 (PST), Milind Kamble
<mbkads@...> wrote:
> Hi.
>    I have been using colinux for the past 6 months,
> but have always invoked it as an app from a cygwin
> bash prompt. I thought of trying to invoke it as a
> service. So
> first I installed the service using
> bash> cd /cygdrive/c/Program\ Files/coLinux
> bash> ./colinux-daemon.exe \
> -c 'c:\\Program Files\\coLinux\\archlinux.colinux.xml'
> \
> --install-service "colinuxarch"
> 
> Then when I invoke the service I get the following
> error:
> bash > ./colinux-daemon.exe --run-service colinuxarch
> Cooperative Linux Daemon, 0.6.2-pre4
> Compiled on Thu Oct  7 13:35:51 2004
> 
> colinux: running as service 'colinuxarch'
> service: Failed to initialize: last error: The service
> process could not connect to the service controller.
> 
> What am I missing?
> I am able to bring up colinux fine from the command
> line.
> 
> Thanks
> Milind
> 
> __________________________________
> 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
> coLinux-users@...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 


-- 
Regards,
Paradise

> bash> cd /cygdrive/c/Program\ Files/coLinux
> bash> ./colinux-daemon.exe \
> -c 'c:\\Program Files\\coLinux\\archlinux.colinux.xml'
> \
> --install-service "colinuxarch"

There is no reason to do this colinux, itself is able to install as a service
You get a service entry like
"E:\Programme\coLinux162pre\colinux-daemon.exe" --run-service "colinux162pre" -d -c "default.colinux.xml"

> What am I missing?
> I am able to bring up colinux fine from the command
> line.

Command Line Parameters
------------------------

The following command line paramaters may be useful in operating Cooperative 
Linux.

	-c filename.XML
		Allows you to choose a specific XML configuration file to use.

	-i servicename
		Allows you to install Cooperative Linux as a service. Also 
		use the -c parameter to specify your configuration file when 
		doing this. <servicename> is whatever you want it to be called.

I tried your suggestion by removing the installed
service first and running the command
cygwin-bash> <path>/colinux-daemon.exe --run-service
"colinuxarch" -d -c <path>/archlinux.colinux.xml

But still I get the same error that "The service
process could not connect to the service controller".

Based on my observations, whenever the --run-service
option is provided to colinux-daemon.exe, I get that
error.


--- Holger Krull <holger.krull@...> wrote:

> 
> > bash> cd /cygdrive/c/Program\ Files/coLinux
> > bash> ./colinux-daemon.exe \
> > -c 'c:\\Program
> Files\\coLinux\\archlinux.colinux.xml'
> > \
> > --install-service "colinuxarch"
> 
> There is no reason to do this colinux, itself is
> able to install as a service
> You get a service entry like
> "E:\Programme\coLinux162pre\colinux-daemon.exe"
> --run-service "colinux162pre" -d -c
> "default.colinux.xml"
> 
> > What am I missing?
> > I am able to bring up colinux fine from the
> command
> > line.
> 
> Command Line Parameters
> ------------------------
> 
> The following command line paramaters may be useful
> in operating Cooperative 
> Linux.
> 
> 	-c filename.XML
> 		Allows you to choose a specific XML configuration
> file to use.
> 
> 	-i servicename
> 		Allows you to install Cooperative Linux as a
> service. Also 
> 		use the -c parameter to specify your configuration
> file when 
> 		doing this. <servicename> is whatever you want it
> to be called.
> 
> 	
> 
> 
> 
>
-------------------------------------------------------
> 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
> coLinux-users@...
>
https://lists.sourceforge.net/lists/listinfo/colinux-users
> 



		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com

Did you ever 
colinux-daemon.exe --install-driver
?

> I tried your suggestion by removing the installed
> service first and running the command
> cygwin-bash> <path>/colinux-daemon.exe --run-service
> "colinuxarch" -d -c <path>/archlinux.colinux.xml
> 
> But still I get the same error that "The service
> process could not connect to the service controller".

I checked that with colinux-daemon.exe --status-driver
and it indicated that the driver was installed. I then
tried --remove-driver and then --install-driver.
Still no luck. It still cannot connect to the service
controller.
BTW, I do have admin previliges.

--- Holger Krull <holger.krull@...> wrote:

> Did you ever 
> colinux-daemon.exe --install-driver
> ?
> 
> > I tried your suggestion by removing the installed
> > service first and running the command
> > cygwin-bash> <path>/colinux-daemon.exe
> --run-service
> > "colinuxarch" -d -c <path>/archlinux.colinux.xml
> > 
> > But still I get the same error that "The service
> > process could not connect to the service
> controller".
> 
> 
> 
> 
>
-------------------------------------------------------
> 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
> coLinux-users@...
>
https://lists.sourceforge.net/lists/listinfo/colinux-users
> 



		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com

> I checked that with colinux-daemon.exe --status-driver
> and it indicated that the driver was installed. I then
> tried --remove-driver and then --install-driver.
> Still no luck. It still cannot connect to the service
> controller.
> BTW, I do have admin previliges.

That is strange.
Does 'net start' output the list of running services? 
Is the rpc service running? Is remote registry running?

There is policy rule that kann prevent loading Drivers and Services. Check in the policy editor, lokal policy, setting of user privileges, load and unload of Devices.
(names probably diffrent, translated from german). But how should mess with this?
I have no real clue.

Milind Kamble wrote:
> I tried your suggestion by removing the installed
> service first and running the command
> cygwin-bash> <path>/colinux-daemon.exe --run-service
> "colinuxarch" -d -c <path>/archlinux.colinux.xml

Cygwin environment?
On Windows XP I do this all in normal windows command prompt.

>>>bash> cd /cygdrive/c/Program\ Files/coLinux
>>>bash> ./colinux-daemon.exe \
>>>-c 'c:\\Program Files\\coLinux\\archlinux.colinux.xml' \
>>>--install-service "colinuxarch"

All paths should be with single backslash, also in strings.
colinux-daemon.exe -c "c:\Program Files\coLinux\archlinux.colinux.xml"
  --install-service "colinuxarch"

-- 
Henry Nestler

Henry Nestler schrieb:
> Milind Kamble wrote:
>> I tried your suggestion by removing the installed
>> service first and running the command
>> cygwin-bash> <path>/colinux-daemon.exe --run-service
>> "colinuxarch" -d -c <path>/archlinux.colinux.xml
> 
> Cygwin environment?
> On Windows XP I do this all in normal windows command prompt.
> 
>>>> bash> cd /cygdrive/c/Program\ Files/coLinux
>>>> bash> ./colinux-daemon.exe \
>>>> -c 'c:\\Program Files\\coLinux\\archlinux.colinux.xml' \
>>>> --install-service "colinuxarch"
> 
> 
> All paths should be with single backslash, also in strings.
> colinux-daemon.exe -c "c:\Program Files\coLinux\archlinux.colinux.xml"
>  --install-service "colinuxarch"

No. He is on bash, which needs either '\' quoting or "\\" to be 
correctly passed to the process.

bash> ./colinux-daemon.exe \
  -c 'c:\Program Files\coLinux\archlinux.colinux.xml' \
  --install-service "colinuxarch"
or
bash> ./colinux-daemon.exe \
  -c "c:\\Program Files\\coLinux\\archlinux.colinux.xml" \
  --install-service "colinuxarch"

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Reini Urban wrote:
> No. He is on bash, which needs either '\' quoting or "\\" to be 
> correctly passed to the process.

But why is in BASH and not in CMD.EXE
Service should start from native windows command prompt, not from CygWin 
with Path-Translators (simulation of mount).

-- 
Henry Nestler

Henry Nestler schrieb:
> Reini Urban wrote:
>> No. He is on bash, which needs either '\' quoting or "\\" to be 
>> correctly passed to the process.
> 
> But why is in BASH and not in CMD.EXE
> Service should start from native windows command prompt, not from CygWin 
> with Path-Translators (simulation of mount).

nope. this is just a simple process invocation and has nothing to do 
with cygwin mounts. it just passes the args to colinux-daemon.exe, which 
are quoted differently by various shells. cmd vs. bash in this case.
the mount is only used to search the process colinux-daemon.exe, the 
rest is independent.

BTW: it's no problem to register ot start any service from cygwin also.
And it's no problem to use cygrunsrv instead, esp. for the bridge, which 
I do. cygrunsrv has some neat features (like --chdir <dir>, logging, 
--dep, --termsig, ...) which the current win32 daemons don't have.

regardless if invoked via net start <service>, psservice start <service> 
cygrunsrv --start <service> or directly.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Reini is right. All that quoting and \-escaping was
due to command processing by bash.
Anyways, I tried to do the same from a cmd shell, and
got the same response.

net start |egrep -i 'rpc|regist' indicates the
following services are running:
   Remote Procedure Call (RPC)
   Remote Procedure Call (RPC) Locator
   Remote Registry

Then I tried the cygrunsrv route. So I first installed
the service (used the -c option to set the
change-directory). I got the following error:
cygwin-bash> cygrunsrv.exe -S colinuxarch
cygrunsrv: Error starting a service:
QueryServiceStatus:  Win32 error 1062:
The service has not been started.

Fortunately cygrunsrv dumps a log file  in
/var/log/colinuxarch.log. The contents of that file
are:
Cooperative Linux Daemon, 0.6.2-pre4
Compiled on Thu Oct  7 13:35:51 2004

daemon: exit code 80008401
daemon: error - CO_RC_ERROR_ERROR, line 33, file id 0


Anyone know what that exit code means? Also on the
line  CO_RC_ERROR_ERROR, which file is that line
number 33 referring to?

Thanks

Milind

--- Reini Urban <rurban@...> wrote:

> Henry Nestler schrieb:
> > Reini Urban wrote:
> >> No. He is on bash, which needs either '\' quoting
> or "\\" to be 
> >> correctly passed to the process.
> > 
> > But why is in BASH and not in CMD.EXE
> > Service should start from native windows command
> prompt, not from CygWin 
> > with Path-Translators (simulation of mount).
> 
> nope. this is just a simple process invocation and
> has nothing to do 
> with cygwin mounts. it just passes the args to
> colinux-daemon.exe, which 
> are quoted differently by various shells. cmd vs.
> bash in this case.
> the mount is only used to search the process
> colinux-daemon.exe, the 
> rest is independent.
> 
> BTW: it's no problem to register ot start any
> service from cygwin also.
> And it's no problem to use cygrunsrv instead, esp.
> for the bridge, which 
> I do. cygrunsrv has some neat features (like --chdir
> <dir>, logging, 
> --dep, --termsig, ...) which the current win32
> daemons don't have.
> 
> regardless if invoked via net start <service>,
> psservice start <service> 
> cygrunsrv --start <service> or directly.
> -- 
> Reini Urban
> http://xarch.tu-graz.ac.at/home/rurban/
> 
> 
>
-------------------------------------------------------
> 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
> coLinux-users@...
>
https://lists.sourceforge.net/lists/listinfo/colinux-users
> 



		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com

Milind Kamble schrieb:
> Reini is right. All that quoting and \-escaping was
> due to command processing by bash.
> Anyways, I tried to do the same from a cmd shell, and
> got the same response.

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).

see the wiki.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

> 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.

Oh yes. I have been running from the console without a
hitch for the past few months. In fact, I run it with
the following command:
cygwin-bash> ./colinux-daemon -c archlinux.colinux.xml
-d
and then connect to colinux using putty.

The reason I am trying to run it as a service is
because if by mistake I shutdown windows without
terminating all running applications, I want colinux
to get a ctl-alt-del signal which will cause it to
terminate cleanly. I believe this happens when colinux
is running as a service.

--- Reini Urban <rurban@...> wrote:

> Milind Kamble schrieb:
> > Reini is right. All that quoting and \-escaping
> was
> > due to command processing by bash.
> > Anyways, I tried to do the same from a cmd shell,
> and
> > got the same response.
> 
> 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).
> 
> see the wiki.
> -- 
> Reini Urban
> http://xarch.tu-graz.ac.at/home/rurban/
> 
> 
>
-------------------------------------------------------
> 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
> coLinux-users@...
>
https://lists.sourceforge.net/lists/listinfo/colinux-users
> 



		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com

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?

Thanks

--- Holger Krull <holger.krull@...> 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
> coLinux-users@...
>
https://lists.sourceforge.net/lists/listinfo/colinux-users
> 



		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com

> 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;

A file open error?! Maybe you can start filemon from http://www.sysinternals.com first. It will print every file accessed.

> Can someone help me figure out how to use the
> colinux-debug-daemon to get this information?

Never figured that out, sorry.

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 <holger.krull@...> 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
>>coLinux-users@...
>>
> 
> 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
> coLinux-users@...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 

-- 
Henry Nestler