Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

fs_messages(1) [xfree86 man page]

FS_MESSAGES(1)						       AFS Command Reference						    FS_MESSAGES(1)

NAME
       fs_messages - Sets whether the Cache Manager writes log messages

SYNOPSIS
       fs messages [-show (user|console|all|none)] [-help]

       fs me [-s (user|console|all|none)] [-h]

DESCRIPTION
       The fs messages command controls whether the Cache Manager displays status and warning messages on user screens, the client machine
       console, on both, or on neither.

       There are two types of Cache Manager messages:

       o   User messages provide user-level status and warning information, and the Cache Manager directs them to user screens.

       o   Console messages provide system-level status and warning information, and the Cache Manager directs them to the client machine's
	   designated console.

       Disabling messaging completely is not recommended, because the messages provide useful status and warning information.

OPTIONS
       -show (user|console|all|none)
	   Specifies the types of messages to display. Choose one of the following values:

	   user
	       Send user messages to user screens.

	   console
	       Send console messages to the console.

	   all Send user messages to user screens and console messages to the console (the default if the -show argument is omitted).

	   none
	       Do not send any messages to user screens or the console.

       -help
	   Prints the online help for this command. All other valid options are ignored.

EXAMPLES
       The following command instructs the Cache Manager to display both types of messages:

	  % fs messages -show all

PRIVILEGE REQUIRED
       The issuer must be logged in as the local superuser root.

SEE ALSO
       afsd(8)

COPYRIGHT
       IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

       This documentation is covered by the IBM Public License Version 1.0.  It was converted from HTML to POD by software written by Chas
       Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

OpenAFS 							    2012-03-26							    FS_MESSAGES(1)

Check Out this Related Man Page

FS_GETCLIENTADDRS(1)					       AFS Command Reference					      FS_GETCLIENTADDRS(1)

NAME
fs_getclientaddrs - Displays the client interfaces to register SYNOPSIS
fs getclientaddrs [-help] fs gc [-h] fs getcl [-h] DESCRIPTION
The fs getclientaddrs command displays the IP addresses of the interfaces that the local Cache Manager registers with a File Server when first establishing a connection to it. The File Server uses the addresses when it initiates a remote procedure call (RPC) to the Cache Manager (as opposed to responding to an RPC sent by the Cache Manager). There are two common circumstances in which the File Server initiates RPCs: when it breaks callbacks and when it pings the client machine to verify that the Cache Manager is still accessible. If an RPC to that interface fails, the File Server simultaneously sends RPCs to all of the other interfaces in the list, to learn which of them are still available. Whichever interface replies first is the one to which the File Server then sends pings and RPCs to break callbacks. fs_setclientaddrs(1) explains how the Cache Manager constructs the list automatically in kernel memory as it initializes, and how to use that command to alter the kernel list after initialization. CAUTIONS
The File Server uses the list of interfaces displayed by this command only when selecting an alternative interface after a failed attempt to break a callback or ping the Cache Manager. When responding to the Cache Manager's request for file system data, the File Server replies to the interface which the Cache Manager used when sending the request. If the File Server's reply to a data request fails, the file server machine's network routing configuration determines which alternate network routes to the client machine are available for resending the reply. The displayed list applies to all File Servers to which the Cache Manager connects in the future. It is not practical to register different sets of addresses with different File Servers, because it requires using the fs setclientaddrs command to change the list and then rebooting each relevant File Server immediately. The displayed list is not necessarily governing the behavior of a given File Server, if an administrator has issued the fs setclientaddrs command since the Cache Manager first contacted that File Server. It determines only which addresses the Cache Manager registers when connecting to File Servers in the future. The list of interfaces does not influence the Cache Manager's choice of interface when establishing a connection to a File Server. OPTIONS
-help Prints the online help for this command. All other valid options are ignored. OUTPUT
The output displays the IP address of each interface that the Cache Manager is currently registering with File Server processes that it contacts, with one address per line. The File Server initially uses the first address for breaking callbacks and pinging the Cache Manager, but the ordering of the other interfaces is not meaningful. EXAMPLES
The following example displays the two interfaces that the Cache Manager is registering with File Servers. % fs getclientaddrs 192.12.105.68 192.12.108.84 PRIVILEGE REQUIRED
None SEE ALSO
fileserver(8), fs_setclientaddrs(1) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 FS_GETCLIENTADDRS(1)
Man Page