On 2008-09-26 23:08 +0200, Joerg Schuetter wrote:
Could the portmap issue be caused by the missing K??portmap symlink
in rc1.d? By running update-rc.d -f portmap remove and then the command
update-rc.d portmap start 43 S . start 32 0 6 . stop 81 1 .
from the postinst-file the required stop script is in rc1.d.
Note the bug report is about runlevel 0, not 1. Start scripts in
runlevel 0 and 6 are special, they are called with a stop argument.
To prevent tampering to much with these links it could be split up in
for single steps. This makes sure the link in rc1.d will be created even
if the creation of the other links failed (since already existing with a
different strt number). In my grown system I already had a few links to
portmap, so it was not possible to add new ones.
If in any runlevel a link already exists, update-rc.d will not create
new ones, true. That ensures local modifications are preserved. This
does not explain why portmap isn't stopped _despite_ the link in
runlevel 0 exists.
Sven
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
