Shutdown without saving: how to reduce the 60 sec. [SOLVED]

[Feek]

I use VanillaDpup64 9.2.6. and I never save session on shutdown.

Till now I always pressed the tab key or the right arrow key to switch to NO SAVE and then confirmed with enter key.
Unfortunatelly in some puppies the keys do nothing in this situation or they become active after some time.
In this case it is better to wait 60 sec.
But I would like to shorten the 60 sec. (e.g. for 5 sec.).

What script and which line to edit or what else to do?
(better to ask than to randomly experiment)

[MochiMoppel]

to be deleted

[fredx181]

To change 60 seconds to 5: the script is /etc/rc.d/rc.shutdown (well, it is on my Fossapup).
Find dialog --timeout 60 and change to dialog --timeout 5
(and best then to change the info text too: Or, wait 5 seconds ....)

[Feek]

@MochiMoppel ,
sorry, I didn't say I'm in pupmode 13. I usually make the changes at a start of the session and use save button to save them.
Anyway thanks for your reply.

@fredx181 ,
this is exactly what I wanted .
Thank you

[greengeek]

I think you may also have to change the default to NO SAVE.
Otherwise after your 5 second delay it will automatically SAVE won't it?

[Feek]

I think you may also have to change the default to NO SAVE.
Otherwise after your 5 second delay it will automatically SAVE won't it?

I don´t think so.
If the enter key is not pressed within 5 sec., the session will not be saved (as the dialog says).

[mikeslr]

From the foregoing, it appears that Feek is operating under PupMode 13, which is automatically established with a frugal install to a USB-Key.
But if you deploy a Puppy to a hard-drive, and then create a SaveFile/Folder it automatically functions under PupMode 12. Changes are automatically written to the SaveFile/Folder. In order to avoid that you can configured it to run under PupMode13: (a) the linux/kernel line of the grub or grub4dos's listing must include a pmedia=ataflash or atausb argument; and (b) the save-session interval setting [Menu>System>Puppy Event Manager>Save Session Tab set to 0/zero with a check in the 'Ask at Shutdown' box.
Some recent Puppys provide the required '(b)' settings by default. So no change would be needed. But it's best to check.
Configuration of the 'save interval' only sets how often during a session a Save will be triggered under PupMode 12; 0/zero = Never. Once triggered, the /etc/rc.d/rc.shutdown's configuration determines how much time you have to decide whether or not to Save. The default if no 'x' is placed in the 'Ask at shutdown' box is Save: you would still be operating under PupMode 12.

[Feek]

To change 60 seconds to 5: the script is /etc/rc.d/rc.shutdown (well, it is on my Fossapup).
Find dialog --timeout 60 and change to dialog --timeout 5
(and best then to change the info text too: Or, wait 5 seconds ....)

Fred's advice about the timeout (editing in /etc/rc.d/rc.shutdown) works great.

But if I update the instalation with the latest .iso (Vanilladpup64 has weekly updated builds) the "system-wide" config files in /etc seem to be brand new, ignoring the changes in my savefolder (I have to change the interval from 60 sec. to 5 sec. after each update with a new .iso).

This is not an issue or a complaint, just a statement of fact (it's not a problem to do one extra step after a manual update).

I've always thought that the save (folder/file) has a higher priority on the system, but that doesn't seem to be the case for the system configuration files in /etc.