82151 – fcron: problems with crontab -e

Bug 82151 - fcron: problems with crontab -e

Summary: fcron: problems with crontab -e

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	High normal
Assignee:	Cron Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-02-15 12:42 UTC by Christian Lemke
Modified:	2005-02-16 02:23 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Christian Lemke 2005-02-15 12:42:59 UTC

After I edit my crontab with crontab -e the following message appears:
chl ~ # crontab -e
21:27:06 fcrontab : editing root's fcrontab
21:31:17 Could not exec /usr/bin fcronsighup: No such file or directory


Reproducible: Always
Steps to Reproduce:
1.chrontab -e



Expected Results:  
fcronsighup (/usr/sbin/fcronsighup) should be executed. (I must do it by hand)

Comment 1 Aaron Walker (RETIRED) gentoo-dev

2005-02-15 16:26:39 UTC

Firstly, you failed to mention fcron version.
Secondly, when did you emerge fcron?  This was a previous bug that was fixed.
Doing 'emerge sync' and remerging fcron should solve the problem.

Comment 2 Christian Lemke 2005-02-16 00:36:23 UTC

Sorry for forgetting the version. :-/
> Thu Jan 20 20:40:34 2005 >>> sys-apps/fcron-2.9.5.1-r2
I re-emerged it and the problem is gone.
Thank you for the help. I only expected a new release for that...

Comment 3 Aaron Walker (RETIRED) gentoo-dev

2005-02-16 02:23:02 UTC

Yeah its my mistake; -r2 was originally supposed to fix this problem, but I goofed and only fixed half the problem.  When fixing the other half I forgot to bump the revision.

Sorry for the inconvenience.