> "Rob" == Rob Browning <[EMAIL PROTECTED]> writes:
Rob> "Karl M. Hegbloom" <[EMAIL PROTECTED]> writes:
>> The special thing was to have upgraded to Bash-2.0. I just
>> downgraded to 1.14.7, and the scripts run now. I think we
>> should report this as a Bash bug.
Rob> Ch
"Karl M. Hegbloom" <[EMAIL PROTECTED]> writes:
> The special thing was to have upgraded to Bash-2.0. I just
> downgraded to 1.14.7, and the scripts run now. I think we should
> report this as a Bash bug.
Check to see if you have a "set -a" (or +a) anywhere in your bashrc,
or related bash setup
I only run bash 2.0 on my systems at home.
On Sat, 17 May 1997, Karl M. Hegbloom wrote:
>> "Christoph" == Christoph Lameter <[EMAIL PROTECTED]> writes:
>
>Christoph> I have tested your scripts and everything works just as
>Christoph> it should. Check your system for anything special
> "Christoph" == Christoph Lameter <[EMAIL PROTECTED]> writes:
Christoph> I have tested your scripts and everything works just as
Christoph> it should. Check your system for anything special you
Christoph> might have done.
The special thing was to have upgraded to Bash-2.0. I j
I have tested your scripts and everything works just as it should.
Check your system for anything special you might have done.
work:~$ ./script1
This is ./script1
The value of $- is 'hB'
This is ./script2
The value of $- is 'hB'
If the grep fails, this will never echo.
work:~$ cat script1
#!/bi
> "Christoph" == Christoph Lameter <[EMAIL PROTECTED]> writes:
Christoph> Could you please give me a simple script that produces
Christoph> the error that you have been talking about so long? I
Christoph> have not been able to produce a single instance of the
Christoph> problem
Could you please give me a simple script that produces the error that you
have been talking about so long? I have not been able to produce a single
instance of the problem you are mentioning. Get emacs and all other
complicating circumstances out of it.
Just tell me how to produce the problem and
This works every time, with no fails due to '-o errexit'.
#!/bin/sh
#
# Register a binary
#
function setperm()
{
if [ -e $2 ]; then
chown $3.$4 $2
chmod $5 $2
fi
}
function compperm()
{
if [ $1 != $4 -o $2 != $5 -o $3 != $6 ]; then
It works some times, but not others. Enclosed are scripts of two
trials, one where it functions, from within an XEmacs buffer, and
another where it fails, from an XTerm shell.
The status display comes from a $PROMPT_COMMAND that prints any
non-zero $? before it prints the next prompt.
*** The
I have tried it and set -e is not propagated into a subprocess.
This is the script I ran successfully:
#/!bin/sh
set -e
suidregister /etc/exports clameter clameter 4755
Please investigate what is wrong with your system.
On Fri, 16 May 1997, Karl M. Hegbloom wrote:
>> "Christoph" == Chris
> "Christoph" == Christoph Lameter <[EMAIL PROTECTED]> writes:
Christoph> To my knowledge set -e
Christoph> is only valid for the currently executing scripts and
Christoph> not a subshell.
Try it and see.
It is why `suidregister` is not working when called from postinst
script
To my knowledge
set -e
is only valid for the currently executing scripts and not a subshell.
On Thu, 15 May 1997, Karl M. Hegbloom wrote:
>> "Christoph" == Christoph Lameter <[EMAIL PROTECTED]> writes:
>
> [... in a release announcement ...]
>Christoph> May fix situations leadin
> "Christoph" == Christoph Lameter <[EMAIL PROTECTED]> writes:
[... in a release announcement ...]
Christoph> May fix situations leading to something described in
Christoph> #9435, #9582 (still not clear how such a thing can
Christoph> happen).
This fixes the bug. With s
13 matches
Mail list logo
