Generally if a reboot script someone wrote acts like that it means that some part of it killed something that immediately caused the logout prior to the reboot command happening. It may be that usually whatever it kills that causes the logout does not always kill the script prior to the reboot happening (race condition). A suggestion would be to make the script a 2 script process, the first script nohup's the 2nd script, or you can nohup the script when you run it. That will prevent a terminal kill from killing and cleaning up the script. On Tue, Nov 3, 2020 at 3:58 PM Samuel Sieb <samuel@xxxxxxxx> wrote: > > On 11/3/20 4:54 AM, Tom Horsley wrote: > > I just ran my normal reboot script which just kills off > > some things systemd has problems killing sometimes then > > does a reboot. > > It would help if you provided the script. > > > Instead of rebooting, it acted like a logout. > > > > I logged back in again, and uptime said 3 days. > > > > I rebooted again, and it really did reboot the 2nd > > time. What the heck happened the first time? > > Maybe there was something inhibiting the reboot. > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
