Search:

What am I doing here?

Oh.....bumpin'

So.....BUMP.

And Merry Christmas to all.

As I was preparing my last post, my inner child had this funny feeling that you would show up and change his diaper. :D
Thanks.

Crusty

Hmmm...Since this thread has become somewhat of a contest to see how many different ways we can write this script, I thought this was a good time bring in some awkological awkumen...sorry, couldn't...

There are several different ways you can capture your CPU usage.
This might help: http://www.cyberciti.biz/tips/how-do-i-find-out-linux-cpu-utilization.html

This is easier than you might think:


any_input=${any_input,,}

Reference: http://mywiki.wooledge.org/BashFAQ/073
Scroll down to the heading: Bash 4

There is more than one way to do what you're asking. My preference is to add a line to the bottom of the file: ~/.bashrc that looks similar to this:


export PATH=$PATH:/path/to/directory

After...

You have this:


else
echo "$(date "+%m%d%Y %T") : rdesktop has Stopped. Attempting to resta$
case $THISHOST in
(rpiA) rdesktop -z -u user -p password 10.100.100.10;;...

Just to add to those confused, I'll make it three of us.

Too funny.
Now, perhaps you've discovered the modern use for twelve pound sledge hammers.

Perhaps you could discover the application that might be responsible for turning your computer into a...

You're mighty welcome.

I really wish I could tell you why the changes we made to ~/.bashrc to modify your PATH fixed the problem. But, I can't because I don't know.

When steeldriver challenged...

To Langstracht:

I'd like you to answer some more questions:

What Linux operating system are you running?
Are you running your operating system in WUBI?
What application did you use to...

Oh, man!
I have my threads confused. There's no "Jonathan" here.
Time to do some heavy editing.

Well, I did it because when I compared Langstracht's PATH to what I have in my PATH, /home/username/bin was the only path that was missing. Since the script runs for me, but doesn't run for him, I...

Yup...sure as hell would be.

Yeah...well...that's why I told you to:

Please post the output you get, in a code box, when you run it.


So, based on what you described, in lieu of posting the output, I'm assuming that...

Well, maybe I don't understand what you want the script to do.
You write: "The above code displays every line it is supposed to ... plus the "Hit [ ... abort." after each "batch" of lines." <--...

Well, I'll be damned. So, that's where I got it.
It still sucks, though.

You're mighty welcome, Jonathan.

I wrote that script several years ago and have been using it ever since, with success. Consequently, the Zenity error message hasn't appeared. However, after I...

You might want to remember that you'll need to use the "shebang" as the first line of every bash script that you write in the future:


#!/bin/bash

See if your script runs if you put the following line in as the very first line of your code (it's called a shebang):


#!/bin/bash


Here's how to make a code box:

It would be nice to see the entire content of your script in a code box. Otherwise, we're just guessing as to why what works for us isn't working for you.

In keeping with your coding style, which is much different than mine, your script worked for me when I added the blue line shown in the code box below:


#!/bin/bash
set -e

count=10
i=1...

Well, since you are not an "Absolute" beginner. Your thread probably doesn't belong in this forum. Since there are several issues involved with the difficulty you're having, a better place to have...

Here's a working example that keeps the Zenity message box on top using wmctrl.
if you don't have wmctrl installed, you can comment out the blue line in the code box below:


#!/bin/bash

#...

You're mighty welcome.
I edited the command to specify that the regular expression should match the word: none, at the beginning of the line.
It' a little better that way.




Please mark...