Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/11/17 2:58 PM, Greg Wooledge wrote: > If the goal is ONLY to configure the environment that appears within > an interactive shell, then you can short circuit the DM/DE/WM > configuration steps and simply tell the terminal emulator to run > login shells instead of regular shells. Yes, I'm

Re: ~/.profile and ~/.bash_profile aren't executed on login

On Mon, Dec 11, 2017 at 01:57:52PM -0500, Chet Ramey wrote: > On 12/11/17 1:30 PM, Yuri wrote: > > /usr/local/bin/bash is set as user's login shell in 'vipw'. So when this > > user logs in, it must be invoked as a login shell. Is this correct? > > Nobody on the list can answer that question. It

Re: ~/.profile and ~/.bash_profile aren't executed on login

On Mon, Dec 11, 2017 at 10:30:51AM -0800, Yuri wrote: > On 12/11/17 06:03, Chet Ramey wrote: > /usr/local/bin/bash is set as user's login shell in 'vipw'. So when this > user logs in, it must be invoked as a login shell. Is this correct? No. Because you are logging in with a Display Manager, not

Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/11/17 06:03, Chet Ramey wrote: Bash, as documented, reads ~/.bash_profile first when it's invoked as a login shell, falling back to ~/.bash_login and ~/.profile if it's not there. I just verified: none of these 3 files are executed by bash when user logs in. /usr/local/bin/bash is

Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/10/17 10:22 PM, Yuri wrote: > On 12/10/17 13:51, Chet Ramey wrote: >> You have not described a bug, since you have not demonstrated that bash is >> behaving other than how it is documented, nor have you provided answers to >> any of the questions you've been asked. You haven't even

Re: ~/.profile and ~/.bash_profile aren't executed on login

On Sun, Dec 10, 2017 at 07:22:36PM -0800, Yuri wrote: > It only calls ~/.profile when it is named 'sh'. In posix mode, bash only looks for ~/.profile, but when you run it in non-posix mode, it will look for ~/.bash_profile and ~/.bash_login first. You probably have a ~/.bash_profile in addition

Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/10/17 13:51, Chet Ramey wrote: You have not described a bug, since you have not demonstrated that bash is behaving other than how it is documented, nor have you provided answers to any of the questions you've been asked. You haven't even determined whether or not bash is being invoked as a

Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/10/17 3:18 PM, Yuri wrote: > On 12/09/17 14:14, Yuri wrote: >> None of these files are executed when bash is a user's default shell on >> FreeBSD. >> No special options were selected. Despite shell.c saying that they should >> be executed they just aren't. > > > The bug is that bash

Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/09/17 14:14, Yuri wrote: None of these files are executed when bash is a user's default shell on FreeBSD. No special options were selected. Despite shell.c saying that they should be executed they just aren't. The bug is that bash doesn't handle login situation when it isn't linked to

Re: ~/.profile and ~/.bash_profile aren't executed on login

Yuri wrote: > Bob Proulx wrote: > > How is the user logging in? Are they logging in with 'ssh' over the > > network? Or are they logging in through an "xdm" X Display Manager > > login from a graphical login display? > > User logs in locally through the display manager. Which graphical display

Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/9/17 6:41 PM, Yuri wrote: > On 12/09/17 15:24, Chet Ramey wrote: >> Of course not: that's not a login shell.  As the documentation says, >> >> "A login shell is one whose first character of argument zero is a -,  or >> one started with the --login option." >> >> The INVOCATION section of the

Re: ~/.profile and ~/.bash_profile aren't executed on login

On Sun, Dec 10, 2017 at 1:41 AM, Yuri wrote: > On 12/09/17 15:24, Chet Ramey wrote: > >> Of course not: that's not a login shell. As the documentation says, >> >> "A login shell is one whose first character of argument zero is a -, or >> one started with the --login option." >>

Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/09/17 15:24, Chet Ramey wrote: Of course not: that's not a login shell. As the documentation says, "A login shell is one whose first character of argument zero is a -, or one started with the --login option." The INVOCATION section of the manual page explains it in exhaustive detail.

Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/9/17 6:09 PM, Yuri wrote: > On 12/09/17 15:01, Chet Ramey wrote: >> Since it doesn't happen on any other OS, I suspect an issue with either the >> FreeBSD port or the pathname that appears in argv[0] when the shell is >> started, which is what bash uses to detect that it's been invoked as a

Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/09/17 15:01, Chet Ramey wrote: Since it doesn't happen on any other OS, I suspect an issue with either the FreeBSD port or the pathname that appears in argv[0] when the shell is started, which is what bash uses to detect that it's been invoked as a login shell. The full path is

Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/09/17 14:59, Bob Proulx wrote: How is the user logging in? Are they logging in with 'ssh' over the network? Or are they logging in through an "xdm" X Display Manager login from a graphical login display? User logs in locally through the display manager. Yuri

Re: ~/.profile and ~/.bash_profile aren't executed on login

On 12/9/17 5:14 PM, Yuri wrote: > None of these files are executed when bash is a user's default shell on > FreeBSD. > No special options were selected. Despite shell.c saying that they should > be executed they just aren't. > > Is this a bug? Since it doesn't happen on any other OS, I suspect

Re: ~/.profile and ~/.bash_profile aren't executed on login

Yuri wrote: > None of these files are executed when bash is a user's default shell on > FreeBSD. > No special options were selected. Despite shell.c saying that they should be > executed they just aren't. How is the user logging in? Are they logging in with 'ssh' over the network? Or are they