Using version GNU parallel 20160222
Currently, sqlmaster appears to populate a table, first dropping any
existing table, and waits for jobs to complete. Wondering if there is a
way to:
1. populate the database then exit immediately without waiting?
My particular use case is parallelizing backup
On Tue, Dec 6, 2016 at 6:10 PM, Andy Loftus wrote:
> Currently, sqlmaster appears to populate a table, first dropping any
> existing table, and waits for jobs to complete. Wondering if there is a way
> to:
>
> 1. populate the database then exit immediately without waiting?
> My particular use ca
On Wed, Nov 23, 2016 at 5:23 AM, Pierre Poujade wrote:
> Hi,
>
> I wanted to see how parallel behaves when one of the hosts is down.
> root@nope is down (host doesn't exist on the network and won't resolve),
> scanner-helper is up and running.
>
> $ parallel --controlmaster --filter-hosts --eta -j
On Tue, Dec 6, 2016 at 4:54 PM Ole Tange wrote:
> On Tue, Dec 6, 2016 at 6:10 PM, Andy Loftus wrote:
>
> > Currently, sqlmaster appears to populate a table, first dropping any
> > existing table, and waits for jobs to complete. Wondering if there is a
> way
> > to:
> >
> > 1. populate the datab
On Thu, Nov 17, 2016 at 10:24 PM, Larry Ploetz wrote:
> Don't know if this really qualifies as a bug, but there were too many open
> files on my MacOS system, which resulted in parallel doing:
>
> Couldn't open /dev/null: Too many open files in system
> parallel: This should not happen. You have