[Leonidas Spyropoulos]
> Well since nxserver (for which I am interesting it) is maintained
> from a company named nomachine it's kinda hard to press them release
> a new version, or correct this one.

Well, I assume they are interested in getting their packages to work
also with newer Debian releases, and thus are interested in fixing
this even if they are not pressed.  Did you try to report the issue to
them?

> Maybe my only way to fix this is provide the LSB headers myself,
> which I have no idea how :P

Here are two draft headers for nxserver and nxsensor. I do not know
what they need to start before or after, so I added some default
values based on a hunch.  More information on the header format is
available from <URL: http://wiki.debian.org/LSBInitScripts/ >.

Try to add these to the init.d scripts in question and see if it help.

### BEGIN INIT INFO
# Provides:          nxserver
# Required-Start:    $remote_fs
# Required-Stop:     $remote_fs
# Should-Start:      $syslog
# Should-Stop:       $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start or stop nxserver
### END INIT INFO

### BEGIN INIT INFO
# Provides:          nxsensor
# Required-Start:    $remote_fs
# Required-Stop:     $remote_fs
# Should-Start:      $syslog
# Should-Stop:       $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start or stop nxserver
### END INIT INFO

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to