literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
When mode_t is char- or short-like, it will be promoted to the pure
int when it is passed as the variable argument [1], so we should pass
'int' to the va_arg.
I had also eliminated fflush for the stream opened read-only, since
it will always fail and there is no need to flush read-only streams.
[1] http://c-faq.com/~scs/cclass/int/sx11c.html
Feature safe: yes
PR: 152304
rather than just leaving them in the examples directory. There seems
to be no real security advantage to not installing the pam files since
they are required for fcron and fcrontab to operate, and root privs are
required to install fcron to begin with.
- The sockaddr.sa_len was not set prior to calls to bind() and connect().
The upshot begin that fcrondyn was unable to open the socket
to communicate with fcron.
PR: ports/97066
Submitted by: maintainer
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.
