Imagine this shell pipeline:
sh prog1 | sh prog2
As given above, prog1 blocks if prog2 hasn't yet read previously written
data (actually, newline separated commands) or is busy. What I want is
for prog1 to never block:
sh prog1 | buffer | sh prog2
I first thought that the aptly named
Hi, I'm trying to run the net/openradius port as non-root
by first changing /usr/local/etc/rc.d/openradius:
. /etc/rc.subr
name=openradius
rcvar=`set_rcvar`
load_rc_config ${name}
: ${openradius_enable=NO}
: ${openradius_flags=-o /var/log/openradius.log}
-command=/usr/local/sbin/radiusd
Hi. I can't seem to find the way FreeBSD deals with stopping the running
rc.d services when shutting down/rebooting the machine. In Linux, for
example, the shutdown command first switches to runlevel 0, triggering
init to call the program for that event, which deals with shutting down
the
Oops, there's this /etc/rc.shutdown thing, sorry to bother you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Is there a security branch for the FreeBSD ports collection? Let's say,
I installed FreeBSD 6.0 together with all needed -RELEASE
ports/packages. Running security/portaudit after a while reveals that
some of the installed packages have vulnerabilities. Am I on my own to
go grab the fresh
Andrea Venturoli wrote:
rihad wrote:
FreeBSD only has a current port tree.
The port tree you call -RELEASE is simply current as it was at the
time the base OS was released.
Yes, wrong wording here. I was aware of that snapshot thing happening,
just lazy to go check www.freebsd.org
Is there a security branch for the FreeBSD ports collection? Let's say,
I installed FreeBSD 6.0 together with all needed -RELEASE ports/packages
(i.e., those on the CD). Running security/portaudit after a while
reveals that some of the installed packages have vulnerabilities. Am I
on my own to
