[Gllug] Stupid shell question

[Murray]

ok, one from the equally stoopid answer brigade:

poll the history file for your user(s) every X minutes, dump the contents to
a file, stripping out known executables along the way - guess you would need
to be a little creative with the parsing there.

of course, also assumes the history is long enough and you poll frequently
enough.

now back to reinventing the wheel

> -----Original Message-----
> From: gllug-admin at linux.co.uk [mailto:gllug-admin at linux.co.uk]On Behalf
> Of John Hearns
> Sent: 18 June 2002 16:04
> To: gllug at linux.co.uk
> Subject: [Gllug] Stupid shell question
>
>
> Well folks, here is another stupid question,
> which I know the answer to already.
> But the collective GLLUG mind never ceases to surprise...
>
>
> Question - is there any way of trapping (or logging)
> executables which users try to execute and  which are not
> present on the system?
> Say the user types 'foo' and gets the response
> bash: foo: command not found
>
> I know the answer to this is 'replace bash (or any other
> shell) with a doctored version which will log this'
> Any better answers (read 'easier to implement by a lazy person')?
>
>
> John H.
>
>
>
> --
> Gllug mailing list  -  Gllug at linux.co.uk
> http://list.ftech.net/mailman/listinfo/gllug
>
>
>



-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug