[Kolab-devel] why is /kolab/etc/rc called with exec in /etc/init.d/kolab?

[Richard Bos]

Hello,

I wonder why 'exec' is being used to launch /kolab/etc/rc in the
/etc/init.d/kolab script?  The problem with it at the moment is,
that programs being programmed to start after the line wth exec
are not started...

I encounter this problem with a kolab/fetchmail combination....
Where fetchmail is to be started after /kolab/etc/rc has finished.

Would it be a problem to leave out the exec line and just launch
it without exec?  After all when the same command is given on the
command line, as proposed by kolab_bootstrap, it is executed without
exec too...


The problem can be emulated with:
----8<----8<----8<----8<----8<----8<
exec echo test
echo this line is not echoed
----8<----8<----8<----8<----8<----8<
put the above in file and execute it, the result is just 'test' ....

Please, find attached a updated /etc/init.d/kolab script.  The change is
that it looks for its filename and from that deduct whether kolab should
be started or stopped.  It is not for general use yet, as the fetchmail is
being started from it as well.  Perhaps fetchmail should be switch on
and off with a variable?

-- 
Richard Bos
Without a home the journey is endless
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kolab
Type: application/x-shellscript
Size: 635 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20050812/aa195fa9/attachment.bin>