1 |
On Mon, Jul 18, 2011 at 3:16 PM, Jarry <mr.jarry@×××××.com> wrote: |
2 |
> On 18-Jul-11 21:07, Michael Mol wrote: |
3 |
>>> |
4 |
>>> ----- |
5 |
>>> 2011-07-18T18:31:02+00:00 game fcron[30032]: pam_unix(fcron:session): |
6 |
>>> session opened for user root by (uid=0) |
7 |
>>> 2011-07-18T18:31:04+00:00 game fcron[30032]: pam_unix(fcron:session): |
8 |
>>> session closed for user root |
9 |
>>> 2011-07-18T18:41:02+00:00 game fcron[30787]: pam_unix(fcron:session): |
10 |
>>> session opened for user root by (uid=0) |
11 |
>>> 2011-07-18T18:41:04+00:00 game fcron[30787]: pam_unix(fcron:session): |
12 |
>>> session closed for user root |
13 |
>> |
14 |
>>> Now my question is: why is fcron sending messages to /dev/log, |
15 |
>>> when it should not do it? |
16 |
>> |
17 |
>> If I'm reading that correctly, it's not really fcron that's logging, but |
18 |
>> PAM. |
19 |
> |
20 |
> I thought it is because cron is opening session as root. |
21 |
> There is nothing else that could fire pam every 10 min. |
22 |
> |
23 |
> I already checked /etc/cron.hourly (daily, weekly, monthly), |
24 |
> there is nothing else that could cause it. And the process |
25 |
> name calling syslog is "fcron" (3rd field in message)... |
26 |
|
27 |
Cron is opening a session as root. Pam is part of that process. Pam is |
28 |
logging its participation in that process. |
29 |
|
30 |
At least, that's what it looks like from here. |
31 |
|
32 |
-- |
33 |
:wq |