Re: [tlug] comand-line recording...

[Curt Sampson <cjs@example.com>]

Sorry, I'm going to let my last bit of pent-up sarcasm out here, and
then let this go. (I just don't have the self-control to *plonk* early
the way that Stephen does.)

On 2009-09-29 21:41 +0900 (Tue), Bruno Raoult wrote:

> You just forgot that sudo won't work, as discussed before (":sh" in vi
> was my example).

Right. Because you were just forced to set up sudo to allow that; your
Linux distribution disabled all of the standard features in sudo that
let you stop that sort of thing. My mistake, obviously.

> The logging is really the only option, discussions about better
> scripting and so on in order to be able to use sudo are then out of
> topic, it just don't work.

Darn! All these things I've been doing for years, it turns out I've not
been doing!

I comfort myself with the thought that, if that's the case, at least
I've been doing some really good drugs for a long, long time. Perhaps
the correct solution here is that you give those same drugs to your
audit guys.

> By the way, FYI, in our case, better scripts is very difficult
> to implement, because of frequent (daily of bi-weekly) software
> deliveries...

Right. People like me who do "infrequent" software deliveries (only
several times per day, or even as rarely as three or four times per
hour) obviously have no understanding of the world in which you live.

> I don't know why, I did not expect another answer... But I will
> consider we could find it out the day we need  it ;-)

Right. "I have no idea if this will work but I'll worry about it later."
Always music to auditors' ears.

cjs
-- 
Curt Sampson       <cjs@example.com>        +81 90 7737 2974
           Functional programming in all senses of the word:
                   http://www.starling-software.com