Re: Re[2]: ~/.bashrc not sourced for ssh commands on Archlinux

2013-04-23 Thread Pierre Gaston
On Wed, Apr 24, 2013 at 9:15 AM, Ilya Basin wrote: > ** > > > > > > > > > > On Wed, Apr 24, 2013 at 7:31 AM, Ilya Basin wrote: > > > Hi. > > > $ cat ~/.bashrc > > # > > # ~/.bashrc > > # > > echo Im in .bashrc >&2 > > > RHEL 6.0, bash 4.1.2 > > $ ssh localhost 'ps -f $$ &

Re[2]: ~/.bashrc not sourced for ssh commands on Archlinux

2013-04-23 Thread Ilya Basin
> On Wed, Apr 24, 2013 at 7:31 AM, Ilya Basin <[1]basini...@gmail.com> wrote: Hi. $ cat ~/.bashrc # # ~/.bashrc # echo Im in .bashrc >&2 RHEL 6.0, bash 4.1.2 $ ssh localhost 'ps -f $$ && true' Im in .bashrc

Re: ~/.bashrc not sourced for ssh commands on Archlinux

2013-04-23 Thread Pierre Gaston
On Wed, Apr 24, 2013 at 7:31 AM, Ilya Basin wrote: > Hi. > > $ cat ~/.bashrc > # > # ~/.bashrc > # > echo Im in .bashrc >&2 > > RHEL 6.0, bash 4.1.2 > $ ssh localhost 'ps -f $$ && true' > Im in .bashrc > UIDPID PPID C STIME TTY STAT TIME CMD >

~/.bashrc not sourced for ssh commands on Archlinux

2013-04-23 Thread Ilya Basin
Hi. $ cat ~/.bashrc # # ~/.bashrc # echo Im in .bashrc >&2 RHEL 6.0, bash 4.1.2 $ ssh localhost 'ps -f $$ && true' Im in .bashrc UIDPID PPID C STIME TTY STAT TIME CMD git 22295 22294 0 08:29 ?Ss 0:00 bash -c ps -f $$ && true

Re: RFE: capture command AND output for display and/or redirection

2013-04-23 Thread Eric Blake
On 04/23/2013 01:07 PM, todd@gmail.com wrote: > Guys, I found the part in the manual about submitting bugs but not requests > for enhancement. If this is not the right place, let me know. A missing feature is merely a different form of bug, so yes, this is the right place. > > Enhancement R

RFE: capture command AND output for display and/or redirection

2013-04-23 Thread todd . dsm
Guys, I found the part in the manual about submitting bugs but not requests for enhancement. If this is not the right place, let me know. Enhancement Request: Bash could use a standardized method of capturing a command AND its output for display in the terminal and/or redirection (to wherever, f

Obsolete SIGRTMAX-n signal names

2013-04-23 Thread Harald Hoyer
As reported in http://savannah.gnu.org/patch/?8025 , I would like to see the SIGRTMAX-n signal names disappear. Signals should never ever be addressed with SIGRTMAX-n. Signals should always be addressed with SIGRTMIN+n. http://man7.org/linux/man-pages/man7/signal.7.html [...] programs should neve