On Fri, Jul 07, 2000 at 05:18:59PM -0700, tony mancill wrote:
> There are two ways around this, but both would require a bit of policy.
> First, we could force the init.d scripts to use the -u command line option
> to the shell. (If an unset variable is referenced, the script will die. -
> sorta
On Fri, Jul 07, 2000 at 04:49:09PM -0700, Joey Hess wrote:
> So it's really not that bad to go in and edit stuff if something has changed.
> This doesn't address the problem of what happens if an essential new variable
> needs to be added though. But I have a simple solution:
>
> /etc/init.d/foo:
Hello.
Matt Zimmerman schrieb:
> On Fri, Jul 07, 2000 at 04:49:29PM -0700, Joey Hess wrote:
> > /etc/init.d/foo:
> >
> > #!/bin/sh
> > # Don't touch these ..
> > FOO=bar
> > NEWVAR=/tmp/killme
> > # .. edit this file instead!
> > if [ -f /etc/default/foo ]; then
> > . /etc/default/foo
> > f
On Fri, Jul 07, 2000 at 04:49:29PM -0700, Joey Hess wrote:
> tony mancill wrote:
> > While we're discussing this, I'd like to hear comments on the idea of
> > using an /etc/rc.config.d/$package scheme, like that in HP-UX. This file
> > is a shell script that gets sourced by the /etc/init.d/$packa
On Sat, Jul 08, 2000 at 01:05:56PM -0500, Michael Urman wrote:
>
> This comment makes it easy to turn off the running of portmap, but it
> does not make it easy to reenable it. Sure your average admin may be
> conversant with 0 and 1, but your actual script runs it on 1, and does
> not otherw
On Sat, Jul 08, 2000 at 12:40:01PM -0400, Christopher W. Curtis wrote:
> >
> > the majority of debian initscripts are elegant in their plain
> > simplicity. its very obvious exactly what is occuring and its very
> > clear how to make changes (say add a command line argument)
>
> Well ... I think
On Sat, Jul 08, 2000 at 12:40:01PM -0400, Christopher W. Curtis wrote:
> if [ "X$RUN_PORTMAP" != "X1" ] ; then
> exit 0
> fi
> # 'portmap' is installed as part of netbase. You cannot remove netbase,
> # as it is a required package, so here's your chance to turn it off.
> # Set RUN_PORTMAP
"Christopher W. Curtis" wrote:
> A (I hope) pertinent example: I don't like portmap in the required
> package netbase. I don't like the existing "solution" for diasbling
> it. Why? This is me. Who cares, I'm providing an alternative. Look
> at /etc/init.d/portmap. I'm going to rewrite this
Joey Hess wrote:
>
> Ethan Benson wrote:
> > because not all daemons are alike, each has thier own subtle needs,
> > trying to make a one-size-fits-all shell script `library' will only
> > cause bugs, and make the script less clear and harder to modify.
>
> I have to agree. If you read say, 50 in
Ethan Benson wrote:
>
> On Sat, Jul 08, 2000 at 01:16:42AM -0400, Christopher W. Curtis wrote:
> >
> > Why do you feel this way? A lot of the debain scripts contain stuff
> > which seems non-obvious to me, and they (pretty much) all do the same
>
> the majority of debian initscripts are elegant
On Fri, 7 Jul 2000, tony mancill wrote:
> What if we did this?
> /etc/rc.config.d/sendmail.default
> /etc/rc.config.d/sendmail
> (or /etc/rc.config.d/sendmail.override)
> And so on. Always source sendmail.default first, so that we know we have
> sane values. If "sendmail" is there, source it too
Ethan Benson wrote:
> because not all daemons are alike, each has thier own subtle needs,
> trying to make a one-size-fits-all shell script `library' will only
> cause bugs, and make the script less clear and harder to modify.
I have to agree. If you read say, 50 init scripts, you'll find 50% of
On Sat, Jul 08, 2000 at 01:16:42AM -0400, Christopher W. Curtis wrote:
>
> Why do you feel this way? A lot of the debain scripts contain stuff
> which seems non-obvious to me, and they (pretty much) all do the same
the majority of debian initscripts are elegant in their plain
simplicity. its ve
[mass cc cleaning; does this belong in -policy?]
Ethan Benson wrote:
>
> On Fri, Jul 07, 2000 at 10:44:15PM -0400, Christopher W. Curtis wrote:
> >
> > My idea is to have a script, '/etc/init.d/defaults', which every init
> > script sources. 'defaults' will read the default settings and define
>
On Fri, Jul 07, 2000 at 10:44:15PM -0400, Christopher W. Curtis wrote:
>
> My idea is to have a script, '/etc/init.d/defaults', which every init
> script sources. 'defaults' will read the default settings and define
> common functions for the scripts to use. Here is a rough draft of the
> idea:
Joey Hess wrote:
>
> tony mancill wrote:
> > While we're discussing this, I'd like to hear comments on the idea of
> > using an /etc/rc.config.d/$package scheme, like that in HP-UX. This file
[...]
>
> I'll try to summarize the rest of the thread:
>
> 1. The files should include nothing but simp
tony mancill wrote:
> What if we did this?
>
> /etc/rc.config.d/sendmail.default
> /etc/rc.config.d/sendmail
> (or /etc/rc.config.d/sendmail.override)
> .
> .
> .
>
> And so on. Always source sendmail.default first, so that we know we have
> sane values. If "sendmail" is there, source it too.
Cool - this could really happen. Here are a couple of comments.
On Fri, 7 Jul 2000, Joey Hess wrote:
> 2. If we move to this type of file, we have to worry about what happens if a
>user modified it, it is a conffile, and a new version of a package adds a
>variable to it; the user meanw
18 matches
Mail list logo
