Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   20441 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

ds.log(4)			 File Formats			     ds.log(4)

NAME
       ds.log - Availability Suite data services log file

DESCRIPTION
       The  /var/adm/ds.log file contains the Availability Suite data services
       command log. The administration commands log activities to the file  in
       the format:

	 date time product: message

       Note  that  when	 the size of the log file exceeds 10 Mbytes, ds.log is
       renamed	/var/adm/ds.log.bak  and a new /var/adm/ds.log	file  is  cre‐
       ated.

       The ds.log fields are:

       date

	   The date format is mmm nn, where mmm	 is  the local three-character
	   abbreviation for the month and nn is the day of the month on	 which
	   the event occurred.

       time

	   The time of the event, in hh:mm:ss format.

       product

	   A product code that identifies which component of the data services
	   produced the event. The code is separated  from  the	 message  that
	   follows by a colon (:) and a space.

       message

	   A  message  that  can extend over  more  than  one  line describing
	   the event that occurred. The second or following lines are not pre‐
	   fixed by  the  date, time, and product code strings.

EXAMPLES
       The example below shows sample ds.log file content:

	 Jan 25 05:26:17 ii: iiboot suspend cluster tag <none>
	 Jan 25 05:32:02 ii: iiboot resume cluster tag <none>
	 Jan 25 05:32:04 sv: svboot: resume /dev/vx/rdsk/bigmaster
	 Jan 25 05:32:04 sv: svboot: resume /dev/vx/rdsk/bigshadow
	 Jan 25 05:32:04 sv: svboot: resume /dev/vx/rdsk/mstvxfs
	 Jan 25 05:32:04 sv: svboot: resume /dev/vx/rdsk/master01

ATTRIBUTES
       See attributes(5) for descriptions of the following attributes:

       ┌─────────────────────┬─────────────────────────────────────────────────────────┐
       │   ATTRIBUTE TYPE    │			   ATTRIBUTE VALUE		       │
       ├─────────────────────┼─────────────────────────────────────────────────────────┤
       │Architecture	     │ x86						       │
       ├─────────────────────┼─────────────────────────────────────────────────────────┤
       │Availability	     │ service/storage/avs/cache-management		       │
       ├─────────────────────┼─────────────────────────────────────────────────────────┤
       │Interface Stability  │ Committed					       │
       └─────────────────────┴─────────────────────────────────────────────────────────┘

SEE ALSO
       iiadm(1M), sndradm(1M), svadm(1M), attributes(5)

SunOS 5.11			  08 Jun 2007			     ds.log(4)

Vote for polarhome