You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering what you would think about making your script better compatible with cockpit to improve user-friendly server administration. It's already pretty close to there given you went with systemd services.
I was thinking that moving from crontab to systemd timers for the restart would be a good first step. I started working on it but thought I'd get your thoughts on if there was a compelling reason to stick with crontab. If not, I'd like to contribute a little, maybe even eventually offer to install/enable cockpit as part of your script.
Just a thought...
The text was updated successfully, but these errors were encountered:
I use a @reboot tag in crontab and avoid systemd. This allows the entire setup to work as a user without root access. @reboot date;until [ -d /var/run/screen ];do sleep 1;done;date;uptime;. /etc/profile;screen -q -ls;[ $? -le 10 ]&&screen -dmS boot&&screen -S boot -X stuff 'cd /home/timr/paper&&./server.sh\n'
I'm wondering what you would think about making your script better compatible with cockpit to improve user-friendly server administration. It's already pretty close to there given you went with systemd services.
I was thinking that moving from crontab to systemd timers for the restart would be a good first step. I started working on it but thought I'd get your thoughts on if there was a compelling reason to stick with crontab. If not, I'd like to contribute a little, maybe even eventually offer to install/enable cockpit as part of your script.
Just a thought...
The text was updated successfully, but these errors were encountered: