[Android Software/Hacking General [Developers Only]] zeppelinrox:
Ok to verify that it's running you can run the script again or read the comments in the script itself.

There's a check in there so that it won't stay in memory twice.

If it finds that it's already sleeping in memory, it tells you that FluchOMatic is already in memory.

You can still flush as usual and you can still change options but it won't relaunch into memory again.

Actually, here's the updated comments:

#!/system/bin/sh
#
# 2 in 1 Engine Flush Script created by zeppelinrox.
#
# The 2 Modes are: Fast Engine Flush and Engine Flush-O-Matic.
#
# See http://goo.gl/krtf9 - Linux Memory Consumption - Nice article which also discusses the "drop system cache" function!
# See http://goo.gl/hFdNO - Memory and SuperCharging Overview, or... "Why 'Free RAM' Is NOT Wasted RAM!"
#
# Credit imoseyon for making the drop caches command more well known :)
# See http://www.droidforums.net/forum/liberty-rom-d2/122733-tutorial-sysctl-you-guide-better-preformance-battery-life.html
# Credit dorimanx (Cool XDA dev!) for the neat idea to show before and after stats :D
#
# Note 1: To enable "Engine Flush-O-Matic" mode, change the "flushOmatic" variable to 1.
# It is automatically enabled and changed to 1 the first time you say yes to enable Engine Flush-O-Matic!
# If "flushOmatic" is anything other than 1, it's off and won't enter into a "Flush Cycle".
# So... "flushOmatic=1" turns it ON. "flushOmatic=*anything else*" turns it OFF.
#
# Note 2: If "Engine Flush-O-Matic" is enabled, you can change the "flushOmaticHours" variable to the number of hours you want.
# Valid values are from 1 to 24 (hours).
# If the value is invalid or missing, it defaults to running every 3 hours.
# If "Engine Flush-O-Matic" is disabled (see Note 1), "flushOmaticHours" can be anything and will be ignored anyway lol.
# Example: If you want it to run every 4 hours, make the line read "flushOmaticHours=4".
#
# Usage: 1. Type in Terminal: "su" and enter, "flush" and enter. ("flush" is indentical to !FastEngineFlush.sh but easier to type :p)
# When in "Engine Flush-O-Matic" mode, the script relaunches and kills itself. Let it run ONCE, then close terminal.
# Do one of the verification tests below.
#
# Usage: 2. Script Manager: launch it once like any other script OR with a widget (DO NOT PUT IT ON A SCHEDULE!)
# When in "Engine Flush-O-Matic" mode, whether you run with a widget or not, the script relaunches and kills itself.
# If the verification tests below fail, run the script again and at any time, press the Back Button and click on "Leave in Background."
# You can then close Script Manager out of memory and the script should still be running. Then do a verification test again.
#
# To verify that it's running, just run the script again!
# OR you can type in Terminal:
# 1. "pstree | grep lush" - for usage option 1 (with Terminal)
# 2. "pstree | grep sleep" - for usage option 2 (with Script Manager)
# 3. "cat /proc/*/cmdline | grep lush" - Sure-Fire method ;^]
# - This output should be 3 items:
# a. "/data/V6_SuperCharger/!FastEngineFlush.sh" OR "/system/xbin/flush" (depending on which script you ran)
# b. "Engine_Flush-O-Matic_is_In_Effect!" (sleep message)
# c. "lush" (created by your query so this doesn't mean anything)

Now you know why it takes awhile to put out updates... LOL