Why M$ OS is without control...
This is JUST an example
why M$ OS is considered uncontrollable ?
Many reason , here comes one.
because service/users policy are inconsistent.
Everybody knows that a service can be started under a user account. So I can create a user, assign to a Service logon priviledge and make a service run under this account.
I Install a service, create a temp directory for that service.... and expect life to flow quietly!
I just discovered CA Brightstore ArcServer Service made my W2k3 ActiveDirectory server crash. It saturated the root directory with more then 2000 .TMP files, reporting an error. a Stupid error : "cannot found cartridge xxx".
Of course this is a Application error (should not report 2000 times the same error in less then 2 minutes!)
of course it is NOT ( :8 ) OS fault if the service wrote 2000 files!
BUT THE OS ALLOWED IT TO DO IT IN THE ROOT DIRECTORY!
which was filled COMPLETELY! and why should an OS crasch , just due to some TMP file wrote in a directory ?
Try to do this under unix, and you will find out your app cannot simply write files in root directory, outside it's own created with priviledge assigned directory
Sorry. m$ Os is UUU
Unstable, Uncontrollable, Untested!
AAA looking for a tough Operating System!
