Hi, please use 'Reply All' so the BTS is getting the information as well.
Am 20.04.19 um 10:46 schrieb Richard Lucassen: > On Sat, 20 Apr 2019 08:10:02 +0200 > Carsten Schoenert <c.schoen...@t-online.de> wrote: > >>> Workaround is to set PIDFILE: >>> >>> PIDFILE=/var/run/kopano/server.pid >> >> good catch. Thanks. Remarked for one of the next uploads. >> >>> Other SysV instances of kopano-* suffer from this issue as well. >> >> Could you please elaborate this a bit more? > > Well, quite simple: all other /etc/init.d/kopano-* init scripts have a > wrong PIDFILE= path. > > At the moment I have no kopano server running here. It's not that simple. I don't know at what time Kopano has changed here anything but the old style was to use a full name of the service to mark the PID file. kopano-server kopano-search ... If I read your previous email correctly the PIF files are now living in /var/run/kopano/ As I normally don't use SysV scripts anymore and also don't do any testing of the Kopano packages in this regard and I'm not sure what the correct naming now is. I guess the new behavior is dropping the prefix name 'kopano' and only use the service name as PID file name within /var/run/kopano/. But without some verification it's not clear what we need to adjust in the packaging. If someone will come up with a validated checking I'm happy to adjust this into the packaging. -- Regards Carsten Schoenert
