Seems like the bug is solved. Can I mark it as solved or you should? Thanks for the help/info Leonidas
On Wed, Jun 30, 2010 at 11:48 AM, Leonidas Spyropoulos <[email protected]>wrote: > > > On Wed, Jun 30, 2010 at 11:08 AM, Petter Reinholdtsen <[email protected]>wrote: > >> [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? >> > Only paid customers can report issues on their site :( > And after some search I found this: > http://www.nomachine.com/fr/view.php?id=FR11G02291 > It's a feature Request for version 4.0 (currently 3.4) so I guess I can't > do > much. > >> >> > 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 >> >> I wrote the above LSB Headers into the init scripts but cannot test them > since I upgraded and I have only encounter these on upgrades. > Is there another way to check the init scripts if their LSB headers are > correct? > Will the make-testsuite show the scripts now correctly? > >> Happy hacking, >> -- >> Petter Reinholdtsen >> > > > > -- > Caution: breathing may be hazardous to your health. > -- Caution: breathing may be hazardous to your health.
