Bug 19375 - [FR] crontab locking/timestamping/whatever to avoid double edits
Summary: [FR] crontab locking/timestamping/whatever to avoid double edits
Status: NEW
Alias: None
Product: Sisyphus
Classification: Development
Component: vixie-cron (show other bugs)
Version: unstable
Hardware: all Linux
: P2 enhancement
Assignee: placeholder@altlinux.org
QA Contact: qa-sisyphus
Depends on:
Reported: 2009-03-27 20:38 MSK by Michael Shigorin
Modified: 2009-03-27 20:38 MSK (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Michael Shigorin 2009-03-27 20:38:55 MSK
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. :)