From: "George Georgalis" <george@galis.org>
Subject: Re: invoking ipsvd-cdb
Date: Fri, 20 Jan 2006 00:48:28 -0500 [thread overview]
Message-ID: <20060120054827.GD13229@sta.duo> (raw)
In-Reply-To: <20060119101516.34c15c05@alloy.copperisle.com>
On Thu, Jan 19, 2006 at 10:15:16AM -0800, Wayne Marshall wrote:
>On Mon, 16 Jan 2006 17:22:29 -0500
>"George Georgalis" <george@galis.org> wrote:
>
>> ipsvd-cdb(8) and ipsvd-instruct(6) have been helpful, but is there
>> an example of a typical "dir" for ipsvd-cdb invocation?
>>
>> I'm moving from tcprules but not sure how to build the cdb files
>> with ipsvd-cdb.
>>
>
>There are a growing number of runit-based service definitions available
>on the slackmatic website in the "guinix" repository:
>
> http://slackmatic.org/site.cgi?repoview=guinix
interesting, saw a couple nice scripts.
>Many of these have default "iprules" instructions set up in an
>iprules sub-directory within the service directory. The run script
>conventions used for these services make sure the rules are recompiled
>each time the service is restarted.
I try to avoid "helpers" like that. it's when the ip
rules change that a new cdb should be generated...
# cat /var/service/qmail-smtpd/peers.sh
#!/bin/sh
cd `dirname $0` && ipsvd-cdb peers.cdb peers.tmp peers
that way whenever you've changed anything under ./peers
you've nearly typed the command to update the cdb too.
The other way, people are liable to restart services
whenever they change a ip rule.
// George
--
George Georgalis, systems architect, administrator <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george@galis.org
next prev parent reply other threads:[~2006-01-20 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 22:22 George Georgalis
2006-01-19 18:15 ` Wayne Marshall
2006-01-20 5:48 ` George Georgalis [this message]
2006-01-20 17:03 ` Wayne Marshall
[not found] <20060116223834.GD1074@sta.duo>
2006-01-16 22:47 ` George Georgalis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060120054827.GD13229@sta.duo \
--to=george@galis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).