Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 31 May 2008 13:50:04 GMT
From:      Paul Schmehl <pauls@utdallas.edu>
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   Re: ports/124122: [PATCH] security/barnyard: [SUMMARIZE CHANGES]
Message-ID:  <200805311350.m4VDo4rk006623@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/124122; it has been noted by GNATS.

From: Paul Schmehl <pauls@utdallas.edu>
To: Akiko Narita <shuyaan@gmail.com>, bug-followup@freebsd.org
Cc:  
Subject: Re: ports/124122: [PATCH] security/barnyard: [SUMMARIZE CHANGES]
Date: Sat, 31 May 2008 08:43:27 -0500

 --On May 31, 2008 9:35:31 PM +0900 Akiko Narita <shuyaan@gmail.com> wrote:
 
 >> I don't know what the desire is for the submission of this patch, but
 >> barnyard won't even run without the correct flags, so the patch doesn't
 >> make any sense to me.
 >
 > Hello Paul,
 >
 > Sorry, I forgot to describe the problem I'm trying to solve.
 >
 > I've used barnyard-sguil-0.2.0_4.
 > When I started up barnyard-sguil, barnyard loaded 'barnyard_flags'
 > redundantly(/usr/local/etc/rc.d/barnyard and /etc/rc.conf) and it
 > couldn't start up.
 > I think that you don't need to specify 'barnyard_flags' in
 > rc.d/barnyard. '*_flags' is usually set in /etc/rc.conf, isn't it?
 >
 
 Barnyard_flags must be defined in the startup script or its values in 
 rc.conf will be ignored.  However, I may have made a mistake in the 
 startup file that is causing the inclusion of both.  I'll investigate.
 
 Paul Schmehl (pauls@utdallas.edu)
 Senior Information Security Analyst
 The University of Texas at Dallas
 http://www.utdallas.edu/ir/security/
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200805311350.m4VDo4rk006623>