On Sat, Dec 12, 2015 at 9:19 PM, Ryan Brothers wrote:
> When using --return, files copied back to the local machine are placed
> in the current working directory such as in the below:
>
> parallel -S $SERVER1 --return {}.out --cleanup echo {} ">"{}.out ::: a
>
> Is it possible to set the output di
On Sat, Dec 12, 2015 at 5:10 PM, Ryan Brothers wrote:
> When using --joblog and --files such as in the below, is it possible
> to have the joblog include the path to the output file for each job?
>
> parallel --tmpdir /var/tmp --files --joblog joblog.txt echo ::: A B C
>
> I am writing a script t
On Fri, Dec 11, 2015 at 11:16 PM, Josef wells
wrote:
> Normal operation of parallel seems to use ~/.parallel/tmp in some
> cases this is a long-distance network drive for me.. I'm unclear on
> exactly what goes here, the files mostly look like
> "linelen-".
>
> Is there a way to relocate this area
On Wed, Dec 9, 2015 at 7:30 PM, Brian McQueen wrote:
> When getting a list of IPs from an API, I've been using sed something like
> this:
>
> getIpsFromAPI -env myEnv | sed 's/^/thisUser@/' | parallel --tag --nonall -S
> - shell command
>
> It would be nice to have a cli option to work this way:
>
On Wed, Dec 9, 2015 at 7:25 PM, Brian McQueen wrote:
> Yea, this works well:
>
> oo -a npm-lb -e npr -p npm | parallel --tag --nonall -S - --basefile
> ./dev.sh ./dev.sh
>
> I had a look at the code and it looks like there's a bit of a learning curve
> to get a patch going if its beyond the trivi
