public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: cron and annoyances
Date: Sat, 1 Nov 2008 11:18:51 -0600	[thread overview]
Message-ID: <12E9795C780140F9838C8AE0FB64BEDB@tdsportable> (raw)
In-Reply-To: <A2E31AC2180144B08E171596EE34134C@BOE>

it was just the output from the commands I was getting. /dev/null worked, 
thanks. didn't think of that. :)

Thanks,
Tyler Littlefield
email: tyler@tysdomain.com
web: tysdomain-com
Visit for quality software and web design.
skype: st8amnd2005

----- Original Message ----- 
From: "Jayson Smith" <jaybird@bluegrasspals.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, November 01, 2008 11:14 AM
Subject: Re: cron and annoyances


> Hi,
>
>     Chuck said just about what I was going to say here. Try redirecting 
> the output of the commands to /dev/null. However, some commands which are 
> normally silent will produce output if an error occurs, even if they've 
> been redirected to /dev/null. If you still get the messages, actually read 
> one to find out what error is occurring, and fix it.
> Jayson
>
> ----- Original Message ----- 
> From: "Chuck Hallenbeck" <chuckh@ftml.net>
> To: "Speakup is a screen review system for Linux." 
> <speakup@braille.uwo.ca>
> Sent: Saturday, November 01, 2008 1:04 PM
> Subject: Re: cron and annoyances
>
>
>> Tyler,
>>
>> Look in /etc/crontab and find out what application is run every 15
>> minutes to produce the mail you are getting. Redirect the output of
>> that application to /dev/null by adding the necessary redirection
>> information to the line that runs the application.
>>
>> Better yet, read the mail you are being sent to learn what the error is
>> that you are being told about, and fix it.
>>
>> Chuck
>>
>>
>> On Sat, Nov 01, 2008 at 09:45:24AM -0600, Tyler Littlefield wrote:
>>> Hello list,
>>> I was wondering if anyone had a fix for this.
>>> I get tons of mail from cron a day, in my local mailbox, which is rather
>>> annoying,
>>> I think it goes to two accounts of mine on the system, and it happens
>>> every 15 mins or so.
>>> Is there a way I can silence this?
>>>
>>>
>>> Thanks,
>>> Tyler Littlefield
>>> email: tyler@tysdomain.com
>>> web: tysdomain-com
>>> Visit for quality software and web design.
>>> skype: st8amnd2005
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>> -- 
>> The Moon is Waxing Crescent (12% of Full)
>>
>> My web site: http://hallenbeck.ftml.net -- my telephone: 1-518-334-9022.
>>                                --------
>> It is wise to keep in mind that neither success nor failure is ever 
>> final.
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 


  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Tyler Littlefield
 ` Chuck Hallenbeck
   ` Jayson Smith
     ` Tyler Littlefield [this message]
     ` Alex Snow
 ` Kerry Hoath

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=12E9795C780140F9838C8AE0FB64BEDB@tdsportable \
    --to=tyler@tysdomain.com \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).