From: Adam Dinwoodie <adam@dinwoodie.org>
To: "Cygwin (cygwin@cygwin.com)" <cygwin@cygwin.com>
Subject: Re: login shell binary outside of /bin
Date: Thu, 1 Jul 2021 08:49:20 +0100 [thread overview]
Message-ID: <CA+kUOam_EVMjYTMwty7Pk_pO_A=pJNEV+fV6q3OorYkATwMrpQ@mail.gmail.com> (raw)
In-Reply-To: <8aadfa42-225f-9d8e-4335-e1e6912202f7@gmail.com>
On Thu, 1 Jul 2021 at 08:30, Basin Ilya via Cygwin <cygwin@cygwin.com> wrote:
> Hi
> I compiled bash 5.1 and installed it to /usr/local
>
> If I try to use it as a login shell it fails to launch programs while sourcing /etc/profile. If I copy the binary to /bin it works. If after successful login I launch `/usr/local/bin/bash5 -login` again it works. If I copy the official bash4 to /usr/local/bin and try to do the initial login it fails just like bash5.
>
> Bad:
>
> C:\cygwin\bin>C:\cygwin\usr\local\bin\bash5 -login
> 0 [main] bash5 674 dofork: child -1 - forked process 20540 died unexpectedly, retry 0, exit code 0xC0000135, errno 11
> bash5: fork: retry: Resource temporarily unavailable
> <snip>
Hello! First of all, have you tried working through the section on
fork problems in the FAQ below? That is normally the way to sort these
issues.
> FAQ: https://cygwin.com/faq/
If you've gone through all those steps, it would be useful to know
exactly how you compiled Bash, including where you got the source code
and what commands and tools you used to do the compilation, as well as
the cygcheck output specified in the Problem reports documentation as
below:
> Problem reports: https://cygwin.com/problems.html
prev parent reply other threads:[~2021-07-01 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 6:53 Basin Ilya
2021-07-01 7:49 ` Adam Dinwoodie [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+kUOam_EVMjYTMwty7Pk_pO_A=pJNEV+fV6q3OorYkATwMrpQ@mail.gmail.com' \
--to=adam@dinwoodie.org \
--cc=cygwin@cygwin.com \
/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).