Thanks for the info.. On Fri, Oct 17, 2014 at 7:06 PM, William Roberts <[email protected]> wrote:
> Also you don't need to declare your own property > > Setprop ctl.start <named service> > Setprop ctl.stop <named service> > > So to stop auditd > Setprop ctl.stop auditd > > To start just use ctl.start > On Oct 17, 2014 4:03 AM, "Pankaj Kushwaha" <[email protected]> > wrote: > >> Hi, >> >> I diverged from AOSP few long back. Took some patches from bit-bucket and >> lots of code was written internally be me. >> What I was trying to achieve is that I restart auditd after every few >> mins so that audit.log is copied to audit.old and I upload this audit.old >> to one of my server through an app (just for testing purpose). >> I restarted auditd by setting a prop declared in init.rc, on setting of >> which 'restrat auditd' is executed. >> What I observed is, that when auditd restarts, PID associated with it >> changes and then it stops logging denials. But if PID in dmesg and PID >> after restart of auditd are same, then there are no issues and logs are >> captured. >> >> Thanks >> Pankaj Kushwaha >> >> On Thu, Oct 16, 2014 at 7:25 PM, William Roberts < >> [email protected]> wrote: >> >>> How are you restarting auditd and what's the purpose? >>> >>> Those logs are OK if you kill auditd, however when it starts back up it >>> should start getting the logs. >>> >>> What code base version our you on, google merged the auditd >>> functionality into something called logd. >>> >>> Bill >>> On Oct 15, 2014 11:21 PM, "Pankaj Kushwaha" < >>> [email protected]> wrote: >>> >>>> Hi, >>>> >>>> I took auditd mechanism from bit-bucket to collect seandroid denials in >>>> audit.log file. >>>> Recently I observed that whenever I restart auditd, sometimes it stops >>>> logging new audit logs. >>>> >>>> I am seeing below error in dmesg- >>>> <3>[ 3130.027258] audit: *NO* daemon at audit_pid=4733 >>>> <4>[ 3130.032157] audit: audit_lost=2 audit_rate_limit=0 >>>> audit_backlog_limit=64 >>>> <3>[ 3130.038063] audit: auditd disappeared >>>> >>>> Is it known issue and do we have any fix for this ? >>>> >>>> I tried to google about it and saw that someone else was facing the >>>> same problem (though no on Andorid)- >>>> https://www.redhat.com/archives/linux-audit/2011-September/msg00010.html >>>> >>>> Thanks >>>> Pankaj Kushwaha >>>> >>>> _______________________________________________ >>>> Seandroid-list mailing list >>>> [email protected] >>>> To unsubscribe, send email to [email protected]. >>>> To get help, send an email containing "help" to >>>> [email protected]. >>>> >>> >>
_______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
