您所在的位置： &
详细解析Linux scp命令的应用
详细解析Linux scp命令的应用
Linux命令有人统计说是有4000多个，Linux scp命令是用于Linux之间复制文件和目录，这里详细介绍scp命令使用和参数。
Linux scp命令用于Linux之间复制文件和目录，具体如何使用这里好好介绍一下，从本地复制到远程、从远程复制到本地是两种使用方式。这里有具体举例：
==================
Linux scp 命令
==================
scp 可以在 2个 linux 主机间复制文件；
命令基本格式：
scp [可选参数] file_source file_target
从 本地 复制到 远程
* 复制文件：
* 命令格式：
scp local_file remote_username@remote_ip:remote_folder
scp local_file remote_username@remote_ip:remote_file
scp local_file remote_ip:remote_folder
scp local_file remote_ip:remote_file
第1,2个指定了用户名，命令执行后需要再输入密码，第1个仅指定了远程的目录，文件名字不变，第2个指定了文件名；
第3,4个没有指定用户名，命令执行后需要输入用户名和密码，第3个仅指定了远程的目录，文件名字不变，第4个指定了文件名；
scp /home/space/music/1.mp3 root@www.:/home/root/others/music
scp /home/space/music/1.mp3 root@www.:/home/root/others/music/001.mp3
scp /home/space/music/1.mp3 www.:/home/root/others/music
scp /home/space/music/1.mp3 www.:/home/root/others/music/001.mp3
* 复制目录：
* 命令格式：
scp -r local_folder remote_username@remote_ip:remote_folder
scp -r local_folder remote_ip:remote_folder
第1个指定了用户名，命令执行后需要再输入密码；
第2个没有指定用户名，命令执行后需要输入用户名和密码；
scp -r /home/space/music/ root@www.:/home/root/others/
scp -r /home/space/music/ www.:/home/root/others/
上面 命令 将 本地 music 目录 复制 到 远程 others 目录下，即复制后有 远程 有 ../others/music/ 目录
从 远程 复制到 本地
从 远程 复制到 本地，只要将 从 本地 复制到 远程 的命令 的 后2个参数 调换顺序 即可；
scp root@www.:/home/root/others/music /home/space/music/1.mp3
scp -r www.:/home/root/others/ /home/space/music/
最简单的应用如下 :
scp 本地用户名 @IP 地址 : 文件名 1 远程用户名 @IP 地址 : 文件名 2
[ 本地用户名 @IP 地址 :] 可以不输入 , 可能需要输入远程用户名所对应的密码 .
可能有用的几个参数 :
-v 和大多数 linux 命令中的 -v 意思一样 , 用来显示进度 . 可以用来查看连接 , 认证 , 或是配置错误 .
-C 使能压缩选项 .
-P 选择端口 . 注意 -p 已经被 rcp 使用 .
-4 强行使用 IPV4 地址 .
-6 强行使用 IPV6 地址 .
Linux scp命令的使用方法应该可以满足大家对Linux文件和目录的复制使用了。
【编辑推荐】
【责任编辑： TEL：（010）】
关于的更多文章
智能化运维是用机器来代替运维人员，在最少人工干预下，结合运用
随着云计算、物联网、大数据、移动互联网的大发展，你应该知道这些。
讲师： 26人学习过讲师： 14人学习过讲师： 33人学习过
性能监测是系统优化过程中重要的一环，如果没有监测、
OS X Server的Mavericks版本并没有发生这样巨大的变化
近几年，开源业界的创新发展很繁荣，不仅在软件层面，
本书全面翔实地介绍了各种病毒的原理，以操作系统的发展为主线，结合病毒的发展过程来综合分析病毒。在分析工具上，较多地利用了
51CTO旗下网站 Version 3.6.2
OFFIS DICOM Toolkit
storescp [options] [port]
DESCRIPTION
The storescp application implements a Service Class Provider (SCP) for the Storage Service Class. It listens on a specific TCP/IP port for incoming association requests from a Storage Service Class User (SCU) and can receive both DICOM images and other DICOM composite objects. The storescp application also supports the Verification Service Class as an SCP.
PARAMETERS
tcp/ip port number to listen on
(this parameter is required unless the --inetd option is specified)
general options
print this help text and exit
print version information and exit
--arguments
print expanded command line arguments
quiet mode, print no warnings and errors
verbose mode, print processing details
debug mode, print debug information
--log-level
[l]evel: string constant
(fatal, error, warn, info, debug, trace)
use level l for the logger
--log-config
[f]ilename: string
use config file f for the logger
--verbose-pc
show presentation contexts in verbose mode
multi-process options
--single-process
single process mode (default)
fork child process for each association
network options
association negotiation profile from configuration file:
--config-file
[f]ilename [p]rofile: string
use profile p from config file f
preferred network transfer syntaxes (not with --config-file):
--prefer-uncompr
prefer explicit VR local byte order (default)
--prefer-little
prefer explicit VR little endian TS
--prefer-big
prefer explicit VR big endian TS
--prefer-lossless
prefer default JPEG lossless TS
--prefer-jpeg8
prefer default JPEG lossy TS for 8 bit data
--prefer-jpeg12
prefer default JPEG lossy TS for 12 bit data
--prefer-j2k-lossless
prefer JPEG 2000 lossless TS
--prefer-j2k-lossy
prefer JPEG 2000 lossy TS
--prefer-jls-lossless
prefer JPEG-LS lossless TS
--prefer-jls-lossy
prefer JPEG-LS lossy TS
--prefer-mpeg2
prefer MPEG2 Main Profile @ Main Level TS
--prefer-mpeg2-high
prefer MPEG2 Main Profile @ High Level TS
--prefer-mpeg4
prefer MPEG4 AVC/H.264 High Profile / Level 4.1 TS
--prefer-mpeg4-bd
prefer MPEG4 AVC/H.264 BD-compatible HP / Level 4.1 TS
--prefer-mpeg4-2-2d
prefer MPEG4 AVC/H.264 HP / Level 4.2 TS for 2D Videos
--prefer-mpeg4-2-3d
prefer MPEG4 AVC/H.264 HP / Level 4.2 TS for 3D Videos
--prefer-mpeg4-2-st
prefer MPEG4 AVC/H.264 Stereo HP / Level 4.2 TS
--prefer-hevc
prefer HEVC H.265 Main Profile / Level 5.1 TS
--prefer-hevc10
prefer HEVC H.265 Main 10 Profile / Level 5.1 TS
--prefer-rle
prefer RLE lossless TS
--prefer-deflated
prefer deflated explicit VR little endian TS
--implicit
accept implicit VR little endian TS only
--accept-all
accept all supported transfer syntaxes
network host access control (tcp wrapper):
--access-full
accept connections from any host (default)
--access-control
enforce host access control rules
other network options:
run from inetd super server (not with --fork)
# not available on all systems (e.g. not on Windows)
--socket-timeout
[s]econds: integer (default: 60)
timeout for network socket (0 for none)
--acse-timeout
[s]econds: integer (default: 30)
timeout for ACSE messages
--dimse-timeout
[s]econds: integer (default: unlimited)
timeout for DIMSE messages
[a]etitle: string
set my AE title (default: STORESCP)
[n]umber of bytes: integer ()
set max receive pdu to n bytes (default: 16384)
--disable-host-lookup
disable hostname lookup
refuse association
reject association if no implementation class UID
ignore store data, receive but do not store
--sleep-after
[s]econds: integer
sleep s seconds after store (default: 0)
--sleep-during
[s]econds: integer
sleep s seconds during store (default: 0)
--abort-after
abort association after receipt of C-STORE-RQ
(but before sending response)
--abort-during
abort association during receipt of C-STORE-RQ
--promiscuous
promiscuous mode, accept unknown SOP classes
(not with --config-file)
--uid-padding
silently correct space-padded UIDs
transport layer security (TLS) options
transport protocol stack:
--disable-tls
use normal TCP/IP connection (default)
--enable-tls
[p]rivate key file, [c]ertificate file: string
use authenticated secure TLS connection
private key password (only with --enable-tls):
--std-passwd
prompt user to type password on stdin (default)
--use-passwd
[p]assword: string
use specified password
--null-passwd
use empty string as password
key and certificate file format:
--pem-keys
read keys and certificates as PEM file (default)
--der-keys
read keys and certificates as DER file
certification authority:
--add-cert-file
[c]ertificate filename: string
add certificate file to list of certificates
--add-cert-dir
[c]ertificate directory: string
add certificates in d to list of certificates
ciphersuite:
[c]iphersuite name: string
add ciphersuite to list of negotiated suites
[f]ilename: string
read DH parameters for DH/DSS ciphersuites
pseudo random generator:
[f]ilename: string
seed random generator with contents of f
--write-seed
write back modified seed (only with --seed)
--write-seed-file
[f]ilename: string (only with --seed)
write modified seed to file f
peer authentication:
--require-peer-cert
verify peer certificate, fail if absent (default)
--verify-peer-cert
verify peer certificate if present
--ignore-peer-cert
don't verify peer certificate
output options
--output-directory
[d]irectory: string (default: ".")
write received objects to existing directory d
bit preserving mode:
allow implicit format conversions (default)
--bit-preserving
write data exactly as read
output file format:
--write-file
write file format (default)
--write-dataset
write data set without file meta information
output transfer syntax
(not with --bit-preserving or compressed transmission):
--write-xfer-same
write with same TS as input (default)
--write-xfer-little
write with explicit VR little endian TS
--write-xfer-big
write with explicit VR big endian TS
--write-xfer-implicit
write with implicit VR little endian TS
--write-xfer-deflated
write with deflated explicit VR little endian TS
post-1993 value representations (not with --bit-preserving):
--enable-new-vr
enable support for new VRs (UN/UT) (default)
--disable-new-vr
disable support for new VRs, convert to OB
group length encoding (not with --bit-preserving):
--group-length-recalc
recalculate group lengths if present (default)
--group-length-create
always write with group length elements
--group-length-remove
always write without group length elements
length encoding in sequences and items (not with --bit-preserving):
--length-explicit
write with explicit lengths (default)
--length-undefined
write with undefined lengths
data set trailing padding
(not with --write-dataset or --bit-preserving):
--padding-off
no padding (default)
--padding-create
[f]ile-pad [i]tem-pad: integer
align file on multiple of f bytes and items on
multiple of i bytes
deflate compression level (only with --write-xfer-deflated/same):
--compression-level
[l]evel: integer (default: 6)
0=uncompressed, 1=fastest, 9=best compression
sorting into subdirectories (not with --bit-preserving):
--sort-conc-studies
[p]refix: string
sort studies using prefix p and a timestamp
--sort-on-study-uid
[p]refix: string
sort studies using prefix p and the Study Instance UID
--sort-on-patientname
sort studies using the Patient's Name and a timestamp
filename generation:
--default-filenames
generate filename from instance UID (default)
--unique-filenames
generate unique filenames
--timenames
generate filename from creation time
--filename-extension
[e]xtension: string
append e to all filenames
event options
--exec-on-reception
[c]ommand: string
execute command c after having received and processed
one C-STORE-RQ message
--exec-on-eostudy
[c]ommand: string
execute command c after having received and processed
all C-STORE-RQ messages that belong to one study
--rename-on-eostudy
having received and processed all C-STORE-RQ messages
that belong to one study, rename output files according
to a certain pattern
--eostudy-timeout
[t]imeout: integer
specifies a timeout of t seconds for end-of-study
determination
--exec-sync
execute command synchronously in foreground
The semantic impacts of the above mentioned options is clear for the majority of options. Some particular options, however, are so specific that they need detailed descriptions which will be given in this passage.
Option &sort-conc-studies enables a user to sort all received DICOM objects into different subdirectories. The sorting will be done with regard to the studies the individual objects belong to, i.e. objects that belong to the same study will be stored in the same subdirectory. In general, a DICOM object d_n+1 is considered to belong to the same study as a DICOM object d_n if and only if d_n and d_n+1 show the exact same values in attribute Study Instance UID. The names of the resulting subdirectories always start with a prefix p which was passed to this option as a parameter. In addition to this prefix, the subdirectory names contain time stamp information with regard to the date and time of reception of this particular study's first DICOM object. In detail, the determination of the subdirectory names pertains to the pattern
[prefix]_[YYYYMMDD]_[HHMMSSPPP]
where YYYY refers to year (4 digits), MM to month (01-12), DD to day (01-31), HH to hour (00-23), MM to minute (00-59), SS to second (00-59) and PPP to milliseconds (000-999). If the prefix is an empty string, the first "_" is omitted.
The other &sort-xxx options work in a similar manner, only the subdirectory names are created differently. For option &sort-on-study-uid the pattern is
[prefix]_[StudyInstanceUID]
and for option &sort-on-patientname
[PatientName]_[YYYYMMDD]_[HHMMSSPPP]
where 'PatientName' is replaced by "ANONYMOUS" if the data element is empty or absent in the data set. Any existing patient name is transformed in order to use only ASCII characters. Please note that in this context only the DICOM default character set (ASCII, i.e. no entry in attribute Specific Character Set) and Latin-1 (Specific Character Set valued "ISO_IR 100") are supported. If another character set is found and the patient name contains non-ASCII characters, a warning is printed and the transformation is performed as if Latin-1 character set would be set in the file. This may lead to unreadable or unexpected patient name directories and behaviour. Thus, it is advisable to use &sort-on-patientname only if Latin-1 or ASCII patient names are expected to be received.
For option &sort-on-study-uid the same subdirectory will be used for all DICOM objects that belong to the same study, i.e. in contrast to the other &sort-xxx options there is no guarantee that a study directory is ever completed.
Option &timenames creates filenames from timestamps corresponding to the time, storescp writes a file to disk. The format is
[YYYYMMDDHHMMSSPPP]_[SERIALNO].[MD]
where YYYY, MM, DD, HH, MM, SS, PPP are interpreted as described above. If more files are created at the same time, SERIALNO is inserted. It consists of a 4-digit, consecutive number (0000 to 9999). For the first file, that exists for a specific time, no number (and no "_") is inserted at all. MD represents an identification code (2 letters) for the kind of object stored in the file (see notes on &rename-on-eostudy).
Option &filename-extension appends a specified suffix to each filename (a dot "." is not added automatically). This suffix is not appended to the filenames created by &rename-on-eostudy to maintain the length of 8 characters.
Option &exec-on-reception allows one to execute a certain command line after having received and processed one DICOM object (through a C-STORE-RQ message). The command line to be executed is passed to this option as a parameter. The specified command line may contain a number of placeholders which will be replaced at run time:
#p: complete path to the output directory into which the last DICOM object was stored (not available with option &ignore though)
#f: filename of the current output file (not available with option &ignore though)
#a: calling application entity title of the peer Storage SCU
#c: called application entity title used by the peer Storage SCU to address storescp
#r: calling presentation address, i.e. hostname or IP address of the peer Storage SCU
The specified command line is executed as a separate process, so that the execution of storescp will not be held back. This behavior can be influenced with the &exec-sync option.
Option &exec-on-eostudy allows one to execute a certain command line when all DICOM objects that belong to one study have been received by storescp. The same placeholders as with &exec-on-reception may be used, except for '#f', which is not supported. A study is considered complete by storescp when an object belonging to a different study is received or the timeout specified with &eostudy-timeout takes place. If option &rename-on-eostudy is in force, the renaming takes place before the external command is executed.
Option &rename-on-eostudy refers to the above mentioned &sort-xxx options and can only be used in combination with one of these options. If a user specifies option &rename-on-eostudy and storescp determines that all DICOM objects that belong to a certain study have been received, all DICOM files that belong to the last study will be renamed in the corresponding output directory. The filenames into which the files are being renamed will be calculated using the pattern
[prefix][consecutive numbering]
where [prefix] is a 2 character prefix that reveals the kind of DICOM object stored in the file and [consecutive numbering] is a consecutively numbered, 6-digit number, starting at "000001". In general, the question if all DICOM objects that belong to one study have been received by storescp will be answered positively if and only if two consecutively received DICOM objects d_n and d_n+1 do not show the same values in attribute Study Instance UID; in such a case, d_n+1 is considered to belong to a new study.
Using option &eostudy-timeout a user can modify the determination process to figure out if all DICOM objects that belong to one study have already been received by storescp. With regard to this fact, it is clear that this option can only be used in combination with at least one of the following options: &sort-xxx, &exec-on-eostudy and &rename-on-eostudy. If option &eostudy-timeout is specified, the end of a study is considered to have occurred not only if two consecutively received DICOM objects d_n and d_n+1 do not show the same values in attribute Study Instance UID, but also if within a time span of x seconds after the reception of a DICOM object d_n, no other DICOM object was received over the network. Note that the amount x of seconds (which determines the length of this time span) has to be passed to this option as a parameter.
Please note that two consecutive network connections can transfer objects for the same study. The study will only be considered complete when an object of a different study is received or the &eostudy-timeout is reached. For this reason, the options &fork and &inet are incompatible with &exec-on-eostudy, &rename-on-eostudy and &sort-conc-studies.
DICOM Conformance
The storescp application supports the following SOP Classes as an SCP:
VerificationSOPClass
RETIRED_StoredPrintStorage
1.2.840..1.27
RETIRED_HardcopyGrayscaleImageStorage
1.2.840..1.29
RETIRED_HardcopyColorImageStorage
1.2.840..1.30
ComputedRadiographyImageStorage
1.2.840..4.1.1.1
DigitalXRayImageStorageForPresentation
1.2.840..4.1.1.1.1
DigitalXRayImageStorageForProcessing
1.2.840..4.1.1.1.1.1
DigitalMammographyXRayImageStorageForPresentation
1.2.840..4.1.1.1.2
DigitalMammographyXRayImageStorageForProcessing
1.2.840..4.1.1.1.2.1
DigitalIntraOralXRayImageStorageForPresentation
1.2.840..4.1.1.1.3
DigitalIntraOralXRayImageStorageForProcessing
1.2.840..4.1.1.1.3.1
CTImageStorage
1.2.840..4.1.1.2
EnhancedCTImageStorage
1.2.840..4.1.1.2.1
LegacyConvertedEnhancedCTImageStorage
1.2.840..4.1.1.2.2
RETIRED_UltrasoundMultiframeImageStorage
1.2.840..4.1.1.3
UltrasoundMultiframeImageStorage
1.2.840..4.1.1.3.1
MRImageStorage
1.2.840..4.1.1.4
EnhancedMRImageStorage
1.2.840..4.1.1.4.1
MRSpectroscopyStorage
1.2.840..4.1.1.4.2
EnhancedMRColorImageStorage
1.2.840..4.1.1.4.3
LegacyConvertedEnhancedMRImageStorage
1.2.840..4.1.1.4.4
RETIRED_NuclearMedicineImageStorage
1.2.840..4.1.1.5
RETIRED_UltrasoundImageStorage
1.2.840..4.1.1.6
UltrasoundImageStorage
1.2.840..4.1.1.6.1
EnhancedUSVolumeStorage
1.2.840..4.1.1.6.2
SecondaryCaptureImageStorage
1.2.840..4.1.1.7
MultiframeSingleBitSecondaryCaptureImageStorage
1.2.840..4.1.1.7.1
MultiframeGrayscaleByteSecondaryCaptureImageStorage
1.2.840..4.1.1.7.2
MultiframeGrayscaleWordSecondaryCaptureImageStorage
1.2.840..4.1.1.7.3
MultiframeTrueColorSecondaryCaptureImageStorage
1.2.840..4.1.1.7.4
RETIRED_StandaloneOverlayStorage
1.2.840..4.1.1.8
RETIRED_StandaloneCurveStorage
1.2.840..4.1.1.9
DRAFT_WaveformStorage
1.2.840..4.1.1.9.1
TwelveLeadECGWaveformStorage
1.2.840..4.1.1.9.1.1
GeneralECGWaveformStorage
1.2.840..4.1.1.9.1.2
AmbulatoryECGWaveformStorage
1.2.840..4.1.1.9.1.3
HemodynamicWaveformStorage
1.2.840..4.1.1.9.2.1
CardiacElectrophysiologyWaveformStorage
1.2.840..4.1.1.9.3.1
BasicVoiceAudioWaveformStorage
1.2.840..4.1.1.9.4.1
GeneralAudioWaveformStorage
1.2.840..4.1.1.9.4.2
ArterialPulseWaveformStorage
1.2.840..4.1.1.9.5.1
RespiratoryWaveformStorage
1.2.840..4.1.1.9.6.1
RETIRED_StandaloneModalityLUTStorage
1.2.840..4.1.1.10
RETIRED_StandaloneVOILUTStorage
1.2.840..4.1.1.11
GrayscaleSoftcopyPresentationStateStorage
1.2.840..4.1.1.11.1
ColorSoftcopyPresentationStateStorage
1.2.840..4.1.1.11.2
PseudoColorSoftcopyPresentationStateStorage
1.2.840..4.1.1.11.3
BlendingSoftcopyPresentationStateStorage
1.2.840..4.1.1.11.4
XAXRFGrayscaleSoftcopyPresentationStateStorage
1.2.840..4.1.1.11.5
GrayscalePlanarMPRVolumetricPresentationStateStorage 1.2.840..4.1.1.11.6
CompositingPlanarMPRVolumetricPresent.StateStorage
1.2.840..4.1.1.11.7
AdvancedBlendingPresentationStateStorage
1.2.840..4.1.1.11.8
VolumeRenderingVolumetricPresentationStateStorage
1.2.840..4.1.1.11.9
SegmentedVolumeRenderingVolumetricPres.StateStorage
1.2.840..4.1.1.11.10
MultipleVolumeRenderingVolumetricPres.StateStorage
1.2.840..4.1.1.11.11
XRayAngiographicImageStorage
1.2.840..4.1.1.12.1
EnhancedXAImageStorage
1.2.840..4.1.1.12.1.1
XRayRadiofluoroscopicImageStorage
1.2.840..4.1.1.12.2
EnhancedXRFImageStorage
1.2.840..4.1.1.12.2.1
RETIRED_XRayAngiographicBiPlaneImageStorage
1.2.840..4.1.1.12.3
XRay3DAngiographicImageStorage
1.2.840..4.1.1.13.1.1
XRay3DCraniofacialImageStorage
1.2.840..4.1.1.13.1.2
BreastTomosynthesisImageStorage
1.2.840..4.1.1.13.1.3
BreastProjectionXRayImageStorageForPresentation
1.2.840..4.1.1.13.1.4
BreastProjectionXRayImageStorageForProcessing
1.2.840..4.1.1.13.1.5
IntravascularOpt.Coh.Tom.ImageStorageForPresentation 1.2.840..4.1.1.14.1
IntravascularOpt.Coh.Tom.ImageStorageForProcessing
1.2.840..4.1.1.14.2
NuclearMedicineImageStorage
1.2.840..4.1.1.20
ParametricMapStorage
1.2.840..4.1.1.30
RawDataStorage
1.2.840..4.1.1.66
SpatialRegistrationStorage
1.2.840..4.1.1.66.1
SpatialFiducialsStorage
1.2.840..4.1.1.66.2
DeformableSpatialRegistrationStorage
1.2.840..4.1.1.66.3
SegmentationStorage
1.2.840..4.1.1.66.4
SurfaceSegmentationStorage
1.2.840..4.1.1.66.5
TractographyResultsStorage
1.2.840..4.1.1.66.6
RealWorldValueMappingStorage
1.2.840..4.1.1.67
SurfaceScanMeshStorage
1.2.840..4.1.1.68.1
SurfaceScanPointCloudStorage
1.2.840..4.1.1.68.2
RETIRED_VLImageStorage
1.2.840..4.1.1.77.1
VLEndoscopicImageStorage
1.2.840..4.1.1.77.1.1
VideoEndoscopicImageStorage
1.2.840..4.1.1.77.1.1.1
VLMicroscopicImageStorage
1.2.840..4.1.1.77.1.2
VideoMicroscopicImageStorage
1.2.840..4.1.1.77.1.2.1
VLSlideCoordinatesMicroscopicImageStorage
1.2.840..4.1.1.77.1.3
VLPhotographicImageStorage
1.2.840..4.1.1.77.1.4
VideoPhotographicImageStorage
1.2.840..4.1.1.77.1.4.1
OphthalmicPhotography8BitImageStorage
1.2.840..4.1.1.77.1.5.1
OphthalmicPhotography16BitImageStorage
1.2.840..4.1.1.77.1.5.2
StereometricRelationshipStorage
1.2.840..4.1.1.77.1.5.3
OphthalmicTomographyImageStorage
1.2.840..4.1.1.77.1.5.4
WideFieldOphthalmicPhoto.Stereogr.Proj.ImageStorage
1.2.840..4.1.1.77.1.5.5
WideFieldOphthalmicPhotogr.3DCoordinatesImageStorage 1.2.840..4.1.1.77.1.5.6
OphthalmicOpticalCoherenceTomogr.EnFaceImageStorage
1.2.840..4.1.1.77.1.5.7
OphthalmicOpticalCoh.Tomogr.BscanVolumeAnalysisStor. 1.2.840..4.1.1.77.1.5.8
VLWholeSlideMicroscopyImageStorage
1.2.840..4.1.1.77.1.6
RETIRED_VLMultiFrameImageStorage
1.2.840..4.1.1.77.2
LensometryMeasurementsStorage
1.2.840..4.1.1.78.1
AutorefractionMeasurementsStorage
1.2.840..4.1.1.78.2
KeratometryMeasurementsStorage
1.2.840..4.1.1.78.3
SubjectiveRefractionMeasurementsStorage
1.2.840..4.1.1.78.4
VisualAcuityMeasurementsStorage
1.2.840..4.1.1.78.5
SpectaclePrescriptionReportStorage
1.2.840..4.1.1.78.6
OphthalmicAxialMeasurementsStorage
1.2.840..4.1.1.78.7
IntraocularLensCalculationsStorage
1.2.840..4.1.1.78.8
MacularGridThicknessAndVolumeReportStorage
1.2.840..4.1.1.79.1
OphthalmicVisualFieldStaticPerimetryMeasurementsSt.
1.2.840..4.1.1.80.1
OphthalmicThicknessMapStorage
1.2.840..4.1.1.81.1
CornealTopographyMapStorage
1.2.840..4.1.1.82.1
DRAFT_SRTextStorage
1.2.840..4.1.1.88.1
DRAFT_SRAudioStorage
1.2.840..4.1.1.88.2
DRAFT_SRDetailStorage
1.2.840..4.1.1.88.3
DRAFT_SRComprehensiveStorage
1.2.840..4.1.1.88.4
BasicTextSRStorage
1.2.840..4.1.1.88.11
EnhancedSRStorage
1.2.840..4.1.1.88.22
ComprehensiveSRStorage
1.2.840..4.1.1.88.33
Comprehensive3DSRStorage
1.2.840..4.1.1.88.34
ExtensibleSRStorage
1.2.840..4.1.1.88.35
ProcedureLogStorage
1.2.840..4.1.1.88.40
MammographyCADSRStorage
1.2.840..4.1.1.88.50
KeyObjectSelectionDocumentStorage
1.2.840..4.1.1.88.59
ChestCADSRStorage
1.2.840..4.1.1.88.65
XRayRadiationDoseSRStorage
1.2.840..4.1.1.88.67
RadiopharmaceuticalRadiationDoseSRStorage
1.2.840..4.1.1.88.68
ColonCADSRStorage
1.2.840..4.1.1.88.69
ImplantationPlanSRDocumentStorage
1.2.840..4.1.1.88.70
AcquisitionContextSRStorage
1.2.840..4.1.1.88.71
SimplifiedAdultEchoSRStorage
1.2.840..4.1.1.88.72
PatientRadiationDoseSRStorage
1.2.840..4.1.1.88.73
ContentAssessmentResultsStorage
1.2.840..4.1.1.90.1
EncapsulatedPDFStorage
1.2.840..4.1.1.104.1
EncapsulatedCDAStorage
1.2.840..4.1.1.104.2
PositronEmissionTomographyImageStorage
1.2.840..4.1.1.128
LegacyConvertedEnhancedPETImageStorage
1.2.840..4.1.1.128.1
RETIRED_StandalonePETCurveStorage
1.2.840..4.1.1.129
EnhancedPETImageStorage
1.2.840..4.1.1.130
BasicStructuredDisplayStorage
1.2.840..4.1.1.131
CTPerformedProcedureProtocolStorage
1.2.840..4.1.1.200.2
RTImageStorage
1.2.840..4.1.1.481.1
RTDoseStorage
1.2.840..4.1.1.481.2
RTStructureSetStorage
1.2.840..4.1.1.481.3
RTBeamsTreatmentRecordStorage
1.2.840..4.1.1.481.4
RTPlanStorage
1.2.840..4.1.1.481.5
RTBrachyTreatmentRecordStorage
1.2.840..4.1.1.481.6
RTTreatmentSummaryRecordStorage
1.2.840..4.1.1.481.7
RTIonPlanStorage
1.2.840..4.1.1.481.8
RTIonBeamsTreatmentRecordStorage
1.2.840..4.1.1.481.9
DICOS_CTImageStorage
1.2.840..4.1.1.501.1
DICOS_DigitalXRayImageStorageForPresentation
1.2.840..4.1.1.501.2.1
DICOS_DigitalXRayImageStorageForProcessing
1.2.840..4.1.1.501.2.2
DICOS_ThreatDetectionReportStorage
1.2.840..4.1.1.501.3
DICOS_2DAITStorage
1.2.840..4.1.1.501.4
DICOS_3DAITStorage
1.2.840..4.1.1.501.5
DICOS_QuadrupoleResonanceStorage
1.2.840..4.1.1.501.6
DICONDE_EddyCurrentImageStorage
1.2.840..4.1.1.601.1
DICONDE_EddyCurrentMultiframeImageStorage
1.2.840..4.1.1.601.2
DRAFT_RTBeamsDeliveryInstructionStorage
1.2.840..4.34.1
RTBeamsDeliveryInstructionStorage
1.2.840..4.34.7
RTBrachyApplicationSetupDeliveryInstructionStorage
1.2.840..4.34.10
The storescp application will accept presentation contexts for all of the abovementioned supported SOP Classes using any of the following transfer syntaxes:
LittleEndianImplicitTransferSyntax
LittleEndianExplicitTransferSyntax
1.2.840..1
BigEndianExplicitTransferSyntax
1.2.840..2
The default behavior of the storescp application is to prefer transfer syntaxes having an explicit encoding over the default implicit transfer syntax. If storescp is running on big-endian hardware it will prefer BigEndianExplicit to LittleEndianExplicit transfer syntax (and vice versa). This behavior can be changed with the &prefer options (see above). Using option &accept-all any of the following transfer syntaxes is supported:
LittleEndianImplicitTransferSyntax
LittleEndianExplicitTransferSyntax
1.2.840..1
DeflatedExplicitVRLittleEndianTransferSyntax
1.2.840..1.99
BigEndianExplicitTransferSyntax
1.2.840..2
JPEGProcess1TransferSyntax
1.2.840..4.50
JPEGProcess2_4TransferSyntax
1.2.840..4.51
JPEGProcess14SV1TransferSyntax
1.2.840..4.70
JPEGLSLosslessTransferSyntax
1.2.840..4.80
JPEGLSLossyTransferSyntax
1.2.840..4.81
JPEG2000LosslessOnlyTransferSyntax
1.2.840..4.90
JPEG2000TransferSyntax
1.2.840..4.91
MPEG2MainProfileAtMainLevelTransferSyntax
1.2.840..4.100
MPEG2MainProfileAtHighLevelTransferSyntax
1.2.840..4.101
MPEG4HighProfileLevel4_1TransferSyntax
1.2.840..4.102
MPEG4BDcompatibleHighProfileLevel4_1TransferSyntax
1.2.840..4.103
MPEG4HighProfileLevel4_2_For2DVideoTransferSyntax
1.2.840..4.104
MPEG4HighProfileLevel4_2_For3DVideoTransferSyntax
1.2.840..4.105
MPEG4StereoHighProfileLevel4_2TransferSyntax
1.2.840..4.106
HEVCMainProfileLevel5_1TransferSyntax
1.2.840..4.107
HEVCMain10ProfileLevel5_1TransferSyntax
1.2.840..4.108
RLELosslessTransferSyntax
1.2.840..5
Additional Storage SOP Classes and Transfer Syntaxes can be used with the so-called "association negotiation profiles" (see below).
The storescp application does not support extended negotiation by default. However, using an appropriate association negotiation profile (see below) the optional support for extended negotiation can be added to particular SOP classes.
Access Control
When compiled on Unix platforms with TCP wrapper support, host-based access control can be enabled with the &access-control command line option. In this case the access control rules defined in the system's host access control tables for storescp are enforced. The default locations of the host access control tables are /etc/hosts.allow and /etc/hosts.deny. Further details are described in hosts_access(5).
Running storescp from inetd
On Posix platforms, storescp can be initiated through the inetd(8) super server. This requires that storescp be configured in the /etc/inetd.conf configuration file. A typical configuration line could look like this:
acr-nema stream tcp nowait root /usr/sbin/storescp -id +ac -od /tmp/storescp
where -id (&inetd) activates the inetd mode in which the DICOM association is actually accepted by inetd and passed to storescp, +ac (&access-control) activates the TCP wrapper based access control described above and -od (&output-directory) defines the directory in which storescp stores incoming DICOM objects. Note that the service name ("acr-nema" in this example) determines the port number on which DICOM associations are accepted and must be defined in /etc/services. When running from inetd, the stdout and stderr streams are discarded. However, you can still configure logging via the &log-config option (see below).
Please note that when run through inetd, storescp is executed with root privileges, which may be a security risk.
Association Negotiation Profiles and Configuration Files
storescp supports a flexible mechanism for specifying the DICOM network association negotiation behavior, based on so-called "association negotiation
profiles" which may be read from a configuration file. The format and semantics of this configuration file are documented in asconfig.txt.
The level of logging output of the various command line tools and underlying libraries can be specified by the user. By default, only errors and warnings are written to the standard error stream. Using option &verbose also informational messages like processing details are reported. Option &debug can be used to get more details on the internal activity, e.g. for debugging purposes. Other logging levels can be selected using option &log-level. In &quiet mode only fatal errors are reported. In such very severe error events, the application will usually terminate. For more details on the different logging levels, see documentation of module "oflog".
In case the logging output should be written to file (optionally with logfile rotation), to syslog (Unix) or the event log (Windows) option &log-config can be used. This configuration file also allows for directing only certain messages to a particular output stream and for filtering certain messages based on the module or application where they are generated. An example configuration file is provided in &etcdir&/logger.cfg.
COMMAND LINE
All command line tools use the following notation for parameters: square brackets enclose optional values (0-1), three trailing dots indicate that multiple values are allowed (1-n), a combination of both means 0 to n values.
Command line options are distinguished from parameters by a leading '+' or '-' sign, respectively. Usually, order and position of command line options are arbitrary (i.e. they can appear anywhere). However, if options are mutually exclusive the rightmost appearance is used. This behavior conforms to the standard evaluation rules of common Unix shells.
In addition, one or more command files can be specified using an '@' sign as a prefix to the filename (e.g. @command.txt). Such a command argument is replaced by the content of the corresponding text file (multiple whitespaces are treated as a single separator unless they appear between two quotation marks) prior to any further evaluation. Please note that a command file cannot contain another command file. This simple but effective approach allows one to summarize common combinations of options/parameters and avoids longish and confusing command lines (an example is provided in file &datadir&/dumppat.txt).
ENVIRONMENT
The storescp utility will attempt to load DICOM data dictionaries specified in the DCMDICTPATH environment variable. By default, i.e. if the DCMDICTPATH environment variable is not set, the file &datadir&/dicom.dic will be loaded unless the dictionary is built into the application (default for Windows).
The default behavior should be preferred and the DCMDICTPATH environment variable only used when alternative data dictionaries are required. The DCMDICTPATH environment variable has the same format as the Unix shell PATH variable in that a colon (":") separates entries. On Windows systems, a semicolon (";") is used as a separator. The data dictionary code will attempt to load each file specified in the DCMDICTPATH environment variable. It is an error if no data dictionary can be loaded.
&docdir&/asconfig.txt - configuration file documentation
&etcdir&/storescp.cfg - example association negotiation profile
storescu(1)
Copyright (C)
by OFFIS e.V., Escherweg 2, 26121 Oldenburg, Germany.
Generated on Mon Jul 17 2017 for
Version 3.6.2 by