Sponsored Content
Operating Systems Solaris Solaris Finger Service Problem Post 302709793 by bartus11 on Wednesday 3rd of October 2012 03:09:16 PM
Old 10-03-2012
Well, you didn't include the "LIST" part. It is very important in this case as it would show only the ports open for connections. Anyway from that you posted it is clear that finger is not running on your server. Did you check what "zonename" is returning?
This User Gave Thanks to bartus11 For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

What is plan that comes when you use finger "usename" on solaris ?

Hai, In order to find out a user we can use finger "username" . The output of finger command has various details in the following manner : Login name: xyz In real life: xyz Directory: /home/xys Shell: /bin/ksh No unread mail No plan What is the plan... (1 Reply)
Discussion started by: ajphaj
1 Replies

2. Solaris

service in solaris

hi frnds What is the command for checking all the services running in the solaris. mit (3 Replies)
Discussion started by: naik_mit
3 Replies

3. UNIX for Advanced & Expert Users

help with list service for Solaris 10x86

I need help finding a free download for a list service like list serv for solaris 10 x86 ? Anyone (0 Replies)
Discussion started by: parente
0 Replies

4. Solaris

Solaris service tag

Hi all, please can any one help me to know the service tag of the solaris machine .Is there any command to get the service tag from remote machine which has been connected through telnet or ssh. thanks in advance sorry for my english (9 Replies)
Discussion started by: pratheepv
9 Replies

5. Solaris

service error on solaris 10

Hi, I am getting following error on my sparc box running solaris 10 - maintenance Feb_12 svc:/network/cswvncserver:default In log file, following logs are found - Following logs are found - /sbin/sh: /var/opt/csw/svc/method/svc-cswvncserver: cannot execute vncserver: couldn't find... (2 Replies)
Discussion started by: sunadmin
2 Replies

6. Solaris

service error on solaris 10

Hi, I am getting following error on my sparc box running solaris 10 - maintenance Feb_12 svc:/application/management/scx-cimd:default In log file, following logs are found - Starting Cim server daemon Stopping Cim server daemon CIM Server stopped. CIM Server stopped... (2 Replies)
Discussion started by: sunadmin
2 Replies

7. Solaris

Having problems with finger on Solaris 10

I have a bunch of Solaris systems and for the 8/9 systems, I can type "finger -s 2" to get a list of all users (whether they are logged in or not) and the last time they logged in. I have some new 10 systems and this command does not work. Does anybody know whether this was changed in Solaris 10?... (6 Replies)
Discussion started by: Muller
6 Replies

8. Solaris

Not able to start cron service in Solaris 10

Hi, This is Solaris-10 x86. I am not able to start cron service, configured in FMRI. It is in maintenance and when I clear it, it seems like calling and failing on /etc/init.d/tcs-rtm script. I am not able to figure out, why cron is calling that script, if this failure is because of that. Cron... (5 Replies)
Discussion started by: ron323232
5 Replies

9. Solaris

Not able to disable finger & telnet command in Solaris 8

Hi I need to disable finger & telnet command in solaris 8 I have put the # infront of finger and telnet line in /etc/inetd.conf file. Further I have run the below command kill -1 <process id of inetd > But when I am running finger command it is till giving information for remote machine... (8 Replies)
Discussion started by: amity
8 Replies
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. Starting and stopping the daemon is handled by systemd(1). Fingerd is not enabled by default after the installation. Its running state can be managed using systemctl(1) commands. If you need to specify some options to fingerd you should copy the finger@.service file from /lib/systemd/system to /etc/systemd/system and edit it there. The finger protocol consists mostly of specifying command arguments. The systemd(1) 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 connections 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), systemd(1), systemctl(1) 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)
All times are GMT -4. The time now is 11:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy