[Initng] Service xxx already in db
Ismael Luceno
ismael.luceno at gmail.com
Thu Jul 2 18:16:13 CEST 2009
El Wed, 01 Jul 2009 22:59:56 +0400
Peter Zotov <whitequark at whitequark.ru> escribió:
> Hi again!
>
> I have a small question about the message:
>
> 18:35:40 -- WARN: Service <service> is already in db, please
> look there before parsing.
> To flush your cache do ngc -R
>
> I have my own distribution, targetted mainly for embedded devices,
> so, I am writing my own initscripts at least for system
> initialization. I receive these messages for four services:
> system/initial, system/initial/{virtfs,cleartmp,preparelogin} even
> when starting a fresh system in which no cache can ever be. Moreover,
> I receive same messages twice: after the "System is starting up"
> message and also after some services are starting. I looked into
> source, but have no idea about them.
These warnings can be ignored, the problem is that the service-cache
stores the names before parsing the content, I will remove the warning
because it's an inoffensive behaviour.
<...>
>
> You can check my disk image at
> http://files.whitequark.ru/t/initng_test_image.gz (3M), and
> initscripts (/etc/initng tree, really) at
> http://files.whitequark.ru/t/initng_tree.tbz2.
>
> Also, when I mount tmpfs over /dev, I destroy initng socket.
> Currently, I recreate it by signalling initng, but it warns... is
> there some nice way to do the same?
Not yet, we could remove that warning too, but I was thinking about
moving that out from /dev...
> Also, when I type `ngreboot' at console, initng does not SIGTERM
> everything, and I need to exit shell manually. Again, is there a nice
> way to fix this?
It's killalli5 who kills the processes not belonging to initng services,
so, it should work as long as you had called it... I will review your
scripts :). I was thinking about moving it inside initng for the next
version.
> And last. NGC outputs many ANSI sequences and replies weirdly on some
> commands (I think that `Command POSITIVE' isn't common reply), and
> also doesn't set exit code. This makes it unsuitable for scripts. Do
> I need to write some patch for it or is it already done?
>
If it's not connected to a tty it doesn't output any ansi sequence.
There's an open ticket for the return code feature [0], maybe you can
help with it :).
[0] http://www.initng.org/ticket/687
--
Ismael Luceno
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://jw.dyndns.org/pipermail/initng/attachments/20090702/7db1508f/attachment.pgp>
More information about the Initng
mailing list