[opensuse-kde3] Closing session(s)
Hello world, I would like to know how to ask KDE3 (ie from a root script) to close the currently openned KDE3 session(s), with or witout leaving to the user, the possibility to abort this closure. More genelary, where can I find the documentation describing this type of command ? I thank you for the attention you paid to this mail. Patrick Serru -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Patrick Serru composed on 2016-09-07 16:45 (UTC-0500):
I would like to know how to ask KDE3 (ie from a root script) to close the currently openned KDE3 session(s), with or witout leaving to the user, the possibility to abort this closure. More genelary, where can I find the documentation describing this type of command ?
I don't know how to tell you about doing it from a script, but from a root login you can run 'ps -A | grep kde' to see the KDE3 process IDs, then use the kill command on the one with the lowest ID to close them all. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Le vendredi 09 septembre 2016, Felix Miata a écrit :
Patrick Serru composed on 2016-09-07 16:45 (UTC-0500):
I would like to know how to ask KDE3 (ie from a root script) to close the currently openned KDE3 session(s), with or witout leaving to the user, the possibility to abort this closure. More genelary, where can I find the documentation describing this type of command ?
I don't know how to tell you about doing it from a script, but from a root login you can run 'ps -A | grep kde' to see the KDE3 process IDs, then use the kill command on the one with the lowest ID to close them all. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Thank you Felix for your reponse. Until now, I have been much more brutal, doing "init 3" ! I just would like something smoother ! I am looking for information on this processes : ps ax | grep kde ... 2017 ? Ss 0:00 kdeinit Running... 2020 ? S 0:00 dcopserver [kdeinit] --nosid 2022 ? S 0:00 klauncher [kdeinit] --new-startup 2024 ? S 0:00 kded [kdeinit] --new-startup 2038 ? S 0:00 ksmserver [kdeinit] 2043 ? S 0:00 kdesktop [kdeinit] 2045 ? S 0:06 kicker [kdeinit] ... I found dcop --all-sessions --user your_user_name ksmserver default logout 0 0 0 It seems to work the way I want, that is, asking the user if unsaved documents should be saved, and possibility to abort from the user's session... For KDE3 maintainers (Serghei Amelian & Mark Goldstein, maybe ?) I have this errors while executing from a root console : SocketUNIXConnect: Cannot connect to non-local host lin-pat.chic DCOPClient::attachInternal. Attach failed Could not open network socket SocketUNIXConnect: Cannot connect to non-local host lin-pat.chic DCOPClient::attachInternal. Attach failed Could not open network socket ERROR: Couldn't attach to DCOP server! SocketUNIXConnect: Cannot connect to non-local host linux-8opp.site DCOPClient::attachInternal. Attach failed Could not open network socket SocketUNIXConnect: Cannot connect to non-local host linux-8opp.site DCOPClient::attachInternal. Attach failed Could not open network socket ERROR: Couldn't attach to DCOP server! DCOPClient::attachInternal. Attach failed Could not open network socket DCOPClient::attachInternal. Attach failed Could not open network socket ERROR: Couldn't attach to DCOP server! even if the your_user_name's session is not open. Could it be because of missing named pipe files ? typing su -c "cd /home/your_user_name/ ; dcop --all-sessions --user your_user_name \ ksmserver default logout 0 0 0" - your_user_name↵ Does not suppress error messages. If the closing session action is stopped by user, it is well mentioned by a notification dialog. I would like to know how to send such a notification to user(s), as "wall" command does not seem to work in KDE3. Sincerly, Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
participants (2)
-
Felix Miata
-
Patrick Serru