[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[Bug 185531] Review Request: fcron, a task scheduler
- From: bugzilla redhat com
- To: fedora-extras-list redhat com
- Subject: [Bug 185531] Review Request: fcron, a task scheduler
- Date: Thu, 23 Mar 2006 13:02:01 -0500
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: fcron, a task scheduler
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185531
------- Additional Comments From fcron free fr 2006-03-23 13:01 EST -------
> > I'm not sure I understand you ... do you mean "why a non priviledged user
> > could not send a signal to fcron daemon?"
> > In this case, you should know that a user can only send a signal to one of
its
> > processes. This implies that fcronsighup has to be root (or have root
rights)
> > to send a signal to fcron daemon which is run by root.
>
> I understand perfectly the issue, what I was saying is that the only
> unpriviledged user that should be allowed to send this signal to fcron
should be
> the fcron user.
>
> What about having fcronsighup with the following rights:
> -rwsr-x--- root fcron
> or
> -rwsr-xr-- root fcron
>
In fact the default rights of fcronsighup are:
---s--x--- 1 root fcron 14K 2006-03-01 14:49 /usr/bin/fcronsighup
which mean that fcronsighup is not executable by anyone.
Then you can sure add the read right.
> > fcron runs the job with the user rights of the owner of the job. It has to
be
> > root to be able to change its rights to user's ones.
>
> Ok, so if the user wants only to run his jobs, then he can run it, so it
should
> be executable by anyone.
>
This is more complicated than that.
Fcron can be used without root privileges, but then you have to compile it
specifically for that. It just won't work if you simply give everyone the
right to execute fcron.
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]