I have one issue that I’m banging my head on a wall
I want to launch some commands in nethgui that need a lot of time to execute and end it…of course during this time, nethgui is waiting the end and the user must wait before to use the server-manager…not acceptable
I mean for example the clamscan command or the freshclam/clamav-unofficial-sigs.sh update.
I did that
but even if I change ‘signalEvent’ by ‘exec’ (and adjust sudo rights) the result is the same…nethgui is hanging up. No matter I do ‘&’ in my bash script because clamav-unofficial-sigs.sh must wait between 60 to 600 seconds before to start, and clamscan must wait the end because it mails the result to the root.
One escape way could be to create a specific cron to start one minute after I launch the command, not nice but efficient
I’d go with a systemd unit that can be started by the server-manager.
create a script that executes systemctl calls
configure it for sudo execution
invoke the script from nethgui
I bet systemctl has everything you need for your requirements. In the future I’m evaluating to execute esmith events as systemd units. This could be a nice experiment
The purpose of ptrack is moving the progress bar during esmith events, which are designed to reconfigure the system. During “detached” events the UI is blocked to forbid running more events simultaneously.
Here we want to run a generic long task, for this reason I’d prefer looking at systemd units.
The unit exit status can be sent by email, written to a file and displayed by the server-manager, or sent to system journal and displayed with journalctl…