| 19 Oct 2021 |
 Kenji Ichikawa | In reply to rudolff
I utilized a "hack" with grep to highlight words with grep -e '' -e 'word' -the trick it outputs everything because empty string '' matches all lines, but highlights the word in the second pattern. grep "^\|shit" | 22:25:03 |
| Kenji Ichikawa | * `grep "^\|shit"` | 22:25:16 |
 rudolff | That works, too. | 22:33:15 |
| 21 Oct 2021 |
|  siduck joined the room. | 07:01:17 |
| siduck | hi | 07:01:34 |
| rudolff | # hi | 11:41:22 |
 KMatias | hi | 15:25:22 |
 Michele Campus | hola | 15:26:51 |
 thatoo | Hello | 22:37:26 |
| thatoo | I want to test all files in users directories /home/sftpuser_* and check if there are recent files (less than a day) | 22:38:53 |
| thatoo | I came up with | 22:38:57 |
| thatoo | * I came up with | 22:39:06 |
| thatoo | #!/bin/bash
if [ find /home/sftpuser_* -mtime -1 ]
then
echo recent enough
fi
| 22:39:19 |
| thatoo | but I get the following error | 22:39:40 |
| thatoo | * but I get the following error | 22:39:55 |
| thatoo | line 2: [: too many arguments | 22:39:57 |
| thatoo | if I do | 22:40:02 |
| thatoo | #!/bin/bash
if [ find "/home/sftpuser_xxx/onefile" -mtime -1 ]
then
echo recent enough
fi
| 22:40:33 |
| thatoo | it works for this specific "onefile" file | 22:41:02 |
| thatoo | I found | 22:52:03 |
| thatoo | #!/bin/bash
for file in /home/sftpuser_*/*; do
#echo $file
if test `find "$file" -mtime -1`
then
echo recent enough
fi
done
| 22:52:16 |
| 22 Oct 2021 |
 mgoerner | Your problem is that you put `find` in brackets. In bash, `if` expects commands and checks their exit code. Thus, you invoke the command `[` with argument `find` and I doubt this is what you want. | 05:38:44 |
 S0AndS0 | thatoo: Ya may be able to use find with a while loop instead of a for loop, eg.
while read -rd '' _file; do
printf 'Recent file -> %s\n' "${_file}"
done < <(find /home/sftpuser_*/* -type f -mtime -1 -print0)
Alternatively the stat, and date, commands may be useful, eg.
_recent="$(date +%s --date='yesterday')"
for _file in /home/sftpuser_*/*; do
[[ -f "${_file}" ]] || { continue; }
[[ "$(stat -c %Y "${_file}")" -gt "${_recent}" ]] && {
printf 'File smells fresh enough -> %s\n' "${_file}";
continue;
}
# ... do something with older files? ...
done
| 06:22:14 |
| S0AndS0 | * thatoo: Ya may be able to use find with a while loop instead of a for loop, eg.
while read -rd '' _file; do
printf 'Recent file -> %s\n' "${_file}"
done < <(find /home/sftpuser_*/* -type f -mtime -1 -print0)
Alternatively the stat, and date, commands may be useful, eg.
_recent="$(( $(date +%s) - (24 * 60 * 60) ))"
for _file in /home/sftpuser_*/*; do
[[ -f "${_file}" ]] || { continue; }
[[ "$(stat -c %Y "${_file}")" -gt "${_recent}" ]] && {
printf 'File smells fresh enough -> %s\n' "${_file}";
continue;
}
# ... do something with older files? ...
done
| 06:22:35 |
| S0AndS0 | * thatoo: Ya may be able to use find with a while loop instead of a for loop, eg.
while read -rd '' _file; do
printf 'Recent file -> %s\n' "${_file}"
done < <(find /home/sftpuser_*/* -type f -mtime -1 -print0)
Alternatively the stat, and date, commands may be useful, eg.
for _file in /home/sftpuser_*/*; do
[[ -f "${_file}" ]] || { continue; }
[[ "$(stat -c %Y "${_file}")" -gt "$(date +%s --date='yesterday')" ]] && {
printf 'File smells fresh enough -> %s\n' "${_file}";
continue;
}
# ... do something with older files? ...
done
| 06:25:24 |
| S0AndS0 | * thatoo: Ya may be able to use find with a while loop instead of a for loop, eg.
while read -rd '' _file; do
printf 'Recent file -> %s\n' "${_file}"
done < <(find /home/sftpuser_*/* -type f -mtime -1 -print0)
Alternatively the stat, and date, commands may be useful, eg.
_recent="$(date +%s --date='yesterday')"
for _file in /home/sftpuser_*/*; do
[[ -f "${_file}" ]] || { continue; }
[[ "$(stat -c %Y "${_file}")" -gt "${_recent}" ]] && {
printf 'File smells fresh enough -> %s\n' "${_file}";
continue;
}
# ... do something with older files? ...
done
| 06:26:12 |
| thatoo | Thank you | 06:40:38 |
| mgoerner | One last note: under Linux, the modification timestamp of a folder is always identical to that of the file changed latest. It might be sufficient to just check if your folder was modified less a day ago. | 07:13:53 |
| S0AndS0 | Happy to help!
If ya go the for loop rout, then there are two shopt options ya may like;
man --pager='less --pattern="^\s+globstar" +n' bash
man --pager='less --pattern="^\s+extglob"' bash
man --pager='less --pattern="^\s+Pathname Expansion"' bash
... which allows for matching a pattern of unknown depth, and known file extension. For example the following will search for paths ending in .css, .html, or .js...
shopt -s extglob globstar
__DIR__="${HOME}/web-site"
for _path in ${__DIR__}/**/*.+(css|html|js); do
printf '_path -> %s\n' "${_path}"
done
... However, beware that paths expend into a temporary array before the for loop begins execution; so for deep searches find is a safer choice.
| 17:28:01 |
| S0AndS0 | In reply to @thatoo:defis.info
Thank you * Happy to help!
If ya go the for loop rout, then there are two shopt options ya may like;
man --pager='less --pattern="^\s+globstar" +n' bash
man --pager='less --pattern="^\s+extglob"' bash
man --pager='less --pattern="^\s+Pathname Expansion"' bash
... which allows for matching a pattern of unknown depth, and known file extension. For example the following will search for paths ending in .css, .html, or .js...
shopt -s extglob globstar
__DIR__="${HOME}/web-site"
for _path in ${__DIR__}/**/*.+(css|html|js); do
printf '_path -> %s\n' "${_path}"
done
... However, beware that paths expend into a temporary array before the for loop begins execution; so for deep searches find is a safer choice.
| 17:29:22 |
