From: Michael Albinus <michael.albinus@gmx.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 33781@debbugs.gnu.org
Subject: bug#33781: tramp tests abort on hydra
Date: Thu, 20 Dec 2018 11:16:46 +0100 [thread overview]
Message-ID: <87sgysa4fl.fsf@gmx.de> (raw)
In-Reply-To: <87efad1cjt.fsf@igel.home> (Andreas Schwab's message of "Wed, 19 Dec 2018 21:33:58 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
>> Yes, I could reproduce it. The problem is, that there is an upper limit
>> to the length of the $PATH variable, to be checked by
>>
>> # getconf PATH_MAX /
>
> PATH_MAX has nothing to do with $PATH.
Yes, PATH_MAX by definition is the maximum length of a file path. But I
still have the feeling it is also involved in setting the $PATH
environment variable. As Glenn did report, there are problems on hydra
when setting $PATH to a string longer than 4096 characters. It doesn't
seem to be related to the shell limit of input lines; Glenn reported
that 'getconf LINE_MAX' returns 2048.
> Andreas.
Best regards, Michael.
next prev parent reply other threads:[~2018-12-20 10:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 19:16 bug#33781: tramp tests abort on hydra Glenn Morris
2018-12-17 19:36 ` Michael Albinus
2018-12-18 1:05 ` Glenn Morris
2018-12-18 1:37 ` Glenn Morris
2018-12-18 2:23 ` Glenn Morris
2018-12-18 7:06 ` Glenn Morris
2018-12-18 13:21 ` Michael Albinus
2018-12-18 18:29 ` Glenn Morris
2018-12-18 19:52 ` Michael Albinus
2018-12-18 20:49 ` Glenn Morris
2018-12-19 19:53 ` Michael Albinus
2018-12-19 20:33 ` Andreas Schwab
2018-12-20 10:16 ` Michael Albinus [this message]
2018-12-20 17:25 ` Andreas Schwab
2018-12-20 20:50 ` Michael Albinus
2018-12-21 8:25 ` Andreas Schwab
2018-12-21 12:55 ` Michael Albinus
2018-12-20 17:46 ` Glenn Morris
2018-12-20 21:06 ` Michael Albinus
2018-12-19 21:50 ` Glenn Morris
2018-12-20 10:19 ` Michael Albinus
2018-12-19 22:10 ` Glenn Morris
2018-12-18 13:09 ` Michael Albinus
2018-12-18 18:27 ` Glenn Morris
2018-12-18 19:33 ` Michael Albinus
2018-12-18 20:47 ` Glenn Morris
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgysa4fl.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=33781@debbugs.gnu.org \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).