Timeline for Running script at shutdown and reboot to prevent chromium session loss
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 7, 2018 at 20:59 | comment | added | istir | Still no luck, I tried changing Default-Start and Default-Stop and even ExecStart and ExecStop - if I run systemctl stop shutdownscriptnew.service it closes chromium, but if I reboot it doesn't do anything and it still terminates it so that I have to restore session. | |
| Aug 7, 2018 at 20:20 | history | edited | Siva | CC BY-SA 4.0 | deleted 7 characters in body |
| Aug 7, 2018 at 20:20 | comment | added | Siva | yes we should start at run level 0,1 and 6 | |
| Aug 7, 2018 at 20:16 | comment | added | istir | I succeeded in enabling the script and running it but it still doesn't do what I want it to do. Maybe I should change Default-start to 0 6? IIRC these are numbers for shutdown and reboot. I had to change shutdownscript.service to shutdownscriptnew.service because I couldn't enable it otherwise. However, when running sudo systemctl stop shutdownscriptnew.service it actually does what it should and closes chromium. | |
| Aug 7, 2018 at 19:59 | comment | added | Siva | @istir try the header as updated in the answer. | |
| Aug 7, 2018 at 19:58 | history | edited | Siva | CC BY-SA 4.0 | added 431 characters in body |
| Aug 7, 2018 at 19:47 | comment | added | istir | Still no luck, when using systemctl enable it actually gives an error update-rc.d: error: shutdownscript Default-Start contains no runlevels, aborting. | |
| Aug 7, 2018 at 19:43 | history | answered | Siva | CC BY-SA 4.0 |