| Summary: | vixie-cron crontab -e calling vi | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Clayton Clarke <claytonc> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | VERIFIED INVALID | ||
| Severity: | normal | CC: | darkside |
| Priority: | High | ||
| Version: | 2008.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | vixiecron examples | ||
|
Description
Clayton Clarke
2008-08-08 21:08:22 UTC
Created attachment 162544 [details]
vixiecron examples
as seen in the attachment, running crontab -e as normal user results in chdir permission error, running it as sudo results in vim issue and running as root is fine works as expected, except that you start with an empty root user based crontab, if it doesn't already exist. If this is considered normal and intended behaviour then please state why and i will mark or delete as necessary
I think crontab -e honors $EDITOR, what is that set to for you? (In reply to comment #1) > Created an attachment (id=162544) [edit] > vixiecron examples > > as seen in the attachment, running crontab -e as normal user results in chdir > permission error, running it as sudo results in vim issue and running as root > is fine works as expected, except that you start with an empty root user based > crontab, if it doesn't already exist. If this is considered normal and > intended behaviour then please state why and i will mark or delete as necessary > Alright that explains it all. set EDITOR properly and add yourself to the cron group. This should be enough after you log out and back in. Re-open bug if that doesn't help. thanks for the help guys it does indeed honour #editor (set as nano :) ) and the group advice really helped, i add my local user to cron and crontab, and it fully resolved all user issues, except sudo, but that ain't really a problem. as long as user custom crontab works, all is ok :) this bug, seems to only occur under sudo. Users who are not in the cron group will get a permission error instead. as of now closed, if anyone wishes further investigation into the sudo crontab -e issue. then leave a message |
