On 2007-08-05, Paul Sladen wrote:
> On Sat, 4 Aug 2007, Andrew Jenkins wrote:
>> For now though I consider playing around as 'root' while being 'under
>> the influence' as bad as driving so I'll leave well alone.
>
> Exact logging is *precisely* why 'sudo' exists. In the morning you do:
>
> sud
On Sun, 5 Aug 2007, Matthew Wild wrote:
> On 8/5/07, Chris Rowson <[EMAIL PROTECTED]> wrote:
> > On Sun, 5 Aug 2007, Paul Sladen wrote:
> > > sudo grep '[s]udo' /var/log/auth.log
> > Well, if you're computer still works eh ;-)
> How do you get around sudo -i or sudo bash?
The best solution is to n
Hi Matthew,
On Sun, 2007-08-05 at 15:50 +0100, Matthew Wild wrote:
> How do you get around sudo -i or sudo bash? Presumably that would free
> them of the detailed logging?
sudo can be configured to allow not only specific users to run commands
under sudo, but can also limit what those commands ar
How do you get around sudo -i or sudo bash? Presumably that would free them
of the detailed logging?
On 8/5/07, Chris Rowson <[EMAIL PROTECTED]> wrote:
>
> > In the morning you do:
> >
> > sudo grep '[s]udo' /var/log/auth.log
> >
> > and find out what you did the night before. 'su' won't give y
> In the morning you do:
>
> sudo grep '[s]udo' /var/log/auth.log
>
> and find out what you did the night before. 'su' won't give you a list...
>
Well, if you're computer still works eh ;-)
--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.
On Sat, 4 Aug 2007, Andrew Jenkins wrote:
> For now though I consider playing around as 'root' while being 'under
> the influence' as bad as driving so I'll leave well alone.
Exact logging is *precisely* why 'sudo' exists. In the morning you do:
sudo grep '[s]udo' /var/log/auth.log
and find o
