Watch changeable interrupts continuously

watch -n1 'cat /proc/interrupts

0
2009-08-19 11:10:55

These Might Interest You

  • change gpeXX by the culprit you discovered on phase 1 In case of this example, the culprit is the biggest number, ie, gpe1C /sys/firmware/acpi/interrupts/ff_gbl_lock: 0 enabled /sys/firmware/acpi/interrupts/gpe01: 0 enabled /sys/firmware/acpi/interrupts/gpe06: 0 enabled /sys/firmware/acpi/interrupts/gpe17: 2 enabled /sys/firmware/acpi/interrupts/gpe18: 0 enabled /sys/firmware/acpi/interrupts/gpe1C: 19 enabled This procedure,if solved this universal issue all linix distros are experimenting for more than 2 years, may be included at startup, via cron. But try first commandline.


    0
    echo "disable" > /sys/firmware/acpi/interrupts/gpeXX
    m33600 · 2013-07-16 03:53:20 0

  • 4
    watch -n <time_interval> "du -s <file_or_directory>"
    stbu · 2010-08-24 20:05:08 0
  • Continuously watches postgres, showing the instances using the most RAM at the top. Show Sample Output


    0
    watch -n 1 '{ ps aux | head -n 1; ps aux --sort -rss | grep postgres | grep -v grep; } | cat'
    carbocation · 2017-05-14 17:01:44 0
  • Cycles continuously through a string printing each character with a random delay less than 1 second. First parameter is min, 2nd is max. Example: 1 3 means sleep random .1 to .3. Experiment with different values. The 3rd parameter is the string. The sleep will help with battery life/power consumption. cycle 1 3 $(openssl rand 100 | xxd -p) Fans of "The Shining" might get a kick out of this: cycle 1 4 ' All work and no play makes Jack a dull boy.'


    2
    cycle(){ while :;do((i++));echo -n "${3:$(($i%${#3})):1}";sleep .$(($RANDOM%$2+$1));done;}
    putnamhill · 2010-10-08 23:45:40 2

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. 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.

Share Your Commands



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: