On 2015-08-10 10:19 PM, Chet Ramey wrote:
On 8/9/15 1:37 PM, aixtools wrote:
Hi,
Via google I came across the define named
config-top.h:/* #define SYSLOG_HISTORY */
Changing it (manually) to
config-top.h:#define SYSLOG_HISTORY
Adds syslog statements such as:
Aug 9 16:52:55 x064 user:info sy
On 2015-08-03 3:40 PM, Chet Ramey wrote:
On 8/2/15 8:50 PM, Steve Dahl wrote:
If on AIX 6.1, I mount an NFS volume exported from CentOS 6.7, Bash
(4.3.30) is unable to do tab completion within that file system. If (for
example) I search for files that I know exist, such as:
ls -l /path/to/
On 2015-08-12 12:38 PM, aixtools wrote:
On 2015-08-03 3:40 PM, Chet Ramey wrote:
On 8/2/15 8:50 PM, Steve Dahl wrote:
If on AIX 6.1, I mount an NFS volume exported from CentOS 6.7, Bash
(4.3.30) is unable to do tab completion within that file system. If
(for
example) I search for files that I
In article ,
aixtools wrote:
>In short, having it included in ./configure simply give it much more
>visibility - and perhaps adoption.
Personally, I think that having bash send executed commands to syslog
is an invasion of privacy; I'm surprised such a feature is even there
at all...
My two ce
On Wed, Aug 12, 2015 at 7:09 AM, Aharon Robbins wrote:
> In article ,
> aixtools wrote:
> >In short, having it included in ./configure simply give it much more
> >visibility - and perhaps adoption.
>
> Personally, I think that having bash send executed commands to syslog
> is an invasion of pri
On Wed, Aug 12, 2015 at 08:00:24AM -0500, John McKown wrote:
> Case 2: I'm running bash on my employer's system???. Do I really have an
> expectation of privacy on my employer's system? Why would I?
In some countries, yes, there is such an expectation. Logging your
employees' activities may or ma
On 8/12/15 6:38 AM, aixtools wrote:
> /*
> * define _LARGE_FILES needs to be first so that all the include files know
> that
> */
> #ifdef _AIX
> #define _LARGE_FILES
> #endif
That define is in config.h and should be set by the AC_SYS_LARGEFILE
autoconf macro. If it's not working on AIX I woul
On 8/12/15 6:31 AM, aixtools wrote:
> In short, having it included in ./configure simply give it much more
> visibility - and perhaps adoption.
Don't assume that wide adoption of this feature is a goal.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa,
On 8/12/15 8:09 AM, Aharon Robbins wrote:
> In article ,
> aixtools wrote:
>> In short, having it included in ./configure simply give it much more
>> visibility - and perhaps adoption.
>
> Personally, I think that having bash send executed commands to syslog
> is an invasion of privacy; I'm sur
On 2015-08-12 3:19 PM, Chet Ramey wrote:
On 8/12/15 8:09 AM, Aharon Robbins wrote:
In article,
aixtools wrote:
In short, having it included in ./configure simply give it much more
visibility - and perhaps adoption.
Personally, I think that having bash send executed commands to syslog
is an in
Bash segfaults when trying to do this: x=-3; echo ${!x}
Here's the backtrace from gdb: https://gist.github.com/306f16a358527b267a1e
It looks like the problem is the savestring macro when ind is negative.
---
xoxo iza
On 8/12/15 3:52 PM, isabella parakiss wrote:
> Bash segfaults when trying to do this: x=-3; echo ${!x}
> Here's the backtrace from gdb: https://gist.github.com/306f16a358527b267a1e
> It looks like the problem is the savestring macro when ind is negative.
Thanks for the report. This will be fixed
This segfaults when it receives a SIGUSR1:
#!/bin/bash
trap ': $(:) < <(:)' USR1
while :; do sleep 1; done
I also received a bunch of scary errors like these:
*** Error in `/bin/bash': munmap_chunk(): invalid pointer:
0x02680f80 ***
*** Error in `/bin/bash': corrupted double-linked list:
1. If the function is complicated and contains lots of commands, it
would be more troublesome appending && to every command rather
than simply using one single "set -e" at the front.
2. It is not
reasonable that suppression of '-e' is applied as well inside the
function. My intention is if my
On 08/12/2015 09:54 PM, PRC wrote:
> 1. If the function is complicated and contains lots of commands, it
> would be more troublesome appending && to every command rather
> than simply using one single "set -e" at the front.
> 2. It is not
> reasonable that suppression of '-e' is applied as wel
On 8/13/15, Eric Blake wrote:
> Like it or not, it is the historical behavior standardized by POSIX. It
> is NOT intuitive, and our advice is "DON'T USE set -e - IT WON'T DO WHAT
> YOU WANT". We can't change the behavior, because it would break scripts
> that rely on the POSIX-specified behavior.
chupilirola
On 10 Aug 2015 16:19, Chet Ramey wrote:
> On 8/9/15 1:37 PM, aixtools wrote:
> > Via google I came across the define named
> >
> > config-top.h:/* #define SYSLOG_HISTORY */
> >
> > Changing it (manually) to
> > config-top.h:#define SYSLOG_HISTORY
> >
> > Adds syslog statements such as:
> > Aug
18 matches
Mail list logo
