On Mon, Mar 30, 2015 at 03:18:25PM +0200, Santiago Vila wrote: > On a qemu virtual machine with minimal packages installed I do this: > > apt-get install fcgiwrap > ls -l /run/fcgiwrap.socket > ls: cannot access /run/fcgiwrap.socket: No such file or directory > > service fcgiwrap restart > ls -l /run/fcgiwrap.socket > ls: cannot access /run/fcgiwrap.socket: No such file or directory > > If I reboot: > > ls -l /run/fcgiwrap.socket > srw-rw-rw- 1 root root 0 mar 30 14:56 /run/fcgiwrap.socket > > but surely we will not tell our users in the release notes that they > have to reboot fot things to work as expected, so I'm setting > "serious" here in the hope that a fix for this is accepted in jessie.
Is this under systemd or sysvinit? > However, if for whatever reason there is not an easy fix for this, > then please feel free to downgrade severity, I don't want this package > to be removed from jessie. > > Ok, after a little bit more of testing, I found that this works just > after installing the package: > > service fcgiwrap start > > but then one might wonder: > > 1. If the service is started after a reboot, why it is not started > after installing it for the first time, as every sane package usually > does? > > 2. If "service fcgiwrap restart" does not work, why an error message > is not shown? (even a message just saying "sorry, restart not > supported" would be orders of magnitude better than not saying > anything). This should be supported. But let's try to find out what codepath is being called, depending on your init system (reportbug would have given us that info!) -- Jordi Mallach Pérez -- Debian developer http://www.debian.org/ jo...@sindominio.net jo...@debian.org http://www.sindominio.net/ GnuPG public key information available at http://oskuro.net/
signature.asc
Description: Digital signature
