Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

OpenID
or
Sign in Register

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Don't spam root. Log your cronjob output to syslog

Terminal - Don't spam root. Log your cronjob output to syslog
*/5 * * * * root /usr/local/nagios/sbin/nsca_check_disk 2>&1 |/usr/bin/logger -t nsca_check_disk
2010-07-02 00:47:05
User: StefanLasiewski
6
Up
Down
Don't spam root. Log your cronjob output to syslog

This command will log the output of your simple cronjobs to syslog, and syslog will take it from there. Works great for monitoring scripts which only produce simple output.

Advantages:

* This can be used by regular users, without modifying system files like /etc/syslog.conf

* Reduce cron spam to root@localhost (Please stop spaming the sysadmins)

* Uses common tools like syslog (and logrotate) so that you don't need to maintain yet another krufty logfile.

* Still ensures that the output is logged somewhere, for posterity. Perhaps it's stored the secure, central syslog server, for example.

* Seems to work fine on Ubuntu, CentOS, FreeBSD & MacOSX

Show sample output | Add to favourites | Report as malicious

Alternatives

There are 6 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Even better, add something like this to syslog.conf:

local0.* /var/log/mycronlog

Then use "logger -p local0.info -t Tag " and your log entries will go to their own log file.

Comment by SuperFly 154 weeks and 5 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts