From: urgrue <urgrue@tumsan.fi>
To: Md Shanto <shanto76@gmail.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: Starting "Script" when user logs on.
Date: Wed, 03 Aug 2005 12:48:01 +0000 [thread overview]
Message-ID: <1123073281l.23049l.0l@hyttynen> (raw)
In-Reply-To: <b30595cd050803033826add037@mail.gmail.com> (from shanto76@gmail.com on Wed Aug 3 13:38:10 2005)
I don't think script will help you, as even if you get it working, your
users can just Ctrl-D out of it. Unless you trust your users.
Once upon a time I used ttysnoop:
http://freshmeat.net/projects/ttysnoop/
On 08/03/2005 01:38:10 PM, Md Shanto wrote:
> Hi all,
>
> I am trying to force "script" for logging all text I/O activities at
> the moment user logs in. Most of the users are running bash at this
> moment.
>
> Initially I tired with "ttyrec" a tty recorder and failed, as it says
> "Out of pty's - Terminated". Now, I tried something like below:
>
> ------------------
> #!/bin/bash -l
> USER=`whoami`
> LOGTIME=`date +%Y-%m-%d-%H:%M:%S`
> /usr/bin/script -q /var/log/commlog/$USER-$LOGTIME
> ------------------
>
> and assigning this script in /etc/passws. This script will log
> scripts
> with time stamp in /var/log/commlog/.
>
> what happen is: when user logs in the process becomes a loop and I
> see
> lot of script instances are running.
>
> Any idea.
>
> -Refayet
> -
> To unsubscribe from this list: send the line "unsubscribe linux-
> admin"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2005-08-03 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 10:38 Starting "Script" when user logs on Md Shanto
2005-08-03 12:48 ` urgrue [this message]
2005-08-03 13:01 ` Andy Davidson
2005-08-03 17:20 ` Jason Clark
2005-08-04 19:06 ` GH Snijders
2005-08-04 11:11 ` Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1123073281l.23049l.0l@hyttynen \
--to=urgrue@tumsan.fi \
--cc=linux-admin@vger.kernel.org \
--cc=shanto76@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).