Search Results

So you want:
log_name="server.log server.log.$AAAA_MM_JJ.[0-9][0-9][0-9]"
in your script sometime after you have set the variable AAAA_MM_JJ.

${DATE:0:1} that's a substring operator -- the variable, the offset, and the length. An offset of 0 and length of 1 gets the first character.

To only process valid lines:
valid () {
...
}
...

To be pedantic: those patterns are not regular expressions. It's just sh pattern matching notation.

To be helpful: use multiple patterns.
case "$3" in
([01][0-9] | 2[0-3])
# Nothing, OK !
...

'case' is the oldest, most portable pattern check. Use (..) on patterns so vi's '%' can track/traverse them:case "$1" in
([a-z][a-z][a-z][a-z])
# nothing, OK !
;;
(*)
echo 'Fatal, $1 =...

Again, be aware that arg n may NOT be set!
Add this to your f1 function for testing the other parameters:[[ "$2" -ge "0" && "$2" -le "23" ]] && echo \$2 is good || echo \$2 is bad
[[ "$3" -ge "0"...

Try find ./temp ./TMP -iname "$nom" ...

It's a bit tricky to get values back to your main script from subshells, and pipes are running in subshells. You can try this one that will save a good result in a variable for use outside the loop...

Rats! Sorry for that. I should never give out any code without thoroughly testing it - even small "corrections" on the fly will come flying in my face!
Drop the shift and make the next line read ...

if [ -f $file.gz ]
then command="gunzip -c"
else command=cat
fi1. You do want to test for $file.gz, don't you.
2. The shell [ ] wants a space on both sides. If you like you can...

Here I want to use any of the following single characters as field seperators: /, [, ] or space.

This equates to the regular expression [/ \][] (just like [ABC] would allow a single A, B or C...

This should correct the "[" and "]" chars around the data and time line.

file=$1
if [ -f $file.gz ]
then command="gunzip -c"
else command=cat
fi
$command $file | awk -F"[/ \\\][]"...