At least on Solaris "-u" is the option. For any other system you are going to have to man ls and actually read it to find out if any of the options have anything to do with access time and then...

man ls

I didn't mention, that was on Solaris. On something else the "t" may not be necessary (and is seemingly not on your system), but that decimal point is (when including seconds).



There is a...

The man page for ls and the awk command.


ls -E f1.sh | awk '{print $6, $7, $8}'

touch -mt 200911141130.00 f1.sh

Take a closer look at the man page.

Yes it will. Why don't you try showing us what you tried.

P.S. Did you try typing "man touch" first?

Configure the ssh to use private keys.

See http://www.daniweb.com/forums/thread15164.html

#! is a built-in exec. The shell script is executed in the shell declared on this line.

$1 etc are the arguments provided on the command line (or provided on the function call when used inside a...

grep will only match the lines (and return the entire line, not just the matched portions of it), and will not alter them. If you wish to alter the lines you are going to need to use sed, or...

try it, post it, and we will help to correct it

You can also do


tar xvf bin.tar \*perl\*


but you're right, the quotes are probably easier.

Of course you can (and it is -9), but it's not worth it if you don't know whether or not it was already used. use split and mail it in pieces, then use join to recreate the file at the other end.

Not that I think you'll win much, but did you use the -9 option when you created the gzip file?

Otherwise, split and join.

Question 1. What if the same pattern also fits inside the "largest" pattern? i.e

pattern: A.*B
String: ABCDEFBGHIJK

Is AB matched, or is ABCDEFB matched?

Question 2:

What is th...

Ok, unfortunately, the only thing left to do, that I can think of, is to do the script this way:


#!/bin/sh -f
for i in `grep "/\\*" file`; do
echo "$i"
done


And start the entire script...

It is because of file name expansion in the shell.

Just for fun try it this way

for i in `grep "/\\*" file`; do
set -f i=$i
echo "$i"
done

for i in `grep "/\\*" file.c`; do


You need to escape the escape character when doing this inside of the expression quotes.

Edit: Which, I believe, is what ithelp meant, but he mistakenly...

I would have to assume that it is coming from the tee (and that error will only occur on the file handle being read, not the filehandle being written), so I have to assume that the find command is...

then do

find / -wholename='somename' -print | tee -a filename


Edit:

Although I am not familiar with "wholename" argument, I assume your find options are actually something different (and...

At the top of this forum is a fixed post to a tutorial. Read through some of that, try something out, if it doesn't work post your code and I'll help, but I'll not do it for you.

are you using ksh or bash? if so

set -A aArray `print "$a" | sed -e 's/-/ /'`
set -A bArray `print "$b" | sed -e 's/-/ /'`
# now ${aArray[0]} and ${bArray[0]} contain the year
# and...

Check which quote you are using. On the keyboard it should be the one that slants from the upper left to the lower right, not the other way around and not straight up and down. In the code, it...

Well this is guaranteed to get you answers.

Have you never heard of Google?

Or even the command "man ftp", since that, itself, describes the .netrc file and your "logfile" can be simple output...

Uhhm, awk is a really large subject. O'Reilly publishing http://www.oreilly.com/ produces an entire book (and a good one at that) dedicated to sed and awk. Try that.

Do Your Own Homework.

I coould be completely wrong, because I always put it against the left edge anyway, but I believe the "END_SCRIPT" marker you are using to end the so-called here document, needs to be against the...