Hy everybody, I'm looking for some script that logs every user, such as : IP, username, typed in commands, when loged in , when logged out,

I tryd the "script" command its good but its not logging any IP, or time, so I'm looking for something more powerfull,

pls help.


Thanks.

The information about login, logout and from where comes
with the system - the command to get to that info is:

last

To see what they did: enable the history-file in their
profile, and look at the .history file.



Cheers,
Tink

P.S.: Are you sure that what you're doing is
ethical? I mean, there's no good reason to see
who did what unless you have to assume that
someone is trying to compromise the machine.

I'm not asuming anything, I'm just learning, I heave a linux mashine suse 9.3 and anotherone 9.2 , and we are using it as a learn server, so we log in do things, and one of important things is security, so I'got that Iidea to heave all info about things that happen, to make it possible to repair the problem, when the problems will accure, so my Idea is to finde some script or to write a script that can put all of this commands together : "last" "script" and others that doe the same , to let only one script handle all of this, so next time when I'll look for something then I'll just opent that log wich was made by that script (wich I'm lookin for) and see all of the info in one plase separeted to each user, so no need to first see the "last" then go and see the History and so on .

Well .. in that case there's two choices: either you hope to
actually get lucky and find something that does this, or you
script it yourself ;)

Hint: bash 3.xx has a time-stamp feature for the history, thus
you can determine what was done at which time.

Hint2: I looked at your original (and slightly distinct) thread
where you discussed script with Matir: you could avoid
the problems with the second session by writing to a time-
stamped file (break it down to seconds, should catch most
simultaneous uses).

Hint3: screen, too, provides an option to create a session-log.
Read it's man page ;)


Cheers,
Tink

Aldow, I'dont think this will be the solution that I'm looking for, but anyway we are learning so I'm goint to try the thing that you said and see if I'll finde something