Emulating bash

Emulating bash

[Mads Martin Jørgensen]

Hey together,

I was toying around and beeing impressed with the bash emulation of zsh
(I actully moved it into /bin/bash). But it struck me it had problems
with trapping the signals because signals known to bash apparantly are
unknown to zsh-bash. This is zsh-4.0.1 final.

Any hints to how I can fix this -- it would be nice on my small systems
to get zsh too :-)

-- 
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic and
totally illogic, with just a little bit more effort."
                                -- A. P. J.

RE: Emulating bash

[Andrej Borsenkow]

>
> I was toying around and beeing impressed with the bash emulation of zsh
> (I actully moved it into /bin/bash). But it struck me it had problems
> with trapping the signals because signals known to bash apparantly are
> unknown to zsh-bash. This is zsh-4.0.1 final.
>
> Any hints to how I can fix this -- it would be nice on my small systems
> to get zsh too :-)
>

Any hints what your particular problem is? :-) It is hard to fix without
knowing what to fix - and not every zsh user or worker expert in bash.

What signals are in bash?


-andrej

Re: Emulating bash

[Mads Martin Jørgensen]

* Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru> [Jun 24. 2001 23:26]:
> >
> > I was toying around and beeing impressed with the bash emulation of zsh
> > (I actully moved it into /bin/bash). But it struck me it had problems
> > with trapping the signals because signals known to bash apparantly are
> > unknown to zsh-bash. This is zsh-4.0.1 final.
> >
> > Any hints to how I can fix this -- it would be nice on my small systems
> > to get zsh too :-)
> >
> 
> Any hints what your particular problem is? :-) It is hard to fix without
> knowing what to fix - and not every zsh user or worker expert in bash.
> 
> What signals are in bash?

Of course -- totally forgot.

It is when trapping SIGINT and SIGTERM, it says unknown signal. SIGQUIT
and SIGSEGV are not problematic..

_From the bash manual (2.05):
SIGNALS
       When bash is interactive, in the absence of any traps,  it
       ignores  SIGTERM (so that kill 0 does not kill an interac­
       tive shell), and SIGINT is caught and handled (so that the
       wait  builtin  is  interruptible).   In  all  cases,  bash
       ignores SIGQUIT.   If  job  control  is  in  effect,  bash
       ignores SIGTTIN, SIGTTOU, and SIGTSTP.

-- 
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic and
totally illogic, with just a little bit more effort."
                                -- A. P. J.

RE: Emulating bash

[Andrej Borsenkow]

>
> Of course -- totally forgot.
>
> It is when trapping SIGINT and SIGTERM, it says unknown signal. SIGQUIT
> and SIGSEGV are not problematic..
>

What system? Have you compiled it yourself or got binary? Zsh autogenerates
signal names from system include file (it tries to guess the correct one).
On my system:

bor@itsrm2% kill -l
HUP INT QUIT ILL TRAP IOT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM USR1 USR2
CLD PWR WINCH URG POLL STOP TSTP CONT TTIN TTOU VTALRM PROF XCPU XFSZ

Both INT and TERM are there.

-andrej