Brian Inglis writes: > System processes with more recent process start times seem to make process > times > available to unelevated processes. > Do startup system processes not have this info available to unelevated > processes > because of some security policy, timing, or possible race conditions with > system > process and performance monitor startup?
I don't understand why you keep talking exclusively about system startup processes, these are just a subset (if a particularly stubborn one). The process start time info is generally unavailable for an unprivileged user (since it requires to "open" the process") except for processes started under the same user account in the same user session. There is a security token (I forgot the name, but it's been posted on this list a few days ago) you can add to user accounts so they get to see more (but still not all) such information. Certain types of information are only accessible conditional on which groups you're a member of. It also varies a bit by Windows version and type of install, I think. On top of that come group policies. So this is a lot more involved than just system startup processes. > System startup process start times appear to not be available to unelevated > processes, so the process default value is zero. > ISTM boot time is a better, more accurate, and useful default for those > processes. I still disagree, but then those are not the only processes that have this issue. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
