Mads Kiilerich wrote:> I noticed one thing I don't like: The NETS variable. Even though
> the script is located under /etc it should _not_ be used as a
> configuration file for normal use. Starting _all_ nets as "I" do
> now is slightly ugly too. Perhaps /etc/tinc/nets should be used?
There are basically three solutions to this question.
1) Put a line in the startup script.
2) Start all nets that are in /etc/tinc.
3) Create a file /etc/tinc/nets (for example) containing only the
networks to be started.
The first option is acceptible, I think, but that is only because I
know the Debian side of the story. Debian's policy documents don't
mention that it should not be done, so there. ;) But I agree that
it's not The Optimal Way.
Option two is ugly, just because you don't know what is in /etc/tinc.
I say we go for option 3, and name the file /etc/tinc/nets.boot, so
that it's clear from the name what the file does.
>
> I suggest that your init.d script is generalized so that it can
> be used under Debian and RedHat - perhaps using a little "glue"
> script.
Does the script as it is now work under redhat?
--
Ivo Timmermans
Deja moo: the feeling you've heard this bullshit before.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url :
http://brouwer.uvt.nl/pipermail/tinc-devel/attachments/20000518/d91c0537/attachment.pgp