FLIT time sound battery applet

[tinypoodle]

-a and -d do not seem to have any effect with jwm-snapshot here.
Multiple instances do not appear to get prevented.

[Jakob Bysewski]

Multiple instances do not appear to get prevented.

Do you have the flit version 1.3.0 beta1 or the one from the tc repository?
Check by running

Code: [Select]

flit -VIf you have the current version please look for a file .flit.pid in your home directory while flit is running and please tell me if it exists (it's contents should be a single number which is the process id of the running flit instance).

[tinypoodle]

Code: [Select]

flit 1.3.0 Beta 1

Code: [Select]

tc@box:~$ ls -l .fli*
-rw-r--r--    1 tc       staff         972 Jan  4 13:01 .flit.conf
tc@box:~$
FWIW, running TC 2.10, but I doubt that would play any role.

[Jakob Bysewski]

I cannot get to what I must be missing here - the file should be created when flit is started and deleted after flit has been canceled.

As there is no error checking in place, flit should even crash when it cannot write the pidfile... this seems strange.

[gerald_clark]

Pid files in the home directory are probably a bad idea.
If you run a backup, and later shutdown without backup, you will be left with a pidfile in mydata.tgz.
This will cause a problem at reboot.

Some things to consider:
When checking for a pid file, make sure the pid is still running.  If not, delete it.
Store your pid files someplace else like /var/run.

[tinypoodle]

If you run a backup, and later shutdown without backup, you will be left with a pidfile in mydata.tgz.

Good catch - a scenario particular to TC.

[Jakob Bysewski]

It is checked if the pid in the pidfile is valid and an instance of flit!
If not, the pidfile is replaced upon start -> so that is not an issue.

At first I wanted to put the pidfile into /var/run but did not do it because of missing access rights. But it couild be put under /tmp/ instead.

[tinypoodle]

Doing some more testing, indeed I did find .flit.pid - no idea why I didn't before.

When running new instances, the content appears to be overwritten with PID of most recent instance.

After exiting the most recent of multiple instance, it's (no longer existing) PID would remain in the file.

[Jakob Bysewski]

Okay, thanks for this input which will hopefully give me some hint to find the problem.