Shell Programming and Scripting

You can get away with running grep 10,000 times in a short interval on Linux but on Windows that will occasionally hiccup, you'll be using resources far faster than they're being freed. Not necessarily running out of memory, but running out of something inside the kernel like free file handles or such.

By doing more with fewer commands you can write a script that Windows will tolerate.

If your script is running commands frequently enough to make Windows hiccup, it could probably stand improvement anyway. You say 'grep and awk' for instance, but awk can do both in one command and a whole lot more. It can replace an entire grep | sed | cut | awk | kitchen | sink kind of pipe chain, which makes a huge difference in resource consumption and performance.

It's a 400 line script. I'll try a weekly restart.

Is there a way for a daily-run script to detect such a thing? I noticed some defunct bash processes the last time when I did a ps -ef

The forum will not explode if you post a 400-line script.

A weekly restart isn't going to make errors less likely.

Since you refuse to post your script, we cannot help you. Thread closed.