On 24 August 2010 14:31, Alex Schuster wrote:
> Mick writes:
>
>> On Sunday 22 August 2010 22:39:47 Alex Schuster wrote:
>
>> > BTW, my two additional drives spin up when I log into KDE. Weird,
>> > they are not even mounted.
>>
>> From KDE-4.4.4 the start up interferes with the hard drives:
>>
>>
Mick writes:
> On Sunday 22 August 2010 22:39:47 Alex Schuster wrote:
> > BTW, my two additional drives spin up when I log into KDE. Weird,
> > they are not even mounted.
>
> From KDE-4.4.4 the start up interferes with the hard drives:
>
> http://thread.gmane.org/gmane.linux.gentoo.user/232044
Apparently, though unproven, at 00:12 on Tuesday 24 August 2010, Alex Schuster
did opine thusly:
> > Configure your syslogger to devnull these specific entries.
> > All three common sysloggers (syslogd,syslog-ng,rsyslog) all come with
> > extensive documentation on how to do this.
>
> Hmm, okay.
Alan McKinnon writes:
> Apparently, though unproven, at 15:25 on Saturday 21 August 2010, Alex
> Schuster did opine thusly:
> > There is a nolog option for fcrontab, but I still get this output
> > every minute:
> That will tell fcron not to log stuff.
> It will not tell other apps to not stuff
Stroller writes:
> On 22 Aug 2010, at 22:39, Alex Schuster wrote:
>> Stroller writes:
>>
>>> The script with which you reply is missing the sleep 60 loop.
>>
>> No, it's only the script that outputs the drive's state. It's called
>> by ~/.kde4/Autostart/hdstate:
>>
>> #!/bin/bash
>>
>> while :
>
On 22 Aug 2010, at 22:39, Alex Schuster wrote:
Stroller writes:
The script with which you reply is missing the sleep 60 loop.
No, it's only the script that outputs the drive's state. It's called
by
~/.kde4/Autostart/hdstate:
#!/bin/bash
while :
do
/usr/local/sbin/hdstate >> ~/log
On Sunday 22 August 2010 22:39:47 Alex Schuster wrote:
> Stroller writes:
> > The script with which you reply is missing the sleep 60 loop.
>
> No, it's only the script that outputs the drive's state. It's called by
> ~/.kde4/Autostart/hdstate:
>
> #!/bin/bash
>
> while :
> do
> /usr/loc
Stroller writes:
> The script with which you reply is missing the sleep 60 loop.
No, it's only the script that outputs the drive's state. It's called by
~/.kde4/Autostart/hdstate:
#!/bin/bash
while :
do
/usr/local/sbin/hdstate >> ~/log/hdstate.log
sleep 10
done
> Running a scr
On 22 Aug 2010, at 20:00, Stroller wrote:
On 22 Aug 2010, at 11:26, Alex Schuster wrote:
Stroller writes:
#!/bin/bash
while true
do
for drive in a b c d
do
/usr/sbin/smartctl /dev/sd$drive --whatever >> /var/log/hdstate
done
sleep 60
done
I use hdparm and hddtemp:
for hd in sda sdb
On 22 Aug 2010, at 11:26, Alex Schuster wrote:
Stroller writes:
#!/bin/bash
while true
do
for drive in a b c d
do
/usr/sbin/smartctl /dev/sd$drive --whatever >> /var/log/hdstate
done
sleep 60
done
I use hdparm and hddtemp:
for hd in sda sdb sdc sdd
do
...
echo "$hd: $sta
Stroller writes:
> On 21 Aug 2010, at 14:25, Alex Schuster wrote:
> > ...
> > I want to monitor the power status of my hard drives, so I wrote a
> > little
> > script that gives me this output:
> >
> > sda: standby
> > sdb: standby
> > sdc: active/idle 32°C
> > sdd: active/idle 37°C
> >
> > This
On 21 Aug 2010, at 14:25, Alex Schuster wrote:
...
I want to monitor the power status of my hard drives, so I wrote a
little
script that gives me this output:
sda: standby
sdb: standby
sdc: active/idle 32°C
sdd: active/idle 37°C
This script is called every minute via an fcron entry, output
Apparently, though unproven, at 15:25 on Saturday 21 August 2010, Alex
Schuster did opine thusly:
> Hi there!
>
> I want to monitor the power status of my hard drives, so I wrote a little
> script that gives me this output:
>
> sda: standby
> sdb: standby
> sdc: active/idle 32°C
> sdd: active/i
13 matches
Mail list logo
