1 |
Because I've seen these errors before as well with logwatch. |
2 |
|
3 |
On Mon, 2005-03-21 at 11:54 -0600, Lance Lassetter wrote: |
4 |
> Ouch, I'm not the one with this problem but would something like |
5 |
> rkhunter which is recommended to be used by the -hardened team pick up |
6 |
> something like this? |
7 |
> |
8 |
> I run with standard with 'rkhunter -c' do I need to specify other |
9 |
> options with rkhunter? |
10 |
> |
11 |
> Thanks, |
12 |
> |
13 |
> Lance(stuNNed) |
14 |
> |
15 |
> On Mon, 2005-03-21 at 10:52 -0500, Wes Kurdziolek wrote: |
16 |
> > When you upgrade certain packages, part of their post-install is to tell |
17 |
> > init to restart b/c it or its configuration has changed. However, if |
18 |
> > you haven't upgraded any of these packages (off the top of my head, I'm |
19 |
> > not sure which, but I'd guess sysvinit would be a good start) it could |
20 |
> > be a sign of someone installing a trojan init. |
21 |
> > |
22 |
> > On Sat, 2005-03-19 at 10:08 -0800, Ben Munat wrote: |
23 |
> > > Anyone know why this: |
24 |
> > > |
25 |
> > > init: Trying to re-exec init |
26 |
> > > |
27 |
> > > would show up in my logs? |
28 |
> > > |
29 |
> > > Ben |
30 |
> > > -- |
31 |
> > > gentoo-server@g.o mailing list |
32 |
> > > |
33 |
> > -- |
34 |
> > gentoo-server@g.o mailing list |
35 |
> |
36 |
> -- |
37 |
> gentoo-server@g.o mailing list |
38 |
|
39 |
-- |
40 |
gentoo-server@g.o mailing list |