.\" -*- mode: troff; coding: utf-8 -*- .\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. .ie n \{\ . ds C` "" . ds C' "" 'br\} .el\{\ . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{\ . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" ======================================================================== .\" .IX Title "LIVESYS 1" .TH LIVESYS 1 2024-03-20 OpenAFS "AFS Command Reference" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH NAME livesys \- Reports the configured CPU/operating system type .SH SYNOPSIS .IX Header "SYNOPSIS" \&\fBlivesys\fR .SH DESCRIPTION .IX Header "DESCRIPTION" The \fBlivesys\fR command displays the string stored in kernel memory that indicates the local machine's CPU/operating system (OS) type, conventionally called the \fIsysname\fR. The Cache Manager substitutes this string for the \fR\f(CI@sys\fR\fI\fR variable which can occur in AFS pathnames; the \&\fIOpenAFS Quick Start Guides\fR and \fIOpenAFS Administration Guide\fR explain how using \fI\fR\f(CI@sys\fR\fI\fR can simplify cell configuration. .PP To set a new value in kernel memory, use the \fBfs sysname\fR command, which can also be used to view the current value. If a sysname list was set using \fBfs sysname\fR, only the first value in the list will be reported by \&\fBlivesys\fR. .SH CAUTIONS .IX Header "CAUTIONS" To see the full sysname list, use \fBfs sysname\fR rather than this command. \&\fBlivesys\fR is mostly useful for scripts that need to know the primary sysname for the local system (to create directories that will later be addressed using \fR\f(CI@sys\fR\fI\fR, for example). .PP \&\fBlivesys\fR first appeared in OpenAFS 1.2.2. Scripts that need to support older versions of AFS should parse the output of \fBfs sysname\fR or use \&\fBsys\fR. .SH OUTPUT .IX Header "OUTPUT" The machine's system type appears as a text string, by itself, on a single line. .SH EXAMPLES .IX Header "EXAMPLES" The following example shows the output produced on a Linux system with a 2.6 kernel: .PP .Vb 2 \& % livesys \& i386_linux26 .Ve .SH "PRIVILEGE REQUIRED" .IX Header "PRIVILEGE REQUIRED" None .SH "SEE ALSO" .IX Header "SEE ALSO" \&\fBfs_sysname\fR\|(1), \&\fBsys\fR\|(1) .PP The \fIOpenAFS Quick Start Guides\fR at . .PP The \fIOpenAFS Administration Guide\fR at . .SH COPYRIGHT .IX Header "COPYRIGHT" IBM Corporation 2000. All Rights Reserved. .PP Copyright 2005 Russ Allbery .PP This documentation is covered by the IBM Public License Version 1.0. It was written by Russ Allbery based on the \fBsys\fR man page.