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.

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

Show crontabs for all users

Terminal - Show crontabs for all users
for i in /var/spool/cron/*; do echo ${i##*/}; sed 's/^/\t/' $i; echo; done
2012-07-11 13:36:34
User: flatcap
Functions: echo sed
0
Show crontabs for all users

Show the crontabs of all the users.

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives
for user in $(cut -f1 -d: /etc/passwd); do echo "### Crontabs for $user ####"; crontab -u $user -l; done
2012-07-11 12:25:56
User: harpo
Functions: crontab cut echo
Tags: crontab
3

added echo "### Crontabs for $user ####"; to make clear whose crontab is listed.

for i in /var/spool/cron/tabs/*; do echo ${i##*/}; sed 's/^/\t/' $i; echo; done
2012-07-12 08:07:20
User: harpo
Functions: echo sed
1

This is flatcaps tweaked command to make it work on SLES 11.2

for user in $(getent passwd|cut -f1 -d:); do echo "### Crontabs for $user ####"; crontab -u $user -l; done
2012-07-11 13:06:17
User: harpo
Functions: crontab cut echo getent
Tags: crontab getent
0

added echo "### Crontabs for $user ####"; to make clear whose crontab is listed.

Know a better way?

If you can do better, submit your command here.

What others think

maybe we need sudo to perform that command..

Comment by chars19 120 weeks and 2 days ago

My command and harpo's all need root privileges.

Comment by flatcap 120 weeks and 2 days ago

for i in /var/spool/cron/*....doesn't work for me on SLES 11.

Comment by harpo 120 weeks and 2 days ago

Hmm... Sorry. I don't have a copy of Suse handy to find out where they're hiding.

The Filesystem Hierarchy Standard says that's where cron jobs should live:

http://www.pathname.com/fhs/pub/fhs-2.3.html#VARSPOOLCRONCRONANDATJOBS

Comment by flatcap 120 weeks and 2 days ago

On SLES one has to type:

for i in /var/spool/cron/tabs/*;
Comment by harpo 120 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts