Re: Using script(1) to log all user sessions

[Jesper Dahl Nyerup <nyerup@one.com>]

[-- Attachment #1: Type: text/plain, Size: 1758 bytes --]

On Apr 28  09:13, Karel Zak wrote:
> On Fri, Apr 25, 2014 at 10:21:34AM +0200, Jesper Dahl Nyerup wrote:
> > [...] support config files, to supply configurable
> > default values for some of the concepts normally passed in the
> > environment or as command line arguments.
> 
>  OK.

We will produce a patch for this, and submit it fow review.

> > Secondly, we're considering to add functionality for script(1) to
> > transmit the session transcript over the network to a collection daemon,
> > to be able to store transcripts from multiple machines on one or more
> > central systems.
> 
>  Hmm.. "Every program attempts to expand until it can read mail. Those
>  programs which cannot so expand are replaced by ones which can."
> 
>  I like git concept: here are files and it's your problem to transfer the
>  staff over the network. You can use rsync, http, ssh, ...
> 
>  Maybe all you need is to store timing and typescript data to the one
>  place (e.g. /var/log/typescripts/user/<timestamp>.{session,timing})
>  and use ssh or so to transfer the data to another place.

I see your point.

Storing the files locally before transferring them away has a number of
drawbacks, for instance logging in on systems with filled up
mountpoints, data loss during crashes on systems without persistent
storage, tampering, and so on.

We'll probably end up piping the transcript data to ssh(1), and have
something collecting the data remotely. One of the challenges is to
ensure this transport mechanism doesn't end up blocking the user's
terminal session, in case of network problems or other offload
difficulties.

Thank you all for you input.

Yours,
-- 
Jesper Dahl Nyerup
Systems Engineer
One.com, nyerup@one.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]