Search results for query: *

Quick question, in you script I see you put {} around your variables when you call them and that you double up on some other things like [[]] (()) any reason for this?

How does the system handle the rename and delete of the errorlog files? The reason I ask is because I am funning various scripts with set -x so that I can track them in the error log, now due to an increase in runs my errorlogs are growing too large. Is there a way to change how the system...

Thx very much, I have a lot of questions but I will see if I can figure it out on my own first. Thanks for the jump start.

DATE,TIME,ERROR,EXIT CODE,ERROR MSG example: 20031002,13:01:01,ERROR,1,Error copying file xyz

nawk 'BEGIN { FS = "," } nawk 'At the BEGINing set the Field Seperator to "," $1 == '"$DATE2"' check if the first field is equal to "$DATE2" && $3 == "ERROR" Also check is the third field is equal to "ERROR" { print $5...

I want to port some unix scripts to perl, mostly for the fun of it. If anyone is kind enough could you help me convert this stuff. Converting these two functions should give me enough of a feel for it to do the rest. #!/bin/sh ################## # USAGE_function # ##################...

That would mean we would create approx 100 directories a day. And have to maintain 300 at a time. Since grep is not recursive it would make research very difficult.

Working with large directories I have a SUN blade 2000 running Solaris 8 that works with lots of files each day. I would say around 50 thousand files a day. We need to maintain at least 3 days worth of these files for research purposes if an error occurs. There are two problems with this...

Working with large directories I have a SUN blade 2000 running Solaris 8 that works with lots of files each day. I would say around 50 thousand files a day. We need to maintain at least 3 days worth of these files for research purposes if an error occurs. There are two problems with this...

I have a SUN blade 2000 running Solaris 8 that works with lots of files each day. I would say around 50 thousand files a day. We need to maintain at least 3 days worth of these files for research purposes if an error occurs. There are two problems with this. 1. Our crontab fails to delete...

I forgot to call it when I typed it here, it seems that () keep the variables within the function but {} let them out. interesting.

Why won't this work? How can I make it work? Start Script: a1()( var=2; export var ) echo $var

Bump

Ygor, thx again that worked great, any chance you could give me a bit of an explanation of how it works. I have been studying awk since you first helped me but this is way over my head.

EOF is the last line of each record. There can be many records in 1 file. I want to write "Line 1" after the last instance of "Page:" in each record. I want to write "Line 4" after the last instance of “Begin” in each record. "Begin" comes after...

Ygor and others, help combining 2 Awk scripts I want to take this script: awk 'BEGIN {b=&quot;&quot;} { if (b > &quot;&quot;) b=b &quot;\n&quot; $0; else b=$0} /Page:/ {print b;b=&quot;&quot;} /EOF/ {print &quot;LINE 1 HERE\n&quot; b;b=&quot;&quot;} END {print b}' < $1 And this scripts: awk...

Tom, Thanks again for the help. I finally have the solution for both the N4525 and DP92. With the DP92 I added a /Staple 1 setpagedevice before each first page and a /Staple 4 setpagedevice in the pagesetup of the last page of the file. For the N4525 I used a /staple 1 setpagedevice before...

Whenever line 4 occurs add a line between the previous Line 1 and Line 2. Their will be up to 48 Line 4’s with a varying number of line 12&3’s between them.

Input File line 1 line 2 line 3 line 1 line 2 line 3 line 1 line 2 line 3 line 4 Output File line 1 line 2 line 3 line 1 line 2 line 3 line 1 Line Added line 2 line 3 line 4

Thatz just what I needed , thanks again tom