Changeset 47 for trunk/oarutils

Timestamp:

Dec 6, 2011, 6:27:18 PM (13 years ago)

Author:

g7moreau

Message:

• Revert --filecmd to --file
• Doc Folder Job

File:

• trunk/oarutils/oar-parexec (modified) (10 diffs)

trunk/oarutils/oar-parexec

@@ -16 +16 @@
 use Cwd qw( getcwd );
 
-my $filecmd  = '';
+my $file  = '';
 my $dir      = '';
 my $cmd      = '';
@@ -29 +29 @@
 
 Getopt::Long::GetOptions(
-   'filecmd=s'  => \$filecmd,
+   'file=s'     => \$file,
    'dir=s'      => \$dir,
    'cmd=s'      => \$cmd,
@@ -43 +43 @@
 pod2usage(-verbose => 2) if $help;
 pod2usage(-verbose => 2) if not (
- (-e "$filecmd")
+ (-e "$file")
  or (-d "$dir" and $cmd ne '')
  );
@@ -68 +68 @@
 # job to run
 my @job = ();
-if (-e "$filecmd") {
+if (-e "$file") {
    my $job_num = 0;
-   open(JOB_LIST, '<', "$filecmd") or die "error: can't open job file $filecmd: $!";
+   open(JOB_LIST, '<', "$file") or die "error: can't open job file $file: $!";
    while (<JOB_LIST>) {
       chomp;
@@ -266 +266 @@
 =head1 SYNOPSIS
 
- oar-parexec --filecmd filecommand [--logtrace tracefile] [--verbose] \
-            [--jobnp integer] [--nodefile filenode] [--oarsh sssh] \
-            [--switchio] [--masterio basefileio]
-
- oar-parexec --dir foldertoitemize --cmd commandtolaunch [--logtrace tracefile] [--verbose] \
-            [--jobnp integer] [--nodefile filenode] [--oarsh sssh] \
-            [--switchio] [--masterio basefileio]
+ oar-parexec --file filecommand \
+    [--logtrace tracefile] [--verbose] \
+    [--jobnp integer] [--nodefile filenode] [--oarsh sssh] \
+    [--switchio] [--masterio basefileio]
+
+ oar-parexec --dir foldertoiterate --cmd commandtolaunch \
+    [--logtrace tracefile] [--verbose] \
+    [--jobnp integer] [--nodefile filenode] [--oarsh sssh] \
+    [--switchio] [--masterio basefileio]
 
  oar-parexec --help
@@ -284 +286 @@
 However, it can be used outside OAR.
 
-Option C<--filecmd> or C<--dir> and C<--cmd> are the only mandatory parameters.
+Option C<--file> or C<--dir> and C<--cmd> are the only mandatory parameters.
 
 Small job will be launch in the same folder as the master job.
@@ -309 +311 @@
 =over 12
 
-=item B<-f|--filecmd filecommand>
+=item B<-f|--file filecommand>
 
 File name which content job list.
@@ -315 +317 @@
 the first valid job in the list will have the number 1 and so on...
 
-=item B<-d|--dir foldertoitemize>
+=item B<-d|--dir foldertoiterate>
 
 Command C<--cmd> will be launch in all sub-folder of this master folder.
 Files in this folder will be ignored.
-Sub-folder name which begin with '.'
-or finish with '.old', '.sav', '.bak', '.no' will either be ignored...
+Sub-folder name which begin with F<.>
+or finish with F<.old>, F<.sav>, F<.bak>, F<.no> will either be ignored...
 
 The JOB_NAME is simply the Sub-folder name.
@@ -394 +396 @@
 =head2 Simple list of sequential job
 
-Content for the job file command (option C<--filecmd>) could have:
+Content for the job file command (option C<--file>) could have:
 
  - empty line
@@ -415 +417 @@
  oarsub -n test -l /core=6,walltime=04:00:00 "oar-parexec -f ./subjob.list.txt"
 
+=head2 Folder job
+
+In a folder F<subjob.d>, create sub-folder with your data inside : F<test1>, <test2>...
+The same command will be executed in every sub-folder.
+C<oar-parexec> change the current directory to the sub-folder before launching it.
+
+A very simple job could be:
+
+ oarsub -n test -l /core=6,walltime=04:00:00 "oar-parexec -d ./subjob.d -c 'sleep 10; env'"
+
+The command C<env> will be excuted in all folder F<test1>, F<test2>... after a 10s pause.
+
+Sometime, it's simpler to use file list command,
+sometime, jobs by folder with the same command run is more relevant.
+
 =head2 Parallel job