Package: ferm
Version: 2.0.6-1
Severity: wishlist
Hi,
the hooks in ferm are very valuable, but currently the hooks get
executed or included into the scripts regardless of the domain.
Since ferm offers the command line option --domain to only process
one domain, this may to trouble in combination with hooks.
(e.g. sysctl settings changed for the other domain, ....)
The solution to this issue are domain-specific hooks.
Ideas for implementation:
- new key words: e.g. @hook4, @hook6
- allow to define @hook inside a domain an d treat those hooks accordingly.
e.g.
@hook pre "echo 'I am a global hook'";
domain ip {
@hook pre "echo 'I am a IPv4 specific hook'";
...
}
domain ip6 {
@hook pre "echo 'I am a IPv6 specific hook'";
...
}
I am willing to help testing.
Best regards
Peter
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ferm depends on:
ii debconf 1.5.27 Debian configuration management sy
ii iptables 1.4.4-2 administration tools for packet fi
ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip
ii perl 5.10.0-25 Larry Wall's Practical Extraction
Versions of packages ferm recommends:
ii libnet-dns-perl 0.65-1 Perform DNS queries from a Perl sc
ferm suggests no packages.
-- debconf information:
* ferm/enable: true
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
