Hi,
there were a strange thing we have caught with Doug:
Could not bind to specified port (error 98)
on install to cleared system (no scheduler running)
because the postinst script have two scheduler-starting code.
One from /etc/debian/livesupport-station.postinst
and second from debhelper - it's started with this comment:
# Automatically added by dh_installinit
(in original /etc/debian/livesupport-station.postinst is
#DEBHELPER#
tag only
Does anybody know now to force only one scheduler start?
May I remove the start code from /etc/debian/livesupport-station.postinst?
It seems to be solution:
debhelper probably replace the #DEBHELPER# tag by scheduler start code
automatically if the file etc/debian/livesupport-station.init.d exists
=> the scheduler start code can't be in postinst scripts along with
#DEBHELPER# tag, because the start code would be redundant.
Unfortunately I haven't found any documentation to this feature
(only for automatic adding execute flag to files in init.d)
Debian experts, please, correct me, if I'm wrong - I'm going to remove
scheduler start code from livesupport-station.postinst.
On Sun, 7 Aug 2005 10:01:35 +0200 Tomas Hlava wrote:
>
> Hi,
> there were a strange thing we have caught with Doug:
>
> Could not bind to specified port (error 98)
>
> on install to cleared system (no scheduler running)
> because the postinst script have two scheduler-starting code.
> One from /etc/debian/livesupport-station.postinst
> and second from debhelper - it's started with this comment:
> # Automatically added by dh_installinit
>
> (in original /etc/debian/livesupport-station.postinst is
> #DEBHELPER#
> tag only
>
> Does anybody know now to force only one scheduler start?
> May I remove the start code from /etc/debian/livesupport-station.postinst?
>
> thanks
>
------------------------------------------
Posted to Phorum via PhorumMail