On Tue, May 12, 2009 at 9:39 AM, Michael Stahnke mastah...@gmail.com wrote:
On May 12, 2009, at 2:07, Bucky 'Igneous' Wolfe
pmigne...@gmail.com wrote:
grep 'whatever' /home/*/.bashrc
perhaps you mean /home/*/.bash_history? .bashrc probably won't be of
much use :P
Yeah, in my head it
grep 'whatever' /home/*/.bashrc
perhaps you mean /home/*/.bash_history? .bashrc probably won't be of much
use :P
Regards,
Bucky 'Igneous' Wolfe
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
NLUG group.
To
On May 12, 2009, at 2:07, Bucky 'Igneous' Wolfe
pmigne...@gmail.com wrote:
grep 'whatever' /home/*/.bashrc
perhaps you mean /home/*/.bash_history? .bashrc probably won't be of
much use :P
Yeah, in my head it all made sense. :)
Regards,
Bucky 'Igneous' Wolfe
Aren't all sudo commands logged?
On Wed, Apr 22, 2009 at 9:44 AM, Andrew Farnsworth farn...@gmail.comwrote:
Morning everyone,
How does one determine the actual user that issued a command to stop an
application? I believe that the stop command is being run via sudo as you
must be a
On Wed, Apr 22, 2009 at 9:44 AM, Andrew Farnsworth farn...@gmail.comwrote:
Morning everyone,
How does one determine the actual user that issued a command to stop an
application? I believe that the stop command is being run via sudo as you
must be a specific user to issue them. I need to
On Wed, Apr 22, 2009 at 9:44 AM, Andrew Farnsworth farn...@gmail.com wrote:
Morning everyone,
How does one determine the actual user that issued a command to stop an
application? I believe that the stop command is being run via sudo as you
must be a specific user to issue them. I need to
