[GE users] SGE questions

Reuti reuti at staff.uni-marburg.de
Fri Mar 2 18:27:20 GMT 2007


    [ The following text is in the "WINDOWS-1252" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some special characters may be displayed incorrectly. ]

Am 02.03.2007 um 18:48 schrieb john.li at mindspeed.com:

>
> Hi Mark,
>
> We run many simulation jobs and each one of them would generates  
> thousands of files.
> Using epilog script or using cron jobs to change the permission are  
> all work arounds to
> me.   I'd like to see the files are generated with the proper  
> permission when they are
> created.

For files besides the STDOUT/ERR you can issue an umask command in  
the jobscript as usual to get the desired permissions. Another option  
is setting a proper ACL for the directory with setfacl with a default  
ACL.

-- Reuti


> Thanks,
>
>
>
>
>
> "Olesen, Mark" <Mark.Olesen at arvinmeritor.com>
> 03/02/07 08:57 AM
> Please respond to
> users at gridengine.sunsource.net
>
>
> To
> "'users at gridengine.sunsource.net'" <users at gridengine.sunsource.net>
> cc
> Subject
> RE: [GE users] SGE questions
>
>
>
>
>
> Hi John,
> > This permission issue is not just limited to STDOUT and STDERR.    
> The
> problem is if a job
> > is submitted as -b y, any output the job generates will have a file
> permission of 644.
> > Ideally, I'd like to be able to use any umask to manage output file
> permission.
>
> I understand what you mean about umask, but isn't it much more  
> reliable to
> explicitly conduct a chmod within the epilog script? This would be  
> similar
> to what the cron job is doing, but could be limited to the job  
> directory.
> Even when the files are to be shared within the same group, I would
> personally have a very bad feeling about having group write  
> permissions on
> input files of running jobs.
>
> /mark
>
> This e-mail message and any attachments may contain legally  
> privileged, confidential or proprietary Information, or information  
> otherwise protected by law of ArvinMeritor, Inc., its affiliates,  
> or third parties. This notice serves as marking of its  
> ?Confidential? status as defined in any confidentiality agreements  
> concerning the sender and recipient. If you are not the intended  
> recipient(s), or the employee or agent responsible for delivery of  
> this message to the intended recipient(s), you are hereby notified  
> that any dissemination, distribution or copying of this e-mail  
> message is strictly prohibited. If you have received this message  
> in error, please immediately notify the sender and delete this e- 
> mail message from your computer.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list