10-19-2010
Want to find the stdout for the partiuclar user login for past 12 hrs.
Want to find the stdout for the partiuclar user login for past 12 hrs.
Say for eg : user login id is teladm
And the host name is sys22prod
I want to see the stdout for that user id in that host for past 12 hrs
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
root pts/5 Sep 04 11:33 (:0.0)
hi, from the above, how do i remove it? (4 Replies)
Discussion started by: yls177
4 Replies
2. UNIX for Dummies Questions & Answers
hi, i noticed that there are still past logins which have not been terminated. how should i removed them?
i am on aix. (9 Replies)
Discussion started by: yls177
9 Replies
3. UNIX for Advanced & Expert Users
Can Anyone tell me how to write the Script to "find file(s) in a directory that is being accessed in last 5 minutes, and if there is result of that find, then throw the mail ".
Means throw the mail to a person regarding whoever and whenever a file is accessed in a directory.
ASAP.
Thnks. (2 Replies)
Discussion started by: varungupta
2 Replies
4. Shell Programming and Scripting
It seems like not all Unix have whoami. What is the alterate way to display just the login id?
Any help is appreciated
jak (5 Replies)
Discussion started by: jakSun8
5 Replies
5. Shell Programming and Scripting
Hi All,
I have a file which contains the listing of another directory:
>cat list.dat
-rwxr-xr-x 1 test staff 10240 Oct 02 06:53 test.txtdd
-rwxrwxrwx 1 test staff 0 Oct 04 07:22 test.txx
-rwxrwxrwx 1 test staff 132 Sep 16 2007 test_tt.sh... (6 Replies)
Discussion started by: deepakgang
6 Replies
6. Shell Programming and Scripting
hi all,
I need to find files in a directory which are older than N hrs...
n can be 1,2,3,.. etc
when tried using -mtime option it gives all the files in the last 24hrs from the current time .
please help me out on this ..
thanks (8 Replies)
Discussion started by: sparks
8 Replies
7. Solaris
Hello World ~
HW : SUN Fire V240
OS : Solaris 8
Error message prompts 'rmclomv ... SC login failure ...' on terminal.
and
Error Message prompts continually 'SC Login Failure for user Please login:' on Single Mode(init S)
The System is in normal operation, though
In case of rain, Can... (1 Reply)
Discussion started by: lifegeek
1 Replies
8. Shell Programming and Scripting
Hi,
I need a script that can search a word "Error" in last 10 Hrs generated logs in /log/App1 and /log/App2 folder..
Note these directories have massive log files ...actually our application generate 100 Log files of size 2MB in just a min so script must be fast enough to cater this I... (9 Replies)
Discussion started by: Mujtaba khan
9 Replies
9. HP-UX
I need to find user login name with their First name and last name .Using HP-UX .
i used Finger but couldn't able to get ...
$ finger ravi.kumar@domain.com
ksh: domain.com: not found
i tried with finger kumar ravi
finger ravi kumar but not able to get
It just giving
Login name:... (9 Replies)
Discussion started by: girija
9 Replies
10. UNIX for Dummies Questions & Answers
Hello,
How to get the modified/created files past 2 hours in Solaris with find command?
Thank you. (7 Replies)
Discussion started by: balareddy
7 Replies
LEARN ABOUT MOJAVE
hosts.equiv
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, +@netgroup (from which
only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, +@netgroup (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD