[Initng] virtuals don't start correctly
Ismael Luceno
ismael.luceno at gmail.com
Tue Jan 2 20:38:02 CET 2007
Ismael Luceno escribió:
> Ismael Luceno escribió:
> ...
>> I finished nearly all these changes, and InitNG appears to work very
>> well, but with an exception, look at this:
>>
>> 04:04:18 R default : START_DEPS_FAILED
>> 04:04:18 S system : SERVICE_FAIL_START_RCODE
> ...
>> The problem is with virtuals, they don't start correctly.
>>
>> As you might guess, I moved all the services from system.virtual to
>> default.runlevel, so I can boot.
>>
>> Maybe service-plugin is trying to handle system.virtual?
I found that "system" isn't handled by any plugin.
But if I put another virtual in the runlevel, it's handled correctly...
>>
>> Everything else appears to work :)
>>
>
> ngc -l output:
> system : bash_helper[system]: line 2: /usr/sbin/accton: No such file or
> system : directory
> system | SERVICE_FAIL_START_RCODE (after 1 seconds)
>
> ngc -L output:
> 10:31:02 S system : SERVICE_START_DEPS_MET
> 10:31:02 S system : SERVICE_START_RUN
> 10:31:03 S system : SERVICE_FAIL_START_RCODE
>
>
> When booting I see a warning about daemon/915resolution being already in
> db, but I haven't it in default.runlevel or system.virtual, so it should
> not be parsed...
>
> Then it lauches system/acct as system (very strange).
>
> For some reason I can't reproduce this problem in fake-mode.
>
> Any ideas?
More information about the Initng
mailing list