You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The processes table includes a uid, but not a username. When users are local to the machine, that uid matches what's in the uid table. However, if the user is a domain user, they're uid is -1, so there's no way to tell which user is actually running a process.
The text was updated successfully, but these errors were encountered:
I'll have to look into this more, there should be a good way for us to make this connection as we get the uid for domain users via the sid, but I need to double check how that ties with the processes table.
@mew1033 ah my apologies for letting this get stale! I'll double check the state of this, and if it's still broken I'm working on some overhauls to the processes table anyway and will ensure this is do-able!
@mew1033 yeah this looks to be a limitation of the way the processes table works. I'll see if I can't address this here soon - again apologies for letting this issue go stale, this fix might prove to be a little tricky.
The processes table includes a uid, but not a username. When users are local to the machine, that uid matches what's in the uid table. However, if the user is a domain user, they're uid is -1, so there's no way to tell which user is actually running a process.
The text was updated successfully, but these errors were encountered: