| Author |
Message |
Ulrich Seeling
Guest
|
Posted:
Tue Dec 07, 2004 2:26 am Post subject:
Problems with unix group within LBS (for distributed analysi |
|
|
Hi *,
I made following experience when trying to use Sun Gridengine via LBS for
distributed analysis:
Even SGE is configured correctly so that it used the effective group id of
the user submitting the job it seems that the LBS daemon does not transfer
this information correct (IC5.0.33).
So if user U with default group g1 switches to group g2 and executes spectre
via LBS (which puts the job into sge), the result files have the ownership
of U with group g1 instead of g2. That can cause problems in an environment
where project access is done via unix group membership ...
Can somebody confirm or negate this behaviour ?
(Anybody using LBS and using unix group id switching ?)
regards
Ulrich
|
|
| Back to top |
|
 |
Andrew Beckett
Guest
|
Posted:
Wed Dec 08, 2004 1:28 pm Post subject:
Re: Problems with unix group within LBS (for distributed ana |
|
|
A similar problem was reported recently by one of our large German
customers - the issue is that cdsqmgr doesn't preserve the primary group
in the submitted job.
I suggest you contact customer support, and then we can tie you in with
the PCR for this:
PCR: 754666
Title: cdsqmgr change unix group for users
However, that was a question PCR - I'm not sure whether anything is
actually being fixed (it may be). But the best thing is to contact
customer support via your usual channel, and reference this.
Andrew.
On Mon, 6 Dec 2004 22:26:33 +0100, "Ulrich Seeling"
<useeling@t-online.removethis.de> wrote:
| Quote: | Hi *,
I made following experience when trying to use Sun Gridengine via LBS for
distributed analysis:
Even SGE is configured correctly so that it used the effective group id of
the user submitting the job it seems that the LBS daemon does not transfer
this information correct (IC5.0.33).
So if user U with default group g1 switches to group g2 and executes spectre
via LBS (which puts the job into sge), the result files have the ownership
of U with group g1 instead of g2. That can cause problems in an environment
where project access is done via unix group membership ...
Can somebody confirm or negate this behaviour ?
(Anybody using LBS and using unix group id switching ?)
regards
Ulrich
|
|
|
| Back to top |
|
 |
Ulrich Seeling
Guest
|
Posted:
Thu Dec 09, 2004 1:56 am Post subject:
Re: Problems with unix group within LBS (for distributed ana |
|
|
Hi Andrew,
thanks for your pointer to the PCR.
I contacted customer support and there has been no progress in this issue.
Unfortunaty on another PCR, which would make this one obsolete I hope, the
full integration of SGE in distributed analysis, there has no progress too.
These items are only P1...
I estimate it to need another 6-12 months to have the SGE integration done.
Thanks
Ulrich
"Andrew Beckett" <andrewb@DcEaLdEeTnEcTe.HcIoSm> schrieb im Newsbeitrag
news:cjedr018p8bh0oldhanbqplji4ejd32e5r@4ax.com...
| Quote: | A similar problem was reported recently by one of our large German
customers - the issue is that cdsqmgr doesn't preserve the primary group
in the submitted job.
I suggest you contact customer support, and then we can tie you in with
the PCR for this:
PCR: 754666
Title: cdsqmgr change unix group for users
However, that was a question PCR - I'm not sure whether anything is
actually being fixed (it may be). But the best thing is to contact
customer support via your usual channel, and reference this.
Andrew.
On Mon, 6 Dec 2004 22:26:33 +0100, "Ulrich Seeling"
useeling@t-online.removethis.de> wrote:
Hi *,
I made following experience when trying to use Sun Gridengine via LBS for
distributed analysis:
Even SGE is configured correctly so that it used the effective group id of
the user submitting the job it seems that the LBS daemon does not transfer
this information correct (IC5.0.33).
So if user U with default group g1 switches to group g2 and executes
spectre
via LBS (which puts the job into sge), the result files have the ownership
of U with group g1 instead of g2. That can cause problems in an
environment
where project access is done via unix group membership ...
Can somebody confirm or negate this behaviour ?
(Anybody using LBS and using unix group id switching ?)
regards
Ulrich
|
|
|
| Back to top |
|
 |
|
|
|
|