No need... It is failing to start because the -i -p and -b attributes defined in init.cfg are being overwritten with "" values in the startup script. To discover this, first I placed the values I needed in the startup script, and things worked. Then I commented those lines out, and the values were pulled from the init.cfg.
Note that the partial file I posted was step three... #INTERFACE="-i br0" #PORT="-p 665" #BINDIP="-b 192.168.5.35" #LOCAL="" #DNS="" #DAYLOG="" The package file is... INTERFACE="" PORT="" BINDIP="" LOCAL="" DNS="" DAYLOG="" And my intermediate testing file was... INTERFACE="-i br0" PORT="-p 665" BINDIP="-b 192.168.5.35" LOCAL="" DNS="" DAYLOG="" I used 665 in the startup file and 666 in the init.cfg just so a "ps -ef" would show where the paramiters were comming from. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215330 Title: package darkstat 3.0.714+dfsg-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darkstat/+bug/1215330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
