Sponsored Content
Operating Systems Solaris Solaris Finger Service Problem Post 302708547 by mvhoward on Monday 1st of October 2012 06:08:52 PM
Old 10-01-2012
Quote:
Originally Posted by bartus11
Right. And this?
Code:
inetadm -l | grep finger

I get nothing returned for that as well:

Code:
inetadm -l | grep finger
Usage:
  inetadm
  inetadm -?
  inetadm -l {FMRI | pattern}...
  inetadm -e {FMRI | pattern}...
  inetadm -d {FMRI | pattern}...
  inetadm -m {FMRI | pattern}... {name=value}...
  inetadm -M {name=value}...

 

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
inetadm(1M)                                               System Administration Commands                                               inetadm(1M)

NAME
inetadm - observe or configure inetd-controlled services SYNOPSIS
inetadm inetadm -? inetadm -p inetadm -l {FMRI | pattern} inetadm -e {FMRI | pattern} inetadm -d {FMRI | pattern} inetadm -m {FMRI | pattern} ... {name=value} ... inetadm -M {name=value} ... DESCRIPTION
The inetadm utility provides the following capabilities for inetd-managed SMF services: o Provides a list of all such services installed. o Lists the services' properties and values. o Allows enabling and disabling of services. o Allows modification of the services'property values, as well as the default values provided by inetd. See smf(5) for a description of an SMF service. With no arguments, inetadm lists all services under inetd(1M) control, including such attributes as their current run state and whether or not they are enabled. OPTIONS
For options taking one or more FMRI operands (see smf(5) for a description of an FMRI), if the operand specifies a service (instead of a service instance), and that service has only a single instance, inetadm operates on that instance. If a service name is supplied and it contains more than one instances or a pattern is supplied and and it matches more than one instance, a warning message is displayed and that operand is ignored. For those options taking name=value parameters, a description of each of the possible names and the allowed values is found in the inetd(1M) man page. The following options are supported: -? Display a usage message. -p Lists all default inet service property values provided by inetd in the form of name=value pairs. If the value is of boolean type, it is listed as TRUE or FALSE. -l {FMRI | pattern}... List all properties for the specified service instances as name=value pairs. In addition, if the property value is inherited from the default value provided by inetd, the name=value pair is identified by the token (default). Property inheritance occurs when properties do not have a specified service instance default. -e {FMRI | pattern}... Enable the specified service instances. -d {FMRI | pattern}... Disable the specified service instances. -m {FMRI | pattern}...{name=value}... Change the values of the specified properties of the identified service instances. Properties are specified as whitespace-separated name=value pairs. To remove an instance-specific value and accept the default value for a property, simply specify the property without a value, for example, name= . -M {name=value}... Change the values of the specified inetd default properties. Properties are specified as whitespace-separated name=value pairs. EXAMPLES
Example 1: Displaying Properties for a Service The following command displays the properties for the spray service. # inetadm -l network/rpc/spray:default SCOPE NAME=VALUE name="sprayd" endpoint_type="tli" proto="datagram_v" isrpc=TRUE rpc_low_version=1 rpc_high_version=1 wait=TRUE exec="/usr/lib/netsvc/spray/rpc.sprayd" user="root" default bind_addr="" default bind_fail_max=-1 default bind_fail_interval=-1 default max_con_rate=-1 default max_copies=-1 default con_rate_offline=-1 default failrate_cnt=40 default failrate_interval=60 default inherit_env=TRUE default tcp_trace=FALSE default tcp_wrappers=FALSE Example 2: Displaying Default Properties The following command displays default properties. # inetadm -p NAME=VALUE bind_addr="" bind_fail_max=-1 bind_fail_interval=-1 max_con_rate=-1 max_copies=-1 con_rate_offline=-1 failrate_cnt=40 failrate_interval=60 inherit_env=TRUE tcp_trace=FALSE tcp_wrappers=FALSE Example 3: Changing Property Values for a Service The following command changes rpc_high_version to 3 and tcp_trace to TRUE for the spray service. # inetadm -m network/rpc/spray:default rpc_high_version=3 tcp_trace=TRUE # inetadm -l network/rpc/spray:default SCOPE NAME=VALUE name="sprayd" endpoint_type="tli" proto="datagram_v" isrpc=TRUE rpc_low_version=1 rpc_high_version=3 wait=TRUE exec="/usr/lib/netsvc/spray/rpc.sprayd" user="root" default bind_addr="" default bind_fail_max=-1 default bind_fail_interval=-1 default max_con_rate=-1 default max_copies=-1 default con_rate_offline=-1 default failrate_cnt=40 default failrate_interval=60 default inherit_env=TRUE tcp_trace=TRUE default tcp_wrappers=FALSE EXIT STATUS
The following exit values are returned: 0 Operation completed successfully. 1 A fatal error occurred. An accompanying error message will provide further information. 2 Invalid arguments were supplied, such as an ambiguous service FMRI or pattern. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
inetd(1M), svccfg(1M), attributes(5), smf(5) SunOS 5.10 17 Dec 2004 inetadm(1M)
All times are GMT -4. The time now is 08:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy