View Revisions: Issue #5906

Summary 0005906: gnunet-arm -e hangs in two scenarios
Revision 2019-09-25 17:25 by xrs
Description "gnunet-arm -e" should end all gnunet services and end with exit code 0.

This behaviour depends on certain conditions.

1. No running services
If there are no running services in the same user context "gnunet-arm -e" will hang. Instead it should end abnormally with an exit code greater 0.

2. Running user services in multiuser setup
If user services are running, "gnunet-arm -e" in system user context will hang. One way to solve this is to end all user services if the system service was stopped. This could be problematic in terms of right management and privilege escalation. The solution here could be that it's the service managements duty to stop all user services before stopping the system services (which is all done by root).
Revision 2019-09-25 17:25 by xrs
Description "gnunet-arm -e" should end all gnunet services and end with exit code 0.

This behaviour depends on certain conditions.

1. No running services
If there are no running services in the same user context "gnunet-arm -e" will hang. Instead it should end abnormally with an exit code greater 0.

2. Running user services in multiuser setup
If user services are running, "gnunet-arm -e" in system user context will hang. One way to solve this is to end all user services if the system service was stopped. This could be problematic in terms of right management and privilege escalation. The solution here could be that it's the service managements duty to stop all user services before stopping the system services (which is done by root).
Revision 2019-09-25 17:23 by xrs
Description "gnunet-arm -e" should end all gnunet services and end with exit code 0.

This behaviour depends on certain conditions.

1. No running services
If there are no running services in the same user context "gnunet-arm -e" will hang. Instead it should end abnormally with an exit code greater 0.

2. Running user services in multiuser setup
If user services are running "gnunet-arm -e" in system user context will hang. One way to solve this is to end all user services if the system service was stopped. This could be problematic in terms of right management and privilege escalation. The solution here could be that it's the service management duty to stop all user services before stopping the system services (which is done by root).