In my SEC rule set, I am using an SQLite in-memory database to cache
data. When I shutdown SEC, I save this sqlite database to disk and
reload it into memory when SEC starts.
I've now observed several times, and it seems to be when the database is
large, that the save to disk procedure during SEC_
hi Bond,
there is no time limit for the shutdown procedure. In fact, since sec is a
single-threaded tool, it would be impossible to impose such a timeout. In
your rule example, the execution of the 'action' field prevents sec from
doing anything else, and since your 'action' field does not seem to
On 10/21/2015 12:54 PM, Risto Vaarandi wrote:
> hi Bond,
>
> there is no time limit for the shutdown procedure. In fact, since sec
> is a single-threaded tool, it would be impossible to impose such a
> timeout. In your rule example, the execution of the 'action' field
> prevents sec from doing an
When you look more closely what killproc() in Centos6 init script actually
does, then you probably spot this:
# TERM first, then KILL if not dead
kill -TERM $pid >/dev/null 2>&1
usleep 10
if checkpid $pid ; then
try=0
