Thanks guys, I will take a look at each option.
On Mon, Aug 6, 2018 at 9:52 PM, William Hay wrote:
> On Wed, Aug 01, 2018 at 11:06:19AM +1000, Derrick Lin wrote:
> >HI Reuti,
> >The prolog script is set to run by root indeed. The xfs quota requires
> >root privilege.
> >I also tr
On Wed, Aug 01, 2018 at 11:06:19AM +1000, Derrick Lin wrote:
>HI Reuti,
>The prolog script is set to run by root indeed. The xfs quota requires
>root privilege.
>I also tried the 2nd approach but it seems that the addgrpid file has not
>been created when the prolog script execut
> Am 01.08.2018 um 03:06 schrieb Derrick Lin :
>
> HI Reuti,
>
> The prolog script is set to run by root indeed. The xfs quota requires root
> privilege.
>
> I also tried the 2nd approach but it seems that the addgrpid file has not
> been created when the prolog script executed:
>
> /opt/gri
HI Reuti,
The prolog script is set to run by root indeed. The xfs quota requires root
privilege.
I also tried the 2nd approach but it seems that the addgrpid file has not
been created when the prolog script executed:
/opt/gridengine/default/common/prolog_exec.sh: line 21:
/opt/gridengine/default
> Am 30.07.2018 um 02:31 schrieb Derrick Lin :
>
> Hi Reuti,
>
> The approach sounds great.
>
> But the prolog script seems to be run by root, so this is what I got:
>
> XFS_PROJID:uid=0(root) gid=0(root) groups=0(root),396(sfcb)
This is quite unusual. Do you run the prolog as root by intenti
Hi Reuti,
The approach sounds great.
But the prolog script seems to be run by root, so this is what I got:
XFS_PROJID:uid=0(root) gid=0(root) groups=0(root),396(sfcb)
Maybe I am still missing something or prolog script is the wrong place for
getting the group ID generated by SGE?
Cheers,
D
On
> Am 28.07.2018 um 03:00 schrieb Derrick Lin :
>
> Thanks Reuti,
>
> I know little about group ID created by SGE, and also pretty much confused
> with the Linux group ID.
Yes, SGE assigns a conventional group ID to each job to track the CPU and
memory consumption. This group ID is in the rang
Thanks Reuti,
I know little about group ID created by SGE, and also pretty much confused
with the Linux group ID.
I assume that "ïd" is called inside the prolog script, typically what the
output looks like?
Cheers,
On Fri, Jul 27, 2018 at 4:12 PM, Reuti wrote:
>
> Am 27.07.2018 um 03:14 schri
Am 27.07.2018 um 03:14 schrieb Derrick Lin:
> We are using $JOB_ID as xfs_projid at the moment, but this approach
> introduces problem to array jobs whose tasks have the same $JOB_ID (with
> different $TASK_ID).
>
> Also it is possible that tasks from two different array jobs run on the same
We are using $JOB_ID as xfs_projid at the moment, but this approach
introduces problem to array jobs whose tasks have the same $JOB_ID (with
different $TASK_ID).
Also it is possible that tasks from two different array jobs run on the
same node contain the same $TASK_ID, thus the uniqueness of the
Hi,
> Am 26.07.2018 um 06:01 schrieb Derrick Lin :
>
> Hi all,
>
> I am working on a prolog script which setup xfs quota on disk space per job
> basis.
>
> For setting up xfs quota in sub directory, I need to provide project ID.
>
> Here is how I did for generating project ID:
>
> XFS_PROJID
On Thu, 2018-07-26 at 14:01 +1000, Derrick Lin wrote:
> Hi all,
>
> I am working on a prolog script which setup xfs quota on disk space
> per job basis.
>
> For setting up xfs quota in sub directory, I need to provide project
> ID.
>
> Here is how I did for generating project ID:
>
> XFS_PROJID
Hi all,
I am working on a prolog script which setup xfs quota on disk space per job
basis.
For setting up xfs quota in sub directory, I need to provide project ID.
Here is how I did for generating project ID:
XFS_PROJID_CF="/tmp/xfs_projid_counter"
echo $JOB_ID >> $XFS_PROJID_CF
xfs_projid=$(w
13 matches
Mail list logo
