[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Condor-users] condor_submit wrapper

I am running condor 6.7.7 and using group quotas on my condor cluster. Most jobs are submitted to this cluster using the Globus GRAM interface and I have hacked the condor.pm to add a +AccountingGroup = "group_<group>.<user>" to the classad of all incoming jobs from the grid. This has been working fine. (Note that the names of the accounting groups on my system correspond to the unix group names of the users in the passwd file).

I am now trying to do the same for local jobs.  I've written
the following perl wrapper for condor_submit, which successfully
does submit the job to the local schedd and put it in the correct
accounting group.  It is grabbing the username and groupname
of the user on the fly.

[root@fngp-osg bin]# cat condor_submit_wrap.pl #!/export/osg/grid/vdt/bin/perl my $realusername = (getpwuid($<))[0]; my $realgroupname = (getgrgid($())[0]; my $groupstring = "+AccountingGroup = \"group_$realgroupname.$realusername\""; my $systemstring = "/export/osg/grid/condor/bin/condor_submit_real -a '$groupstring' @ARGV "; system ($systemstring);

---------------- But when I put this perl wrapper in the place of condor_submit and rename the condor_submit binary to condor_submit_real, all sorts of wierd things happen. So--the first question-- should any such wrapper to condor_submit be returning the return code of the real condor_submit binary, and if so, how would this be done. Second question, is there anything else obvious I'm missing?


Steve Timm

Steven C. Timm, Ph.D  (630) 840-8525  timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team