The KDE client try to send the signal, but as it is an asyncronious call, it sometime quit before the signal have been handled connectly. I always fix that thing only to see it break again a few week later. I think both Gnome and KDE client fail to end the daemon way too often.
I created a story/feature on our bug tracker about switching to a "ping alive" like system instead of keeping client count (or trying too). This is not perfect, but it would be much more robust. https://projects.savoirfairelinux.com/issues/11837 Any feedback? ----- Original Message ----- From: "Andrew Myers" <[email protected]> To: [email protected] Sent: Thursday, May 31, 2012 10:20:17 AM Subject: Re: [SFLphone] sflphoned keeps running after gnome client shutdown Looking into this further I find that when I quit the KDE-client the instance of sflphoned started by the client is not killed. The reason I thought of using the pid and not pam would be to kill the specific sflphoned instance relating to that user when he/she quits the sfl client, which may not be the same as when they log out. Looks like that is what I will need to do for the moment as well :( Cheers Andrew On 31/05/12 15:58, Jan Middelkoop wrote: Hi Andrew, Oh, please - barge in as much as you like. That's what the internet is for. :-) Hacking around this bug is not really the issue here though. I could run a 'killall sflphoned' via pam, when the user logs out. There are more people out there using SFLphone with LTSP. In fact, I recommend it - as it is (afaik) the only softphone out there with features that target business use (conference, attended transfer, multiple calls), and that works flawless with remote X and pulseaudio (fundamental technologies behind LTSP). I'm trying to provide Tristan with information that will help him track down this bug, so SFLphone users worldwide can benefit. :) Met vriendelijke groet, Jan Middelkoop Recreatie en Zorg Groep B.V. -- Website: http://www.recreatie-zorg.nl/ E-mail: [email protected] Telefoon: +31 10 714 22 97 Op 31-05-12 15:51, Andrew Myers schreef: Excuse me barging in but, on my system there is a pid file created under the users home directory e.g. /home/username/.cachesflphone/sfl.pid, which seems to hold the pid of the sflphoned instance started for that user. If this is correct then you could use that to stop the daemon relating to that user when they quit their client. >From what Tristan says all the sflphoned instances will remain running until >the last user quits their client, at which time, it is not clear if one >sflphoned instance will be killed, or all of them. Either way would not work >for you. Cheers Andrew On 31/05/12 15:32, Jan Middelkoop wrote: Hi Tristan, Thank you for your reply. How does sflphoned check if there is still a client instance running? Because this is a terminal server environment. On busy days, there are at least 10 sflphoned & sflphone-client-gnome instances running on the computer. All under different users though. When everyone logs out, there are no instances of sflphone-client-gnome still running, but there are always several sflphoned processes still running (and accepting phonecalls). Met vriendelijke groet, Jan Middelkoop Recreatie en Zorg Groep B.V. _______________________________________________ SFLphone mailing list [email protected] http://lists.savoirfairelinux.net/mailman/listinfo/sflphone _______________________________________________ SFLphone mailing list [email protected] http://lists.savoirfairelinux.net/mailman/listinfo/sflphone _______________________________________________ SFLphone mailing list [email protected] http://lists.savoirfairelinux.net/mailman/listinfo/sflphone _______________________________________________ SFLphone mailing list [email protected] http://lists.savoirfairelinux.net/mailman/listinfo/sflphone
