1 |
Hi there! |
2 |
|
3 |
I want to monitor the power status of my hard drives, so I wrote a little |
4 |
script that gives me this output: |
5 |
|
6 |
sda: standby |
7 |
sdb: standby |
8 |
sdc: active/idle 32°C |
9 |
sdd: active/idle 37°C |
10 |
|
11 |
This script is called every minute via an fcron entry, output goes into a |
12 |
log file, and I use the file monitor plasmoid to watch this log file in |
13 |
KDE. |
14 |
|
15 |
It's working fine, but also monitor my syslog in another file monitor |
16 |
plamoid, and now I get lots of these entries: |
17 |
|
18 |
Aug 21 14:21:06 [fcron] pam_unix(fcron:session): session opened for user root by (uid=0) |
19 |
Aug 21 14:21:06 [fcron] Job /usr/local/sbin/hdstate >> /var/log/hdstate started for user root (pid 24483) |
20 |
Aug 21 14:21:08 [fcron] Job /usr/local/sbin/hdstate >> /var/log/hdstate completed |
21 |
Aug 21 14:21:08 [fcron] pam_unix(fcron:session): session closed for user root |
22 |
|
23 |
There is a nolog option for fcrontab, but I still get this output every |
24 |
minute: |
25 |
|
26 |
Aug 21 15:10:06 [fcron] pam_unix(fcron:session): session opened for user root by (uid=0) |
27 |
Aug 21 15:10:08 [fcron] pam_unix(fcron:session): session closed for user root |
28 |
|
29 |
Hmmm... could it be that these entries do not come from fcron itself, but |
30 |
from PAM? Do I need to look there so suppress them? And if so, would this |
31 |
make sense? I want to suppress only these specific logs, not other stuff |
32 |
that might be interesting. |
33 |
|
34 |
Any ideas? It's nothing important, but maybe there's a simple solution, |
35 |
and I like to learn. Don't knwo much about this PAM stuff yet. |
36 |
Maybe I'll just start a background job for that instead of using fcron. |
37 |
|
38 |
Wonko |