Then you can ask the server1 from other server like this:
Code:
root@server2 # finger @server1
Of course now normal finger will not work.
I'm not sure is there any security issue with that solution. But if your network is secure, then it works fine.
Above example is for Solaris10.
On Solaris 9 you can just edit /etc/inetd.conf.
On Solaris 11 I cat't find finger :/
Can someone tell me the command to display the info about the CPU? I need the CPI id.. of my SUN box. Solaris 8.
It's some totally un-intuitive command, and i can't recall it.
tnx. (3 Replies)
Hi all,
I've searched around and not found any specific solution to my problem, so wondered if someone out there could help.
I'm in the process of migrating some shell scripts from HP UNIX to AIX and one of the scripts uses the 'logname' command.
On HP 'logname' returns the login name,... (8 Replies)
My Linux system was last rebooted few hours ago.
But it seems little confusing for me to figure out the exact reason behind it.
I guess following command should justify what i meant to say.
# date
Wed May 11 13:22:49 IST 2011
# last | grep "May 10"
reboot system boot 2.6.18-194.el5 ... (5 Replies)
Hi!
I want to extract the uptime from the output of the uptime command.
The output:
11:53 up 3:02, 2 users, load averages: 0,32 0,34 0,43
I just need the "3:02" part. How can I do this?
Dirk (6 Replies)
Hello folks,
uptime command not shows how long the system has been up.
I know it come from a corruption of /var/adm/utmpx file.
I've done :
cat /dev/null > /var/adm/utmpx
Now who and last commands work fine. But uptime still give me back an answer without the "up time".
In which... (6 Replies)
I know the ipaddress of a remote machine and would like to know its hostname
I used the nslookup command but... is there an easier way of doing it... just like hostname command.
When i give this command i get the following
nslookup 10.2.47.36
Server: 10.233.04.31
Address: ... (2 Replies)
OK folks, my first post here.. hope the community can come up with a clever solution. Cross posting this in the Solaris and Shell scripting forums, as problem is scripting problem specifically on Solaris platform.
I am trying to detect a host's uptime with greater precision than is offered up... (1 Reply)
OK folks, my first post here.. hope the community can come up with a clever solution. Cross posting this in the Solaris and Shell scripting forums, as problem is scripting problem specifically on Solaris platform.
I am trying to detect a host's uptime with greater precision than is offered up... (1 Reply)
How to find Physical server uptime from HMC/ ASMI.
Server was in standby mode. We have started the Lpar manually. Server rebooted automatically but no information updated in Lpars's errpt, alog.console or HMC prior to the reboot. (1 Reply)
Discussion started by: sunnybee
1 Replies
LEARN ABOUT REDHAT
fingerd
FINGERD(8) BSD System Manager's Manual FINGERD(8)NAME
fingerd -- remote user information server
SYNOPSIS
fingerd [-wulf] [-pL path] [-t timeout]
DESCRIPTION
Fingerd is a simple daemon based on RFC1196 that provides an interface to the ``finger'' program at most network sites. The program is sup-
posed to return a friendly, human-oriented status report on either the system at the moment or a particular person in depth.
If the -w option is given, remote users will get an additional ``Welcome to ...'' banner which also shows some informations (e.g. uptime,
operating system name and release) about the system the fingerd is running on. Some sites may consider this a security risk as it gives out
information that may be useful to crackers.
If the -u option is given, requests of the form ``finger @host'' are rejected.
If the -l option is given, information about requests made is logged. This option probably violates users' privacy and should not be used on
multiuser boxes.
If the -f option is given, finger forwarding (user@host1@host2) is allowed. Useful behind firewalls, but probably not wise for security and
resource reasons.
The -p option allows specification of an alternate location for fingerd to find the ``finger'' program. The -L option is equivalent.
The -t option specifies the time to wait for a request before closing the connection. A value of 0 waits forever. The default is 60 sec-
onds.
Options to fingerd should be specified in /etc/xinetd.d/finger.
The finger protocol consists mostly of specifying command arguments. The xinetd(8) ``super-server'' runs fingerd for TCP requests received
on port 79. Once connected fingerd reads a single command line terminated by a <CRLF> which is passed to finger(1). It closes its connec-
tions as soon as all output is finished.
If the line is empty (i.e. just a <CRLF> is sent) then finger returns a ``default'' report that lists all people logged into the system at
that moment. This feature is blocked by the -u option.
If a user name is specified (e.g. eric<CRLF>) then the response lists more extended information for only that particular user, whether
logged in or not. Allowable ``names'' in the command line include both ``login names'' and ``user names''. If a name is ambiguous, all pos-
sible derivations are returned.
SEE ALSO finger(1), xinetd(8)RESTRICTIONS
Connecting directly to the server from a TIP or an equally narrow-minded TELNET-protocol user program can result in meaningless attempts at
option negotiation being sent to the server, which will foul up the command line interpretation.
HISTORY
The finger daemon appeared in 4.3BSD.
Linux NetKit (0.17) August 29, 1996 Linux NetKit (0.17)