Bash Script -

Checksumfail · 01-13-2011, 01:06 PM

removed

szboardstretcher · 01-13-2011, 01:11 PM

Quote:

command=`ps aux | grep root | sed -n '1,13p;13g'`
echo $command >> somefile.out

You can try this

Checksumfail · 01-13-2011, 01:16 PM

removed

colucix · 01-13-2011, 01:16 PM

Code:

"ps aux | grep root | sed -n '1,13p;13g'" >> $HOME/ShellScriptsRemote/output.txt

Why you embed the command in double quotes? The shell interprets the whole pipe as a single command name and obviously cannot find it. Remove the (unnecessary) quotes and the trick is done.

grail · 01-13-2011, 07:13 PM

I am curious what the point of the '13g' is for in this particular sed?

Also if you want extra marks in your assignment you might consider the following:

1. grep is not required as sed could provide the functionality for you

2. Whether using grep or sed to find search item you may wish to consider are you searching for a user or that word anywhere on the line??

crts · 01-13-2011, 09:15 PM

Hi,

I agree with grail. Unless you shortened your actual sed command before you posted it here, the '13g' does not accomplish anything. It simply tells sed to copy the hold buffer to your pattern space. Since you have not put anything in in your hold buffer you simply 'delete' your pattern space. This is also pointless because line #13 has already been printed by the previous command: '1,13p'
You can speed up your sed by
sed -e '13 q'
This will print line 1-13 by default and quit when it encounters line 13.

szboardstretcher · 01-19-2011, 11:49 AM

According to your signature, that sed line should be wrapped in CODE tags.

crts · 01-19-2011, 12:07 PM

Quote:

Originally Posted by szboardstretcher

According to your signature, that sed line should be wrapped in CODE tags.

Does not strictly apply for one-liners

colucix · 01-19-2011, 12:32 PM

Quote:

Originally Posted by Checksumfail

removed

How to trash a thread... congratulations!

H_TeXMeX_H · 01-19-2011, 01:38 PM

It was probably homework and he didn't want his teacher to find it.