>
> On Wed, Feb 19, 2014 at 12:57 AM, Chad Gross wrote:
>
>> On Tue, Feb 18, 2014 at 10:33 AM, Chad Gross wrote:
>>
>> > I managed to configure net-mgmt/flowviewer with security/silktools, but
>> > had to make some modifications to get it working.
On Tue, Feb 18, 2014 at 1:57 PM, Chad Gross wrote:
> On Tue, Feb 18, 2014 at 10:33 AM, Chad Gross wrote:
>
>> I managed to configure net-mgmt/flowviewer with security/silktools, but
>> had to make some modifications to get it working. FlowViewer is configured
>&g
On Tue, Feb 18, 2014 at 10:33 AM, Chad Gross wrote:
> I managed to configure net-mgmt/flowviewer with security/silktools, but
> had to make some modifications to get it working. FlowViewer is configured
> by defaut to pass the $silk_data_dir + $device_name as the root data
> dire
I managed to configure net-mgmt/flowviewer with security/silktools, but had
to make some modifications to get it working. FlowViewer is configured by
defaut to pass the $silk_data_dir + $device_name as the root data directory
to the rwfilter tool, when the root directory should be the same as
$silk
No problem; it happens.
Chad
On Wed, Nov 13, 2013 at 5:20 PM, Mark Felder wrote:
>
> On Nov 13, 2013, at 12:27, Chad Gross wrote:
>
> > I found an issue with the nfsen port Makefile. It is not properly
> > configured to expand the %%PORTNAME%% variable used when gen
I found an issue with the nfsen port Makefile. It is not properly
configured to expand the %%PORTNAME%% variable used when generating the
nfsen config file.
For example, the config that is installed shows this:
$VARDIR="${BASEDIR}/var/%%PORTNAME%%";
When it should be this:
$VARDIR="${BASEDIR}