unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: Eric Bavier <ericbavier@centurylink.net>
Cc: help-guix@gnu.org
Subject: Re: Problems with GNU Parallel and ulimit
Date: Thu, 17 Aug 2017 20:30:43 +0530	[thread overview]
Message-ID: <4a4226ea.AEAAOgSM9JoAAAAAAAAAAAPHPkIAAAACwQwAAAAAAAW9WABZla-q@mailjet.com> (raw)
In-Reply-To: <20170814235837.0a42fe85@centurylink.net>


Eric Bavier writes:

> The problem appears if you do not have 'perl' available in $PATH. GNU
> parallel calls it recursively for a few tasks:

This is correct. I have verified it. When I have perl in my PATH, GNU
parallel works fine.

> There is some path patching that goes on in the package recipe, but it
> must have gone out of sync in latest versions.  The 'post-install-test'
> phase wouldn't catch this particular error without '(setenv "PATH" "")'.
>
> I wouldn't feel quite comfortable doing a "blind" update of the regex,
> since some mentions of "perl" I think are meant to be executed by
> remote hosts and so shouldn't be patched to absolute store references.

Why does parallel need to execute perl on remote hosts?

> It might be useful to get Ole's opinion on this.

Yes, could you please do this?

Thanks!

  reply	other threads:[~2017-08-17 15:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15  4:58 Problems with GNU Parallel and ulimit Eric Bavier
2017-08-17 15:00 ` Arun Isaac [this message]
2018-06-21 22:55 ` Clément Lassieur
2018-08-11 10:04   ` Arun Isaac
  -- strict thread matches above, loose matches on Subject: below --
2017-08-15  4:41 ericbavier
2017-08-14  2:31 Arun Isaac
2017-08-14  2:46 ` Ben Woodcroft
2017-08-14 16:14   ` Leo Famulari
2017-08-14 18:44     ` Arun Isaac
2017-08-14 19:16       ` Marius Bakke
2017-08-14 20:07       ` myglc2

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4a4226ea.AEAAOgSM9JoAAAAAAAAAAAPHPkIAAAACwQwAAAAAAAW9WABZla-q@mailjet.com \
    --to=arunisaac@systemreboot.net \
    --cc=ericbavier@centurylink.net \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).