NEX-9586 remove nodename from the default savecore directory path
Reviewed by: Dan Fields <dan.fields@nexenta.com>
Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com>
Reviewed by: Sanjay Nadkarni <sanjay.nadkarni@nexenta.com>

@@ -1,13 +1,13 @@
 '\" te
 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
-.\" Copyright 2015 Nexenta Systems, Inc.  All Rights Reserved.
+.\" Copyright 2017 Nexenta Systems, Inc.  All Rights Reserved.
 .\" Copyright (c) 2013 by Delphix. All rights reserved.
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
-.TH DUMPADM 1M "Apr 09, 2015"
+.TH DUMPADM 1M "Feb 13, 2017"
 .SH NAME
 dumpadm \- configure operating system crash dump
 .SH SYNOPSIS
 .LP
 .nf

@@ -15,11 +15,10 @@
      [\fB-m\fR \fImin\fRk | \fImin\fRm | \fImin\fR%] [\fB-s\fR \fIsavecore-dir\fR]
      [\fB-r\fR \fIroot-dir\fR] [\fB-z\fR on | off]
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBdumpadm\fR program is an administrative command that manages the
 configuration of the operating system crash dump facility. A crash dump is a
 disk copy of the physical memory of the computer at the time of a fatal system
 error. When a fatal operating system error occurs, a message describing the

@@ -63,11 +62,11 @@
 .nf
 example# \fBdumpadm\fR
 
       Dump content: kernel pages
        Dump device: /dev/dsk/c0t0d0s1 (swap)
-Savecore directory: /var/crash/saturn
+Savecore directory: /var/crash
   Savecore enabled: yes
    Save compressed: on
 .fi
 .in -2
 .sp

@@ -76,20 +75,19 @@
 .LP
 When no options are specified, \fBdumpadm\fR prints the current crash dump
 configuration. The example shows the set of default values: the dump content is
 set to kernel memory pages only, the dump device is a swap disk partition, the
 directory for \fBsavecore\fR files is set to
-\fB/var/crash/\fR\fIhostname\fR\fB,\fR \fBsavecore\fR is set to run
+\fB/var/crash\fR, \fBsavecore\fR is set to run
 automatically on reboot, and compression is turned on.
 .sp
 .LP
 When one or more options are specified, \fBdumpadm\fR verifies that your
 changes are valid, and if so, reconfigures the crash dump parameters and
 displays the resulting configuration. You must be \fBroot\fR to view or change
 dump parameters.
 .SH OPTIONS
-.sp
 .LP
 The following options are supported:
 .sp
 .ne 2
 .na

@@ -284,13 +282,11 @@
 Modify the dump configuration to use the specified directory to save files
 written by \fBsavecore\fR. The directory should be an absolute path and exist
 on the system. If upon reboot the directory does not exist, it will be created
 prior to the execution of \fBsavecore\fR. See the \fBNOTES\fR section below for
 a discussion of security issues relating to access to the savecore directory.
-The default savecore directory is \fB/var/crash/\fIhostname\fR\fR where
-\fIhostname\fR is the output of the \fB-n\fR option to the \fBuname\fR(1)
-command.
+The default savecore directory is \fB/var/crash\fR.
 .RE
 
 .sp
 .ne 2
 .na

@@ -341,19 +337,18 @@
 .nf
 example# dumpadm -d /dev/dsk/c0t2d0s2
 
            Dump content: kernel pages
             Dump device: /dev/dsk/c0t2d0s2 (dedicated)
-     Savecore directory: /var/crash/saturn
+     Savecore directory: /var/crash
        Savecore enabled: yes
         Save compressed: on
 .fi
 .in -2
 .sp
 
 .SH EXIT STATUS
-.sp
 .LP
 The following exit values are returned:
 .sp
 .ne 2
 .na

@@ -384,11 +379,10 @@
 .RS 4n
 Invalid command line options were specified.
 .RE
 
 .SH FILES
-.sp
 .ne 2
 .na
 \fB\fB/dev/dump\fR\fR
 .ad
 .sp .6

@@ -417,16 +411,14 @@
 Contains minimum amount of free space for \fIsavecore-directory\fR. See
 \fBsavecore\fR(1M).
 .RE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBsvcs\fR(1), \fBuname\fR(1), \fBsavecore\fR(1M), \fBsvcadm\fR(1M),
 \fBswap\fR(1M), \fBattributes\fR(5), \fBsmf\fR(5)
 .SH NOTES
-.sp
 .LP
 The system crash dump service is managed by the service management facility,
 \fBsmf\fR(5), under the service identifier:
 .sp
 .in +2

@@ -440,11 +432,10 @@
 .LP
 Administrative actions on this service, such as enabling, disabling, or
 requesting restart, can be performed using \fBsvcadm\fR(1M). The service's
 status can be queried using the \fBsvcs\fR(1) command.
 .SS "Dump Device Selection"
-.sp
 .LP
 When the special \fBswap\fR token is specified as the argument to \fBdumpadm\fR
 \fB-d\fR the utility will attempt to configure the most appropriate swap device
 as the dump device. \fBdumpadm\fR configures the largest swap block device as
 the dump device; if no block devices are available for swap, the largest swap

@@ -451,11 +442,10 @@
 entry is configured as the dump device. If no swap entries are present, or none
 can be configured as the dump device, a warning message will be displayed.
 While local and remote swap files can be configured as the dump device, this is
 not recommended.
 .SS "Dump Device/Swap Device Interaction (UFS File Systems Only)"
-.sp
 .LP
 In the event that the dump device is also a swap device, and the swap device is
 deleted by the administrator using the \fBswap\fR \fB-d\fR command, the
 \fBswap\fR command will automatically invoke \fBdumpadm\fR \fB-d\fR \fBswap\fR
 in order to attempt to configure another appropriate swap device as the dump

@@ -470,11 +460,10 @@
 stored in the configuration file for subsequent reboots. If a larger or more
 appropriate swap device is added by the administrator, the dump device is not
 changed; the administrator must re-execute \fBdumpadm\fR \fB-d\fR \fBswap\fR to
 reselect the most appropriate device fom the new list of swap devices.
 .SS "Minimum Free Space"
-.sp
 .LP
 If the \fBdumpadm\fR \fB-m\fR option is used to create a \fBminfree\fR file
 based on a percentage of the total size of the file system containing the
 savecore directory, this value is not automatically recomputed if the file
 system subsequently changes size.  In this case, the administrator must

@@ -481,11 +470,10 @@
 re-execute \fBdumpadm\fR \fB-m\fR to recompute the \fBminfree\fR value. If no
 such file exists in the savecore directory, \fBsavecore\fR will default to a
 free space threshold of one megabyte. If no free space threshold is desired, a
 minfree file containing size 0 can be created.
 .SS "Security Issues"
-.sp
 .LP
 If, upon reboot, the specified savecore directory is not present, it will be
 created prior to the execution of \fBsavecore\fR with permissions 0700 (read,
 write, execute by owner only) and owner \fBroot\fR. It is recommended that
 alternate savecore directories also be created with similar permissions, as the