Here is a similar use-case:
I maintain a number of HA clusters with fully automatic bi-directional
synchronization using rdist. To achieve this I have as few file
differences as possible and those that must differ (mostly
hostname.$if) being entirely scriptable -- the sole noteable exception
i
I would hope that in this particular case, Theo's mail is not to be
taken literally -- especially when the process can easily be made even
more bullet-proof... (and yes, I do "make install" after re-building
the kernel due to errata.)
On 13 Jan 2015 at 0:39, Simon Nicolussi wrote:
> Theo de Ra
If I understand PF documentation correctly, then I stumbled onto a bug.
Through process of elimination and simplification I've determined that
the following pf.conf(5) snippet works flawlessly, while the one below
(same thing inside an anchor) does not. How can I [help] track down
this bug? Con
I think you are missing two very important points that are addressed in
the official documentation and have been pointed out to you by other
respondents:
1. what you are asking for provides NO real added security, and perhaps
just the opposite through FALSE SENSE of security, and
2. the fact t
THIS MESSAGE IS FROM OUR TECHNICAL SUPPORT TEAM This message is sent
automatically by the computer. If you are receiving this message it means
that your email address has been queued for deactivation; this was as a
result of a continuous error script (code:505)receiving from this email
address. Cli
