Hello Tycho!
> the login shell detection (leading dash: -bash) is apparently broken - at
> least, ~/.bashrc is not sourced.
As far as I understand the manual ~/.bashrc is not sourced from a login-shell,
see https://www.gnu.org/software/bash/manual/bash.html#Bash-Startup-Files
At
On Thu, Mar 16, 2023 at 05:21:23PM +0100, Tycho Kirchner wrote:
> Hi,
> when compiling bash with a plain
>
> mkdir build; cd build; ../configure && make
>
> the login shell detection (leading dash: -bash) is apparently broken - at
> least, ~/.bashrc is not so
Hi,
when compiling bash with a plain
mkdir build; cd build; ../configure && make
the login shell detection (leading dash: -bash) is apparently broken - at
least, ~/.bashrc is not sourced.
This happens in all tested versions, from 4.4 until the latest release 5.2.15.
Interestingl
On 2010-08-24 15:59 , Chet Ramey wrote:
Well, if they cause bash to crash, I suppose removing that code (or
removing the #define) is a good place to start.
That code has been there for a very long time. Maybe if you changed it
to turn on the FD_CLOEXEC bit instead of closing the fd we could
On 8/22/10 10:13 PM, Rainer Müller wrote:
Bash Version: 4.1
Patch Level: 7
Release Status: release
I cannot reproduce this very good, but it happens for me now with
iTerm.app and '/opt/local/bin/bash -l' as command. A crash report is
attached to this message.
The important part of
Hi,
I am the maintainer of bash in MacPorts, a package management system for
Mac OS X. I am currently debugging crashes with bash 4.1.7 when being
run as a login shell under certain conditions. The original report was
here: http://trac.macports.org/ticket/25693
Configuration Information
Hi,
I am the maintainer of bash in MacPorts, a package management system for
Mac OS X. I am currently debugging crashes with bash 4.1.7 when being
run as a login shell under certain conditions. The original report was
here: http://trac.macports.org/ticket/25693
Configuration Information
I make my ~/.bash_profile empty. I still see
$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
I checked /etc/profile and /etc/bash.bashrc. But I don't PATH is set
in the two files. I'm wondering from which file PATH is set. BTW, my
system is ubuntu.
Peng Yu wrote:
I make my ~/.bash_profile empty. I still see
$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
I checked /etc/profile and /etc/bash.bashrc. But I don't PATH is set
in the two files. I'm wondering from which file PATH is set. BTW, my
Peng Yu wrote:
I make my ~/.bash_profile empty. I still see
$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
What is in your ~/.bashrc file?
I checked /etc/profile and /etc/bash.bashrc. But I don't PATH is set
in the two files. I'm wondering from which
On Tue, Nov 17, 2009 at 3:12 PM, Bob Proulx b...@proulx.com wrote:
Peng Yu wrote:
I make my ~/.bash_profile empty. I still see
$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
What is in your ~/.bashrc file?
I checked /etc/profile and /etc/bash.bashrc.
i was going through the new features list in NEWS to see what cool things are
in here and i saw the new checkjobs option. is it just me or does this cause
a non-login bash to crash at exit which leads to an infinite loop / cpu
churning ?
$ gdb bash
(gdb) r
vap...@vapier 0:0 bash-4.0 $ shopt
Mike Frysinger wrote:
i was going through the new features list in NEWS to see what cool things are
in here and i saw the new checkjobs option. is it just me or does this cause
a non-login bash to crash at exit which leads to an infinite loop / cpu
churning ?
I can't reproduce this. Do
On Monday 23 February 2009 18:05:26 Chet Ramey wrote:
Mike Frysinger wrote:
i was going through the new features list in NEWS to see what cool things
are in here and i saw the new checkjobs option. is it just me or does
this cause a non-login bash to crash at exit which leads to an
Mike Frysinger wrote:
On Monday 23 February 2009 18:05:26 Chet Ramey wrote:
Mike Frysinger wrote:
i was going through the new features list in NEWS to see what cool things
are in here and i saw the new checkjobs option. is it just me or does
this cause a non-login bash to crash at exit which
On Monday 23 February 2009 23:00:31 Chet Ramey wrote:
Mike Frysinger wrote:
On Monday 23 February 2009 18:05:26 Chet Ramey wrote:
Mike Frysinger wrote:
i was going through the new features list in NEWS to see what cool
things are in here and i saw the new checkjobs option. is it just me
In an interative shell, what is the easiest way to tell whether it is a login
shell or not? Thanks.
--
View this message in context:
http://www.nabble.com/login-shell-or-not--tf3211932.html#a8919535
Sent from the Gnu - Bash mailing list archive at Nabble.com
peter360 wrote:
In an interative shell, what is the easiest way to tell whether it is a login
shell or not? Thanks.
In sufficiently modern versions of bash (basically anything newer than
bash-2.05), you can test the setting of the `login_shell' shopt variable.
The shell sets it automatically
18 matches
Mail list logo
