28-05-2022, 03:35 PM
The next step...
as VNC does not handle the login screen on Linux (buggar) I have to get my system to auto login after a restart, so it can cope with power outages or planned reboots.. this was way simpler than I thought and all done through the GUI..
LINK-1
LINK-2
The two links above give 2 different version of the same story, though it best just in case one of them goes away...
So now I am nearly finished, just have to now schedule a weekly reboot of the system to allow all the system logs to do their clean-ups and not grow out of proportion. I could probably get away without this but seemed like a good thing to have in place just in case..
So for scheduling events Linux has a utility called crontab
to edit the events that run as the root user (the bloke who has all the clout) you need to edit the crontab file referenced by root.
This will ask you to select an editor, nano is a great choice, not the file only vaguely explains the formatting so the example below I found in another forum post (gosh) might help.
# m h dom mon dow command
# .---------------- minute (0 - 59)
# | .------------- hour (0 - 23)
# | | .---------- day of month (1 - 31)
# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# | | | | |
# * * * * * command to be executed
# * * * * * command --arg1 --arg2 file1 file2 2>&1
so to reboot on a Sunday at 5 30 we would put in this line
hit Ctrl X to exit, this should see the system reboot at 5:30 am system time on the 7th day of the week (Mon=1, Tue=2 etc)
as VNC does not handle the login screen on Linux (buggar) I have to get my system to auto login after a restart, so it can cope with power outages or planned reboots.. this was way simpler than I thought and all done through the GUI..
LINK-1
LINK-2
The two links above give 2 different version of the same story, though it best just in case one of them goes away...
So now I am nearly finished, just have to now schedule a weekly reboot of the system to allow all the system logs to do their clean-ups and not grow out of proportion. I could probably get away without this but seemed like a good thing to have in place just in case..
So for scheduling events Linux has a utility called crontab
to edit the events that run as the root user (the bloke who has all the clout) you need to edit the crontab file referenced by root.
Code:
sudo crontab -e
This will ask you to select an editor, nano is a great choice, not the file only vaguely explains the formatting so the example below I found in another forum post (gosh) might help.
# m h dom mon dow command
# .---------------- minute (0 - 59)
# | .------------- hour (0 - 23)
# | | .---------- day of month (1 - 31)
# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# | | | | |
# * * * * * command to be executed
# * * * * * command --arg1 --arg2 file1 file2 2>&1
so to reboot on a Sunday at 5 30 we would put in this line
Code:
30 5 * * 7 /sbin/reboot
hit Ctrl X to exit, this should see the system reboot at 5:30 am system time on the 7th day of the week (Mon=1, Tue=2 etc)
Peter Sumner, vk5pj
You have enemies? Good. That means you've stood up for something, sometime in your life.
- Winston Churchill
You have enemies? Good. That means you've stood up for something, sometime in your life.
- Winston Churchill