public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Disable fcron logging
Date: Mon, 23 Aug 2010 23:30:36 +0200	[thread overview]
Message-ID: <201008232330.48408.wonko@wonkology.org> (raw)
In-Reply-To: <C0BB04CD-2A54-4883-B219-57232836586F@stellar.eclipse.co.uk>

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



      reply	other threads:[~2010-08-23 21:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21 13:25 [gentoo-user] Disable fcron logging Alex Schuster
2010-08-21 13:43 ` Alan McKinnon
2010-08-23 22:12   ` Alex Schuster
2010-08-24  6:49     ` Alan McKinnon
2010-08-21 19:26 ` Stroller
2010-08-22 10:26   ` Alex Schuster
2010-08-22 19:00     ` Stroller
2010-08-22 19:50       ` Stroller
2010-08-22 21:39       ` Alex Schuster
2010-08-22 22:18         ` Mick
2010-08-24 13:31           ` KDE and hdparm (was: Re: [gentoo-user] Disable fcron logging) Alex Schuster
2010-08-25  9:54             ` [gentoo-user] Re: KDE and hdparm Alex Schuster
2010-08-25 19:14               ` Mick
2010-08-30 16:38             ` KDE and hdparm (was: Re: [gentoo-user] Disable fcron logging) Mick
2010-08-23 18:25         ` [gentoo-user] Disable fcron logging Stroller
2010-08-23 21:30           ` Alex Schuster [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008232330.48408.wonko@wonkology.org \
    --to=wonko@wonkology.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox