On 31/12/2007, DAve [EMAIL PROTECTED] wrote:
Small hint shown to me many years ago when enabling things in rc.conf.
If I want to startup ipfilter for example (trimmed to avoid wrapping).
bash-2.05b# cat /etc/defaults/rc.conf | grep ^ipfilter
Returns the following,
ipfilter_enable=NO
On Dec 30, 2007, at 10:44 PM, Bill Moran wrote:
Jeffrey Goldberg [EMAIL PROTECTED] wrote:
Putting
syslogd_enable=NO
into /etc/rc.conf did not prevent it from starting.
The above works on every system I've done it to (which is quite a
few).
I suspect you've either got a typo in your
Jeffrey Goldberg wrote:
On Dec 30, 2007, at 10:44 PM, Bill Moran wrote:
Jeffrey Goldberg [EMAIL PROTECTED] wrote:
Putting
syslogd_enable=NO
into /etc/rc.conf did not prevent it from starting.
The above works on every system I've done it to (which is quite a few).
I suspect you've
On Dec 31, 2007, at 9:13 AM, DAve wrote:
Jeffrey Goldberg wrote:
Yep. It was a typo. I should let this be a reminder to always
copy and
paste such things into email instead of retyping.
Small hint shown to me many years ago when enabling things in rc.conf.
If I want to startup ipfilter
I've installed and configured syslog-ng from ports and no longer wish
to have the standard syslogd run.
Putting
syslogd_enable=NO
into /etc/rc.conf did not prevent it from starting.
Of course I can see lots of ways of preventing syslogd from starting.
I could remove the binary, I could
Jeffrey Goldberg [EMAIL PROTECTED] wrote:
I've installed and configured syslog-ng from ports and no longer wish
to have the standard syslogd run.
Putting
syslogd_enable=NO
into /etc/rc.conf did not prevent it from starting.
The above works on every system I've done it to (which
