On 2013-03-18 15:44, Mike Frysinger wrote:
On Monday 18 March 2013 14:17:42 Joshua Judson Rosen wrote:
`luckily', the other popular bourne shells (e.g.: bash, dash/ash, ksh) seem
to all actually behave contrary to POSIX on this matter; portable scripts
already have to do ". $file || exit" if the
From: Jonh Wendell
Currently we are ignoring the '-l' command line with
regards to remote logging. We're sending all logs to
the remote machine.
This patch makes remote logging behave just like local
logging by honoring the '-l' flag.
Signed-off-by: Jonh Wendell
---
sysklogd/syslogd.c | 87
On Monday 18 March 2013 14:17:42 Joshua Judson Rosen wrote:
> `luckily', the other popular bourne shells (e.g.: bash, dash/ash, ksh) seem
> to all actually behave contrary to POSIX on this matter; portable scripts
> already have to do ". $file || exit" if they actually want the POSIX
> behaviour...
On Monday 18 March 2013 05:37:10 walter harms wrote:
> Am 18.03.2013 10:09, schrieb Bastian Bittorf:
> > * Joshua Judson Rosen [18.03.2013 09:58]:
> >> failure to dot/source a file can still result in an error-message
> >> without making the shell quit. In order to do that, I had to slightly
> >>
Hi !
>> No, it already reads /etc/profile before setting HISTFILE. But it
>> doesn't read $HOME/.profile at all, should I send a patch to bring it
>> in line with ash and other shells?
The idea behind this is, that /etc/profile may source $HOME/.profile if
this is required, e.g.
# somewhere at t
On 2013-03-18 14:37, Bastian Bittorf wrote:
* Joshua Judson Rosen [18.03.2013 19:32]:
[ -e "$file" ]&& . "$file"
not ok for you? my usecase was more a "speed" issue, because
The only technical reason against that is the race condition if $file is
deleted after the existence/read check.
Y
On 2013-03-18 14:17, Joshua Judson Rosen wrote:
`luckily', the other popular bourne shells (e.g.: bash, dash/ash, ksh) seem to
all actually behave contrary to POSIX on this matter;
Ugh--I take it back about dash/ash--dash/ash actually behave according
to POSIX, here. :\
I was running a script
On Fri, Mar 15, 2013 at 10:02 AM, Stefan Hellermann
wrote:
>> Does hush also suffer from this?
>>
>
> No, it already reads /etc/profile before setting HISTFILE. But it
> doesn't read $HOME/.profile at all, should I send a patch to bring it
> in line with ash and other shells?
No one yet asked for
* Joshua Judson Rosen [18.03.2013 19:32]:
> >>[ -e "$file" ]&& . "$file"
> >>
> >>not ok for you? my usecase was more a "speed" issue, because
> >
> >The only technical reason against that is the race condition if $file is
> >deleted after the existence/read check.
>
> Yes. And there's no way to
On 2013-03-18 05:38, Bernd Petrovitsch wrote:
Hi!
On Mon, 2013-03-18 at 10:09 +0100, Bastian Bittorf wrote:
* Joshua Judson Rosen [18.03.2013 09:58]:
failure to dot/source a file can still result in an error-message without
making the shell quit. In order to do that, I had to slightly adjust
On Sun, Feb 24, 2013 at 11:45 PM, Aaro Koskinen wrote:
> When adding To: header, add only a single header. If there are multiple
> addresses, make it multiline.
>
> Signed-off-by: Aaro Koskinen
Applied all patches, thanks!
Please try current git.
___
Cathey, Jim wrote:
So if I should type, manually, ". oopsImisspelledIt"
my session is supposed to go away?
No, only an non-interactive shell is supposed to exit.
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/
So if I should type, manually, ". oopsImisspelledIt"
my session is supposed to go away?
Not cool.
-- Jim
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
Hi!
On Mon, 2013-03-18 at 10:09 +0100, Bastian Bittorf wrote:
> * Joshua Judson Rosen [18.03.2013 09:58]:
> > failure to dot/source a file can still result in an error-message without
> > making the shell quit. In order to do that, I had to slightly adjust
>
> somebody posted a link to the posix
Am 18.03.2013 10:09, schrieb Bastian Bittorf:
> * Joshua Judson Rosen [18.03.2013 09:58]:
>> failure to dot/source a file can still result in an error-message without
>> making the shell quit. In order to do that, I had to slightly adjust
>
> somebody posted a link to the posix-standard, where
* Joshua Judson Rosen [18.03.2013 09:58]:
> failure to dot/source a file can still result in an error-message without
> making the shell quit. In order to do that, I had to slightly adjust
somebody posted a link to the posix-standard, where explicity is
written, a shell must abort when a '. $file
16 matches
Mail list logo