Hello James,
I have applied the patch and now it shows that snort should be started
root@nac:~# /usr/local/pf/bin/pfcmd service snort status
service|shouldBeStarted|pid
snort|1|0
If I try to start snort by hand it doesn't work
root@nac:~# /usr/local/pf/bin/pfcmd service snort start
service|command
memcached|already started
httpd.admin|already started
Checking configuration sanity...
pfdetect|already started
snort|not started
I just can see this in packetfence.log (no errors though)
Feb 06 11:37:56 pfcmd.pl(5417) INFO: Daemon snort took 0.073 seconds to
start. (pf::services::manager::launchService)
Getting better but not working yet.
> Hi Sampath,
>
> Try this patch and let me know if it works
> https://github.com/inverse-inc/packetfence/commit/d0de4fa74b58e70de6941f9a871198be8ccbe13f.diff
>
>
>
> James Rouzier
> [email protected] :: +1.514.755.3630 ::http://www.inverse.ca
> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence
> (http://www.packetfence.org)
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
