Openbox terminate process upon logout of openbox How to?

BW-userx · 02-23-2019, 10:23 AM

is there a means to run a script to kill processes that where started with the autostart script upon login to openbox, like WindowMaker has, or what mechanisms are there that I can cut into and execute a script to kill some of the things I started when logging into openbox?

I could go into the xml file and edit it,

Code:

        <menu id="40" label="OpenBox">
            <menu id="client-list-menu"/>
            <item label="Reconfigure"> <action name="Reconfigure"/> </item>
            <separator/>
            <item label="Exit"> <action name="Exit"/> </item>

add a redirect to a script that kills the processes, then call exit perhaps. Though, every time I would update the menu it would be over written, so I'd have to go back in an edit it, or write another script calling menumaker, then using sed perhaps to remove and add that part back into the menu after menumaker is done re-creating the menu. Is there a way to get around that or is that pretty much the only avenue of attack?

this is mainly at the time of this writing, to kill a script that is running to simply change the background at a given time.

BW-userx · 02-23-2019, 11:45 AM

wrapper for menumaker : openbox

Code:

#!/bin/bash
mmaker -t xterm -f openbox3 

sed -i 's+<execute>gparted</execute>+<execute>gksu gparted</execute>+g' ~/.config/openbox/menu.xml 
sed -i 's+<item label="Exit"> <action name="Exit"/> </item>+<item label="Exit">  <action name="Execute"> \
		<execute>~/bin/obshutdown</execute> \
	</action> </item>+g' ~/.config/openbox/menu.xml

obshutdown, taken off wmakers then made to work for openbox...

Code:

#!/bin/sh
#
# Place commands to be executed when openbox is exited here.
#
# Openbox will wait until this script finishes, so if you run any
# commands that take long to execute (like a xterm), put a ``&'' in the
# end of the command line.
#
# This file must be executable.
#

piddy=$(pgrep -u $USER changebg)
kill "$piddy"

pkill openbox

it may have been a redundant question but just wanted to know...

ondoho · 02-23-2019, 02:43 PM

isn't menumaker configurable to include custom menu entries?
at least obmenu-generator is.

anyhow, do you want to kill ALL user processes after killing openbox?
how did you login and start X?
if you used "exec startx", you will be logged out when you kill openbox.
then it depends a little on the init system, but it's possible to automatically kill all user processes on logout.

BW-userx · 02-23-2019, 03:19 PM

Quote:

Originally Posted by ondoho

isn't menumaker configurable to include custom menu entries?
at least obmenu-generator is.

anyhow, do you want to kill ALL user processes after killing openbox?
how did you login and start X?
if you used "exec startx", you will be logged out when you kill openbox.
then it depends a little on the init system, but it's possible to automatically kill all user processes on logout.

right now I am using kde login manager. menumaker has a py file that can be edited, but mostly all I've ever done with that is correct the path when using wmaker for a WM.

I'm not user if I want to kill every process, never tired that to see what it does. I started using a script to change backgrounds and noticed that when I logged out of Wmaker and into openbox to set that up, the script was still running. So I fixed that in Wmaker because it has a shutdown script just for that reason. whereas Openbox is less setup for that kind of a thing.

killing every 'user' process should not be a bad thing seeings how this is on logout anyways?