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 :
>> do
>> /usr/local/sbin/hdstate >> ~/log/hdstate.log
>> sleep 10
>> done
>
> You wrote to the list telling us that you were running a script from
> cron every minute, and that this was causing your log file to fill up
> with messages from cron.
>
> That is what I replied to.
Yes, I know. You had the good idea of simply putting the script into a
loop, and I actually followed your advice by now. When I posted my first
script in response to yours, I just wanted to show how I got the
relevant information in a more convenient format, using hdparm and
hddtemp, than using the direct output of smartctl. Just in case someone
else also likes this. Of yourse the outer loop was missing, but I did
not bother to add this trivial addition just for the posting here. It's
just the script I was already using in cron. And later in the posting I
mentioned that the script itself should be run in a loop instead of
cron, also because I could decrease the update interval.
Sorry, I probably should have made clear that the original question was
sort of solved.
> Please do not move the goalposts halfway through the thread, and make
> it about something else unrelated. That is the perfect way to annoy
> people who are trying to help you.
I'm sorry about this, I did not mean to annoy anyone. But I still do not
really seewhat the problem is. You had the idea to do this without cron,
and so I did. Well, I forgot a 'thank you' for the loop idea, this is
true. Sorry again. Your ideas were appreciated as always.
Wonko
