From: Jason A. <ja...@co...> - 2007-03-24 01:51:09
|
George P Boutwell wrote: > I'm curious, too, if other people who run coLinux as service have seen > this problem or not. Other than that Jason, we are looking into this > problem and should have an patch applied once we figure out what the > issue is. It would help, alot to know your command-line, especially the > options that you are sending to coLinux when you register your service. > I posted all the requested information to the list yesterday :) Unfortunately it topped out just a little over 'maxsize' so went to the admin for approval. Hopefully he approves it soon to let it through! Here though is part of the post, minus the log outputs which is what caused it to go oversize.: Henry Nestler wrote: > > Your command line for installing the service and the config file would > > be interesting, and the current directory where you stays on installing > > the service. > > > C:\Program Files\coLinux>colinux-daemon --install-service "coLinux - Lynx" @d:\coLinux\Configuration\Lynx.config (Lynx.config) kernel="c:\Program Files\coLinux\vmlinux" mem=256 cobd0=d:\coLinux\FileSystems\Lynx\root_fs cobd1=d:\coLinux\FileSystems\Lynx\swap_file eth0=tuntap,"TAP" root=/dev/cobd0 ro > > CoLinux 0.7.1 use a new internal parameter for starting service, if path > > for installing and running is differ. This could be a problem? > > Are you shure, to re-installed the service after update from 0.6.4 to > > 0.7.1? Re-installing means two calls --remove-service and --remove-service. > > > Yes. I clean-installed Windows onto an empty hard disk then installed coLinux 0.7.1 (just transfered the root_fs file), so I know there was no prior 0.6.4 config cruft. |