stewie410

Or use a while-read loop anyway?

while read -r foo; do
  cmd "${foo}" 
done < <(ls -1)

(But don’t script ls)

The find example should just use -exec grep "USB" {} + also, though -exec generally is the correct way to do this.

iptables --> nftables

And if you really want the iptables UX, iptables-nft is also an option (at least on Debian). While I prefer firewalld most of the time on a server, my boss really wants to stick with the same tools he’s used for 20yr; so iptables-nft it is.

I’ve somewhat recently taken TrueNAS to avoid the headache of DKMS for ZFS support.

While it is nice to know I basically don’t have to worry about that, the rest of it is pretty painful – I can’t even install a package without manually running it in docker.

We’ve in a CentOS/Rocky shop at work until recently, moving to Debian.

If I has to redo my NAS, is take Debian or something and call it a day. The hassle of TrueNAS and similar distros do not really seem worth it, if you want more control.

shell built-in command

After looking into it a bit more, its at least a builtin for bash but is otherwise not POSIX. I guess nohup ... & would be the POSIX compliant equivalent, though still not a builtin.

Its my understanding that & backgrounds, not necessarily detaches, a process – if the parent process closes, I think the background tasks would still be wait()ed on, if only using &.

Shouldn’t you end with & disown to fully detach?