T
Thomas G. Marshall
Once in a while, I am doing something very cpu intensive and would like to
shut down [all of] NSW. Simply asking for auto-protect to disable doesn't
seem to do the trick since the worm protection seems to stay on.
I can easily write a simple script to kill all the processes, but in order
to relaunch them all properly I would probably have to log in again (?) Is
this true? Or is there a special way to fire up NSW afterward that would
replace all the processes properly?
Furthermore, is there somewhere a cleaner alternative to this, perhaps a 3rd
party utility?
Thanks
--
I've seen this a few times--Don't make this mistake:
Dwight: "This thing is wildly available."
Smedly: "Did you mean wildly, or /widely/ ?"
Dwight: "Both!", said while nodding emphatically.
Dwight was exposed to have made a grammatical
error and tries to cover it up by thinking
fast. This is so painfully obvious that he
only succeeds in looking worse.
shut down [all of] NSW. Simply asking for auto-protect to disable doesn't
seem to do the trick since the worm protection seems to stay on.
I can easily write a simple script to kill all the processes, but in order
to relaunch them all properly I would probably have to log in again (?) Is
this true? Or is there a special way to fire up NSW afterward that would
replace all the processes properly?
Furthermore, is there somewhere a cleaner alternative to this, perhaps a 3rd
party utility?
Thanks
--
I've seen this a few times--Don't make this mistake:
Dwight: "This thing is wildly available."
Smedly: "Did you mean wildly, or /widely/ ?"
Dwight: "Both!", said while nodding emphatically.
Dwight was exposed to have made a grammatical
error and tries to cover it up by thinking
fast. This is so painfully obvious that he
only succeeds in looking worse.