19375 2009-03-27 20:38:55 +0300 [FR] crontab locking/timestamping/whatever to avoid double edits 2009-03-27 20:38:55 +0300 1 1 4 Development Sisyphus vixie-cron unstable all Linux NEW P2 enhancement --- 1 mike placeholder glebfm ldv placeholder vt qa-sisyphus oldest_to_newest 88147 0 mike 2009-03-27 20:38:55 +0300 Would be quite nice if crontab -e did something to avoid concurrent sessions with the last one silently overwriting any previous changes. Issuing a warning if a file has been changed since reading it in (by comparing temporary and spooled file timestamps) should be good enough: * check out spooled file for editing while saving its timestamp * edit * check saved timestamp against current spooled file's one * issue a warning if it's older already, or * check edited file into spool PS: yes I just [almost] did fall to this one. :)