Recover edit crash files

[Jakes Louw]

Apart from the obvious impact, what else can be affected by removing the "Recover editor crash files" option from the INIT process?

[Stefan Farrelly]

In fact I find it a good idea to disable this boot up option. Weve had cases this year of servers rebooting and sitting on this boot option for ages and ages because of a whole ton of temporary files created in /var/tmp, which the editor crash recovery program is busy searching through to see if theyre vi files! Only option is to abort the bootup, delete all of /var/tmp and reboot, thus we disable it also. Weve had no problems which this feature disabled.

You should have a cleanup job to tidy up /var/tmp periodically anyway, but this didnt save us from the the sudden large appearance of files in /var/tmp caused by some app/user before our cleanup job would remove them, then we did a reboot, and we had the problem above.

[Sanjay_6]

Hi Jakes,

Fortunately we did not had to face the situation as referred by Stefan, so we are still keeping this option around. But i do concur with the statement that it should not be any big problem if you turn this option off. But probably only to avoid sitations like stefan has suggested, else you can leave it on. Why mess with the standard procedure if you are not required to loose any sleep on it.

Hope this helps.

Regds

[Jakes Louw]

My reason for asking is PRECISELY the scenario as mentioned by Stefan: I waited 90 minutes a while back for this darn init job to complete, and finally aborted it with CTRL \ anyway.
I was just wondering if there was anything I could break by disabling this function. AFAIC, nobody should be sitting in huge edits on our production servers.