Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: SysV configuration patch
-----BEGIN PGP SIGNED MESSAGE-----
On Wed, 18 Nov 1998, John Williams wrote:
> Not only that, but HP-UX runs the S* scripts for each level in order
> [1..n] when bringing the system up, and runs the K* scripts for each level
> in reverse order [n-1..0] to shut down. Which forces each level to be a
> superset of the previous one. (I don't think any other unixes do this.)
> The proper places are probably /sbin/rc4.d/S905hylafax and
> /sbin/rc3.d/K095hylafax. That's not a typo; they go in different
> directories.
This is not so bad: It means that the locations need to be configured
differently for different operating systems. This is what we get for
supporting so many different operating systems!!!
> Furthermore, HP-UX invokes the script as "S905hylafax start_msg" and
> "K095hylafax stop_msg" expecting it to output strings which should be
> displayed on its startup and shutdown screens. For example:
The S905 and K095 is OK.
> case $1 in
> start_msg)
> echo "Start hylafax server"
> ;;
> stop_msg)
> echo "Stop hylafax server"
> ;;
> start)
> # start the daemons...
> ;;
> stop)
> # stop the daemons...
> ;;
**THIS** is new to me, at least. This takes re-writing of the
"hylafax.in" script source. Is HP married to the "start_msg" rather
than the "start" flag?
> p.s. hylafax runs as a client only on my HPs because their serial ports
> suck too.
Ahh. So can we pitch HP as a server altogether? Or should we try to include
that?
Nico Kadel-Garcia
Senior Engineer, CIRL
Mass. Eye and Ear Infirmary
raoul@cirl.meei.harvard.edu
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNlQOPD/+ItycgIJRAQEcIAP9ElE9SC43RWo7kKgd8+cgxUC/XIloFDmS
2Vk/CR+hKkHcSvDRISFY1Ocb68WSHeBBxFe9HbAq0UfDHJRzduyw6K+Nl/3PaTKL
gqEpnIq9ADESjoBfEOu0MoioH5x45Q9WLNJ0Bx5+anJ54qYcI9wt4Oan+TNu+XNn
Miq6XldkeZg=
=+FVL
-----END PGP SIGNATURE-----