Search Results

Unfortunatelly this sequence is not a perfect if-then-else replacement. It works as expected in situations like:

$ true && echo true || echo false
true
$ false && echo true || echo false...

Yes, it is AND and OR. They connect pipelines and execute them conditionally. man bash:
So - if the test result is TRUE, execute the first command list, if FALSE, the second. That's why it acts as...

Not knowing what cat_item does, I can see that the upper process is the child of the lower, linked/indicated by its parent PID (4486). Look into the script to see if and where and what for it forks....

disown builtin is in ksh93. HP-UX 11.31 and older have ksh88.
Workaround is closing or redirecting all the file handles, at minimum stdin(0), stdout(1), stderr(2).
TIME is accumulated CPU usage....

S isn't stopped. it's "interruptable sleep". Only 1 process can technically be running at a time on each CPU. T is the code you want to look out for. That means stopped by job control. see man ps for...

Not that I'm aware of. I guess I should have started by asking your OS and $KSH_VERSION.

You should be able to exit by trying exit twice. But I've not dealt with such a system, at least not for a...

The ? means the process is not connected to a controlling terminal.
Since computers are very fast and ps has limited number of significant digits, some small values are rounded down to 0.00.
...

It seems ksh doesn't ignore SIGTTOU, which is sent when a background process tries to write to a terminal. This question was just asked by alexcol...

What is the full command-line you are trying to run? Many people think they need something like:
find path... primary... -print0 | xargs -0 commandwhen:
find path... primary... -exec command {} +...

That one liner actually does what it is said to do. The -es are not needed (at least in my linux mawk). Try printing the pattern space with the l command to see how it proceeds. If it finds only...

I have a general pattern that I remember that works for lots of cases. Your problem is simpler than many and in this specific case, I should have given you the much simpler command:
find . ! -name...

From the (Linux) man page:

Read it like this: From the first non-empty line till the next blank line, DO NOT delete (explicit meaning); for the rest, DELETE (implicit).

The find -depth primary produces a post-order walk of the file hierarchy instead of the default pre-order walk; it has no effect on how deep find goes as it walks the hierarchy. To get what TomG...

Actually, if your loop is doing what I think it is -- running one head, tail, awk and tr for each line in a file -- that is extremely inefficient, and should be replaced entirely with a while read...

LstFldDataPart =`head -n "$LstFldDataPartCntr" "${FeedFileDir}/${FeedFileBadRecs}" | tail -1 | tr -d '\n'` is wrong, because of the spaces around the equal. Try:

LstFldDataPart=`head -n...

Everything is working just fine.

Your problems are that you have a DOS file that you're working on with UNIX utilities (get rid of the carriage return characters and you would get something closer...

What operating system are you using?
How many lines are you concatenating?
After concatenating those lines, how long is your single output line supposed to be?
How have you determined that the...

awk 'BEGIN {FS="|"} NF !=17 {printf $0} END {print ""} ' feedfile.txt >feedfilebadrecs.txt

and forget about tr.
If this doesn't work, post the output of: cat -vet feedfile.txt using the code tags.

for f in *
do
[ -s "$f" ] && continue ## file exists, but is not empty
[ -f "$f" ] && rm "$f"
done