Terry Raitt wrote:
> The =~ operator does not appear to function.
Unfortunately that is not enough information to recreate the problem.
The =~ operator appears to work for others. Can you say what you were
trying to do?
Bob
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: freebsd5.3
Compiler: cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='freebsd5.3' -DCONF_MACHTYPE='i386-portbld-freebsd5.3'
-DCONF_VENDOR='portbld' -DLOCALEDIR='/usr/local/share/loc
John Gatewood Ham <[EMAIL PROTECTED]> writes:
> Description:
> The info file says "Trapped signals are reset to their original
> values in a child process when it is created." but this is not
> true for me with crond and smartd for the SIGTERM signal.
Signals that are ignore
Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Michael Wardle on 12/8/2005 7:22 PM:
> Yet when I attempt a simple match, it doesn't work:
>
> bash-3.00$ [[ "foo" == "foo" ]]
> bash-3.00$ echo $?
> 0
> bash-3.00$ [[ "foo" == "fo?" ]]
> bash-3.00$ echo $?
> 1
Gl
Michael Wardle wrote:
> In the SHELL GRAMMAR section of the bash man page, the [[ expression ]]
> syntax is described:
>
> When the == and != operators are used, the string to the right of
> the operator is
> considered a pattern and matched according to the rules described below
> und
In the SHELL GRAMMAR section of the bash man page, the [[ expression ]]
syntax is described:
When the == and != operators are used, the string to the right of the
operator is
considered a pattern and matched according to the rules described below
under Pattern Matching.
The P
