FATAL ERROR: Failed to Lock PID File "/var/run

[Pedro Marinho <pppmarinho () gmail com>]

Hello Gentlemen,

I have noticed that in one of my sensors snort is falling down.

Jul 27 18:30:04 xyz snort[17282]: PID path stat checked out ok, PID path set
to /var/run/
Jul 27 18:30:04 xyz snort[17282]: FATAL ERROR: Failed to Lock PID File
"/var/run//snort_eth1.pid" for PID "17282"
Jul 27 18:30:05 xyz snort[17275]: Child exited unexpectedly
Jul 27 18:30:05 xyz snort[17275]: Daemon parent exiting

I did make an script to check if it is down and up it again case it is true.
I need to know what may i have to do for it to never fall down. I remember
that when i did use snort 2.3.2  in slackware it never comes down only if i
did kill it. But now i am using suse linux and the version of snort is
Version 2.8.4 GRE (Build 26)

I need that script to check it for me so i can´t up snort with
--nolock-pidfile because it may up another instance of snort.. please help!

ps: i am a newbie

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users