polybar

Commit Graph

Author	SHA1	Message	Date
TheDoctor314	a7b978412c	Add env parameter to exec_sh() Before passing the cmd to exec() we set the required environment variables. Also add the test for it.	2021-09-28 22:16:07 +02:00
patrick96	47483a94f1	fix(process): fork_detached created zombie processes Since the forked processes are still our children, we need to wait on them, otherwise they become zombie processes. We now fork twice, let the first fork immediately return and wait on it. This reparents the second fork, which runs the actual code, to the init process which then collects it. Ref #770	2020-12-12 02:37:21 +01:00
patrick96	52eee95bf8	controller: Detach shell commands from polybar Shell commands triggered from action tags used to block polybar until they finished. Since we are not actually interested in the output of the commands, it makes sense to run them completely detached from polybar and have polybar not block when executing these commands. Now the spawned child processes no longer get killed when polybar exits. This is fine because polybar is not responsible for these processes since they were explicitly started by the user through click commands. Ref: #770 Ref: #1680	2020-11-29 03:53:59 +01:00

Author

SHA1

Message

Date

TheDoctor314

a7b978412c

Add env parameter to exec_sh()

Before passing the cmd to exec() we set the required environment
variables.

Also add the test for it.

2021-09-28 22:16:07 +02:00

patrick96

47483a94f1

fix(process): fork_detached created zombie processes

Since the forked processes are still our children, we need to wait on
them, otherwise they become zombie processes.

We now fork twice, let the first fork immediately return and wait on it.
This reparents the second fork, which runs the actual code, to the init
process which then collects it.

Ref #770

2020-12-12 02:37:21 +01:00

patrick96

52eee95bf8

controller: Detach shell commands from polybar

Shell commands triggered from action tags used to block polybar until
they finished.

Since we are not actually interested in the output of the commands, it
makes sense to run them completely detached from polybar and have
polybar not block when executing these commands.

Now the spawned child processes no longer get killed when polybar
exits. This is fine because polybar is not responsible for these
processes since they were explicitly started by the user through click
commands.

Ref: #770
Ref: #1680

2020-11-29 03:53:59 +01:00

3 Commits