Hi,
this behaviour is intentional. The reason is that if a job is
suspend another will start using its resources. That's why only
privileged users can do so. However you can you scancel to send a signal
STOP directly to the job bypassing the controller.
On 05/21/2015 03:26 PM, [email protected] wrote:
Hi,
Sorry for a lot of typos in the previous mail. I have just written quick
and dirty patch that is allowing any user (under which id job is
running) to suspend resume his/her jobs. Is there any objection to
implement something like this?
*Sergey Meirovich*
Unix Support | Global Information Services | Applied Materials
[email protected]
<mailto:[email protected]>
Phone : +972543358943, ext: 15588445
Please reply to all when responding to this email and ensure the email
ID : *[email protected] <mailto:[email protected]>*is included
*From:*Sergey Meirovich --CNTR
*Sent:* Thursday, May 21, 2015 6:01 PM
*To:* slurm-dev
*Subject:* [slurm-dev] scontrol suspen only allowd to slurm user and root?
Hi
In slurmctld:job_mgr.c job_suspend()/job_suspend2() both sharint the
same check:**
/* validate the request */
if ((uid != 0) && (uid != getuid())) {
error("SECURITY VIOLATION: Attempt to suspend job from
user %u",
(int) uid);
rc = ESLURM_ACCESS_DENIED;
goto reply;
}
That pretty much means to me that job suspension (via scontrol suspend)
is allowed only to root and to SlurmUser
Is that intentional?
--
Thanks,
/David/Bigagli
www.schedmd.com
