개요

• 솔라나라에 설명된 어플리케이션에 대해 맨 페이지를 찾아 출력한다.
• MAN 페이지에 대한 설명은 윈디하나의 솔라나라: MAN 페이지을 참고하자.
• svcadm(1M)을 검색하려면 섹션에서 1M 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.

sum(1)

sum(1)                           User Commands                          sum(1)



NAME
       sum - print checksum and block count for a file

SYNOPSIS
       /usr/bin/sum [-r] [file...]

DESCRIPTION
       The sum lists the checksum for each of its file arguments. The standard
       input is read if there are no file arguments.

OPTIONS
       The following option is supported:

       -r    Use an alternate (machine-dependent) algorithm in  computing  the
             checksum.


OPERANDS
       The following operands are supported:

       file    A  path  name  of  a  file. If no files are named, the standard
               input is used.


ENVIRONMENT VARIABLES
       See environ(7) for descriptions of the following environment  variables
       that affect the execution of sum: LC_CTYPE, LC_MESSAGES, and NLSPATH.

EXIT STATUS
       The following exit values are returned.

       0      Successful completion.


       > 0    An error occurred.


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


       tab()  box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE TYPEAT‐
       TRIBUTE VALUE _ Availabilitysystem/core-os _ CSIEnabled


SEE ALSO
       cksum(1), digest(1),  getconf(1),  wc(1),  libmd(3LIB),  attributes(7),
       environ(7)

DIAGNOSTICS
       Read error is indistinguishable from end of file on most devices. Check
       the block count.

NOTES
       Portable applications should use cksum(1). The  default  algorithm  for
       this  command  is defined in the POSIX standard and is identical across
       platforms.


       The sum command is typically used to quickly  compare  a  suspect  file
       against  a  trusted  version  of the same, such as to ensure that files
       transmitted over noisy media arrive intact.  However,  this  comparison
       cannot  be considered cryptographically secure. When compatibility with
       existing sum usage or values is not required, the digest(1) command  is
       recommended instead, as it provides more modern and secure algorithms.


       In previous releases of Solaris, there was a /usr/ucb/sum that returned
       a different checksum than the sum command described here due to differ‐
       ent blocksizes and algorithms used. The command sum uses 512 byte block
       sizes while /usr/ucb/sum used 1024 byte block sizes.



Oracle Solaris 11.4               16 Jun 2020                           sum(1)