any way to track commands of a user logged in through ssh 2298

Jeremiah DeWitt Weiner

whooops... -- stupid gaga google interface didn't let me see the sig that I had forgotten to remove. I usually do "ok" with trimming ;-) ...(not to mention I was in a huge hurry this morning).

Yeah, I know

Understood - thanks for clarifying

What I had forgotten is that; "whomever" tries to run sudo, 'First' atleast needs to be a logged in as a user (meaning a verifiable pbuttwd too). Disregarding (for my situation as it is now) remote logins using FTP, TElnet, etc, clear text over the network, etc. So I see why it's good the way I have it. Yet, these are 'real-world' issues for many, especially the OP, as it pertains to his-her situation.

Well, I understand, but in my situation (only person with physical access), I'll be darned if I'm going to type a 'pbuttwd' in *everytime* I use-run a Shell command that requires 'root' privileges...Especially since I'm just realizing *which* apps (system admin, etc) actually require it (for alteration), though most apps allow for READ only for the average user.

Precisely as I had thought - thanks again for clarifying, reinforcing

Understood......and thanks

So what do you think about creating a separate 'group' for certain users, as it pertains to the OP's original question? I'm still trying to grasp the full power available in separating-grouping using Groups-Users and Permissions (even ACLs, 'mount' options, and encryption using loop devices, etc). It's slowly sinkin' in ;-)

Regards