Ticket #1353 (closed defect: fixed)

Opened 2 years ago

Last modified 13 months ago

licq should check for stale pidfile

Reported by: Peter Eisentraut <peter_e@…> Owned by: erijo
Priority: normal Milestone: 1.3.4
Component: licq daemon Version: 1.3.2
Keywords: Cc:

Description

15:32:28: [ERR] Licq: Already running at pid 4793.
                      Kill process or remove /home/nemesis/.licq/licq.pid.

This is an annoyance because no error is reported in the GUI, so it appears that licq is simply doing nothing. Even worse, there is no process 4793, so the pidfile is obviously stale. licq should check for that. An even better check would be to write /proc/self/cmdline also into the pidfile, and then see if /proc/<pid>/cmdline matches that. Then even if a different process has taken over the pid, licq can still start successfully.

Change History

Changed 2 years ago by erijo

  • owner set to erijo
  • status changed from new to assigned
  • milestone set to 1.3.4

Changed 2 years ago by erijo

  • status changed from assigned to closed
  • resolution set to fixed

Fixed in r4644.

Changed 13 months ago by anonymous

  • milestone 1.3.4 deleted

Milestone 1.3.4 deleted

Changed 13 months ago by erijo

  • milestone set to 1.3.4
Note: See TracTickets for help on using tickets.