IMHO init scripts must be POSIX (Bourne?) compliant.
They should work in bash, ksh, whateversh, and don't depend on the
administrator's will to install one or another.
i.e.
I'll say this:
if [ $errors == 1 ]; then
is better this way:
if [ $errors -eq 1 ]; then
And this:
On Fri, May 02, 2003 at 11:25:46AM +0200, Alberto Gonzalez Iniesta wrote:
> Anyway, I'm attaching Debian's init.d script in case you want to take a
> look at it.
>
Doh! I ALWAYS forget to attach files! Sorry :)
--
Alberto Gonzalez Iniesta | They that give up essential liberty
agi@(agi.a
On Fri, 02 May 2003, James Yonan wrote:
> How do most other initialization scripts handle the differences between bash 1
> and 2? Do they just restrict themselves to the least common denominator (a)?
Yes. /bin/sh is standardized; Solaris for some strange reason ship
b0rked year-old stuff though
On Mon, 28 Apr 2003, Alberto Gonzalez Iniesta wrote:
> Sorry for the huge forward, but everything needed to understand this
> problem should be there :)
FYI:
My post of the FreeBSD-ports mailing list how I should handle this
license issue LZO <-> OpenSSL hasn't turned up anything in some days; s
