New answers tagged services
1
Follow the following steps:
Your service file must go into /etc/systemd/user. Execute mv /etc/systemd/system/Testing1.service /etc/systemd/user/ for that.
Use the user mode of systemd. Execute systemctl --user start Testing1.service from your user account (not root) to start your service.
Explication systemd has two running modes, the system mode and user ...
1
Have you tried Requires ?
Requires : Configures requirement dependencies on other services. If this service gets activated, the units listed here are activated too. If one of the dependent services fails to activate, systemd does not start this service. This option may be specified more than once or you can specify multiple space-separated units. Below is ...
1
Thanks for the help. I ended up fixing this problem by modifying my trigger.sh file to this and left the udev trigger the same. This is what is in trigger.sh:
#!/bin/bash
cd /mnt/DVD/MakeMKV/
info=$(blkid -o value -s TYPE /dev/sr1)
type=$(echo 'udf')
echo $info
echo $type
if [ "$info" == "$type" ]
then
systemctl start DVD-Ripper
fi
It checks the type and ...
0
If you set the rules correctly, you should be able to do this without having to restart this service.
Some of these resources maybe helpful:
Cgroups from Arch Wiki
cgrules.service sample
cgconfig.service sample
Starting a process in a control group
0
Udev allows you to react to hardware events, in this case the ACTION can be add, remove, change.
You have ACTION=="change" which will fire when a DVD is inserted or ejected.
Try the following rule:
KERNEL=="sr1", ACTION=="add",ENV{ID_CDROM_MEDIA_DVD}="1", ENV{ID_CDROM_MEDIA_STATE}!="blank", RUN+="/mnt/DVD/MakeMKV/trigger.sh"
1
Use presto-admin server status on each node to generate a status report.
Query repeatedly each of your 763 nodes for that staus.
Sort the result on the node URL and throw away all but the latest status.
Turn that into HTML with a script.
Generate an HTML page to display which might look something like this
by perpetually refreshing an HTML page which draws ...
0
For me the solution was loginctl enable-linger username. Without this the service would die when the user logged out. https://wiki.archlinux.org/index.php/Systemd/User#Automatic_start-up_of_systemd_user_instances
Top 50 recent answers are included
