Vetteman Posted December 4, 2021 Share Posted December 4, 2021 I've had a couple of vms seem to hang so I pressed the three finger salute to reboot the vm guest and my Unraid server rebooted. I did this while accessing the vm from the Unraid server's keyboard, monitor and mouse as I was using pass through for video & sound card. I did some poking arround in the \etc\inittab config and commented out the line ca::ctrlaltdel:/sbin/shutdown -t5 -r now I did edit \etc\inittab via terminal seesion webgui using, nano putting hashmark "#" in front of line ca::ctrlaltdel:/sbin/shutdown -t5 -r now I Pressed Ctrl O to save & Ctrl X to exit. I re-opened nano to verify if my changes were indeed saved and they were saved. Next I rebooted the server via the webgui and once the server came back, again via nano I opened the inittab config file and there was NO # in front of "ca::ctrlaltdel:/sbin/shutdown -t5 -r now". What am I doing wrong? How can I make this a permanent change to the inittab config? Also, this should disable control alt delete from rebooting the host. But will it still allow a reboot of the VM guest? Also are there any good reasons for NOT commenting out this line? Cheers from Nova Scotia & many thanks... Quote Link to comment
Squid Posted December 4, 2021 Share Posted December 4, 2021 Settings to the underlying OS do not survive a reboot unless you reapply them at boot time (go file or user scripts). One of the advantages (and in certain cases disadvantages) since every boot of the OS is effectively a clean install Quote Link to comment
Squid Posted December 4, 2021 Share Posted December 4, 2021 37 minutes ago, Vetteman said: But will it still allow a reboot of the VM guest? No it wouldn't. Once you have access to the GUI why not simply restart it from the GUI? Quote Link to comment
Vetteman Posted December 4, 2021 Author Share Posted December 4, 2021 1 hour ago, Squid said: No it wouldn't. Once you have access to the GUI why not simply restart it from the GUI? I was running the vm from the keyboard, monitor and mouse of my Unraid server as I had the vm configured for video & sound passthrough. Cheers Quote Link to comment
Vetteman Posted December 4, 2021 Author Share Posted December 4, 2021 1 hour ago, Squid said: Settings to the underlying OS do not survive a reboot unless you reapply them at boot time (go file or user scripts). One of the advantages (and in certain cases disadvantages) since every boot of the OS is effectively a clean install Not sure what commands or syntax a script would contain to disable Ctrl-Alt-Del. IMHO it would be simpler just to comment out the appropriate line in the inittab config. Thanks kindly... Quote Link to comment
trurl Posted December 5, 2021 Share Posted December 5, 2021 41 minutes ago, Vetteman said: IMHO it would be simpler just to comment out the appropriate line in the inittab config. 1 hour ago, Squid said: Settings to the underlying OS do not survive a reboot The OS is in RAM, including that inittab config you are wanting to edit so the change won't survive reboot. The script you need is simply a script that runs at boot time to apply that edit. Quote Link to comment
Vetteman Posted December 5, 2021 Author Share Posted December 5, 2021 2 hours ago, trurl said: The script you need is simply a script that runs at boot time to apply that edit. I do not know what the syntax of this script would look like. No idea. I understand the inittab config is in RAM. But RAM is volatile. So isn't the inittab file loaded from a disk into RAM? Where is this inittab stored at? It must be on the flash drive some where. But I can not seem to locate it. Quote Link to comment
itimpi Posted December 5, 2021 Share Posted December 5, 2021 5 hours ago, Vetteman said: I understand the inittab config is in RAM. But RAM is volatile. So isn't the inittab file loaded from a disk into RAM? Where is this inittab stored at? It must be on the flash drive some where. But I can not seem to locate it A fresh copy of Unraid is loaded into RAM from the archives on the flash drives during the boot process and then user settings are applied to that. The file you mention is part of these archives and thus not accessible which is why you would need a script run at boot time to apply any changes Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.