Scp Chilkat2 PHP Reference Documentation

Scp

Current Version: 11.7.0

Markdown version of this page for AI tools (v 11.7.0) · all AI docs

Chilkat.Scp

Transfer files, text, and binary data over SCP using an existing SSH connection.

Chilkat.Scp is the Chilkat class for SCP file transfer over an already-established Chilkat.Ssh connection. It supports local-file upload and download, in-memory binary transfer, encoded binary transfer, text transfer with explicit character sets, BinData transfer, directory-tree synchronization, sync filtering, remote UNIX permission overrides, environment variables, progress scaling, abort support, and asynchronous task integration.

Uses an SSH connection

Attach Scp to an authenticated Chilkat.Ssh session rather than opening a separate network connection.

Upload and download files

Transfer local files to remote paths or download remote files to the local filesystem using SCP.

Memory-based transfers

Upload or download binary data, encoded data, text, or Chilkat.BinData without requiring temporary files.

Directory synchronization

Synchronize directory trees and use filtering options to include or exclude selected files.

Remote file options

Set remote UNIX permissions, pass environment variables, and control transfer-related behavior required by the remote server.

Progress and async support

Monitor progress, scale progress percentages, abort active transfers, and run supported operations as asynchronous tasks.

Common pattern: Connect and authenticate with Chilkat.Ssh, initialize Chilkat.Scp with that SSH connection, then upload, download, or synchronize the desired files or in-memory data. Use Scp for SCP-style transfers over SSH; use Chilkat.SFtp when the remote server expects the SFTP protocol instead.

Object Creation

use Chilkat2\Scp;

try {
    $scp = new Scp();
    // ... use $scp ...
} catch (\Chilkat2\Exception $e) {
    echo $e->getClass(), '::', $e->getMethod(), " failed\n";
    echo $e->getMessage(), "\n";              // the LastErrorText of the failed call
}
public function __construct(array $properties = [])

Creates the object. The optional array sets properties in order, as if assigned one by one (new Scp(['VerboseLogging' => true, 'RaiseError' => false])); an unknown or read-only name throws Error. The class is defined by the chilkat2 extension (extension=chilkat2 in php.ini): there is no PHP file to include.

There is no close(): PHP frees the object when its last reference goes (unset($scp), $scp = null, or the end of the function or request). Objects returned by methods are independent and freed the same way. The class may be extended (class MyScp extends \Chilkat2\Scp); objects cannot be cloned or serialized.

public bool $RaiseError;

When true (the default), a method that fails throws Chilkat2\Exception. When false, it returns false (or null) instead, and the reason is in LastErrorText. Objects returned by a method inherit the value of the object that returned them.

Errors

Chilkat2\Exception extends RuntimeException: getMessage() is the failed call's full LastErrorText, getClass() its class ('Chilkat2\Scp') and getMethod() the method name. The object remains usable. Methods that look something up and find nothing return null without throwing (each such method says so), methods that answer a question (HasMember, IsUnlocked, ...) return a plain bool, and property reads and writes do not throw for Chilkat reasons.

Misuse always throws, whatever RaiseError is: a wrong argument type is a TypeError (exact types under declare(strict_types=1)), a missing or extra argument an ArgumentCountError, a string containing a NUL byte or an out-of-range integer a ValueError, and an unknown property (properties are case-sensitive) or a write to a read-only one an Error. Named arguments work with the parameter names shown.

Strings are passed and returned as UTF-8; binary data is a PHP string of bytes. Unlocking: call (new \Chilkat2\GlobalSettings())->UnlockBundle('...') once at startup.

Properties

AbortCurrent
public bool $AbortCurrent;
Introduced in version 9.5.0.58

Set to true to request cancellation of the method currently executing on this object. Long-running network and file-transfer operations check this property periodically; a method that completes quickly may finish before the request is observed.

Both synchronous and asynchronous operations can be cancelled. To cancel a synchronous call, set this property from another thread on the same Scp object. Chilkat resets the property to false after the cancellation is processed. If no method is running, a previously set value is cleared when the next method begins.

Cooperative cancellation: This property requests an abort; it does not forcibly terminate a thread. Use the method return value, LastMethodSuccess where applicable, and LastErrorText to determine the final outcome.

top
DebugLogFilePath
public string $DebugLogFilePath;

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

  • A timeout property set to 0, indicating an infinite timeout.
  • A hang occurring within an event callback in the application code.
  • An internal bug in the Chilkat code causing the hang.

More Information and Examples
top
HeartbeatMs
public int $HeartbeatMs;

Specifies the interval, in milliseconds, between AbortCheck event callbacks during supported long-running operations. The callback allows the application to report activity or request cancellation before the operation completes.

The default value is 0, which disables periodic AbortCheck callbacks.

Event-callback setting: This property is useful only in programming environments that support Chilkat event callbacks. It is not an SSH keep-alive interval and does not change connection or read timeouts.

More Information and Examples
top
LastErrorHtml
public readonly string $LastErrorHtml;

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorText
public readonly string $LastErrorText;

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorXml
public readonly string $LastErrorXml;

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastMethodSuccess
public bool $LastMethodSuccess;

Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.

top
PercentDoneScale
public int $PercentDoneScale;
Introduced in version 9.5.0.51

Specifies the value that represents 100% completion in PercentDone event callbacks. The default is 100, which reports progress in whole-percent units. For example, when the scale is 1000, a callback value of 453 represents 45.3% completion.

The value is limited to the range 10 through 100000. Increasing the scale provides finer numeric granularity for operations whose progress can be measured.

Event-callback setting: This property applies only in programming environments that support Chilkat event callbacks. A larger scale changes the meaning and possible granularity of callback values; it does not guarantee that every intermediate value will be reported.

top
SendEnv
public string $SendEnv;
Introduced in version 9.5.0.79

Specifies environment variables to send for each SCP upload or download. Set the property to a JSON object whose member names are environment-variable names and whose values are strings.

{
  "LCS_PASSWORD": "myPassword",
  "SOME_ENV_VAR": "some_value"
}
Server policy controls acceptance: SCP transfers run through SSH channels. The SSH server may accept, reject, or ignore requested environment variables according to its configuration. Do not assume that setting this property guarantees that the remote SCP process receives every variable.
Sensitive values: Environment variables can contain secrets, but they are not a substitute for SSH authentication. Avoid exposing sensitive values in application logs or diagnostic output.

top
SyncedFiles
public string $SyncedFiles;
Introduced in version 9.5.0.51

Contains the local paths of the files transferred by the most recent call to SyncTreeUpload or SyncTreeDownload. Paths are listed one per line.

  • After an upload, each line is the full local path of a source file that was uploaded.
  • After a download, each line is the full local path of a destination file that was downloaded.
Local paths only: This property reports local filesystem paths, not remote paths. It lists files actually transferred by the last synchronization operation, rather than every file examined during comparison.

More Information and Examples
top
SyncMustMatch
public string $SyncMustMatch;
Introduced in version 9.5.0.51

Specifies a semicolon-separated list of wildcard patterns for filenames that are eligible for transfer by SyncTreeUpload and SyncTreeDownload. A file is considered only when its filename matches at least one pattern.

For example, *.xml;*.txt;*.csv limits synchronization to XML, text, and CSV files. The default empty string imposes no include restriction.

Pattern scope: Patterns are matched against the final filename, not the full local or remote path. Directory traversal is controlled separately by SyncMustMatchDir and SyncMustNotMatchDir.

top
SyncMustMatchDir
public string $SyncMustMatchDir;
Introduced in version 9.5.0.58

Specifies a semicolon-separated list of wildcard patterns for directory names that may be traversed by SyncTreeUpload and SyncTreeDownload. When this property is nonempty, synchronization descends only into directories whose names match at least one pattern.

For example, a*;b*;c* permits traversal into directories whose names begin with a, b, or c. The default empty string permits traversal into all directories, subject to SyncMustNotMatchDir.

Pattern scope: Each pattern is matched against the directory name itself, not its complete path. This property affects traversal; it does not directly select individual files.

top
SyncMustNotMatch
public string $SyncMustNotMatch;
Introduced in version 9.5.0.51

Specifies a semicolon-separated list of wildcard patterns for filenames that must be skipped by SyncTreeUpload and SyncTreeDownload.

For example, *.tmp;*.bak;*.log excludes temporary, backup, and log files. The default empty string excludes no files.

Pattern scope: Patterns are matched against the final filename, not the full path. Use SyncMustNotMatchDir to prevent synchronization from entering selected directories and their subtrees.

More Information and Examples
top
SyncMustNotMatchDir
public string $SyncMustNotMatchDir;
Introduced in version 9.5.0.58

Specifies a semicolon-separated list of wildcard patterns for directory names that must not be traversed by SyncTreeUpload and SyncTreeDownload. A matching directory and everything below it are skipped.

For example, temp*;cache*;.git prevents traversal into temporary, cache, and Git metadata directories. The default empty string excludes no directories.

Pattern scope: Each pattern is matched against the directory name itself, not its complete path. This setting is especially useful during recursive synchronization because excluding a directory avoids scanning its entire subtree.

top
UncommonOptions
public string $UncommonOptions;
Introduced in version 9.5.0.77

Provides a comma-separated list of specialized compatibility options. The default is the empty string, which is appropriate for normal SCP transfers.

KeywordBehavior
FilenameOnlyUses only the filename, rather than the complete target path, in the remote scp -t command. This option exists for compatibility with systems such as certain LANCOM routers.
ProtectFromVpnOn Android, attempts to route the SCP connection outside an installed or active VPN.
Leave empty unless needed: These options alter uncommon platform or server compatibility behavior. Enable a keyword only when a Chilkat example, release note, or support response identifies it as necessary for the target environment.

top
UnixPermOverride
public string $UnixPermOverride;
Introduced in version 9.5.0.77

Specifies an octal UNIX permission mode to apply to files uploaded by SCP, overriding the permissions derived from the local source file. For example, set this property to 0644 to grant read/write permission to the owner and read-only permission to the group and others.

The default is the empty string, which causes the uploaded file's remote permissions to be based on the local file's permissions.

UNIX permission notation: Supply the mode as a string containing octal digits, such as 0600, 0644, or 0755. The remote SSH account must still have permission to create or replace the file, and server-side policy may restrict the final mode.

top
VerboseLogging
public bool $VerboseLogging;

If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
public readonly string $Version;

Version of the component/library, such as "10.1.0"

More Information and Examples
top

Methods

DownloadBd
public function DownloadBd(string $remotePath, BinData $bd): bool
Introduced in version 9.5.0.77

Downloads the file at $remotePath and appends its exact bytes to the existing contents of the BinData object in $bd.

An absolute remote path begins with /. A relative path is interpreted relative to the authenticated SSH user's home directory.

Append behavior: This method does not clear $bd before downloading. Clear the BinData object first when the downloaded file should replace, rather than follow, its current contents.

Returns true on success. On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns false). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

top
DownloadBinaryEncoded
public function DownloadBinaryEncoded(string $remotePath, string $encoding): ?string
Introduced in version 9.5.0.51

Downloads the file at $remotePath and returns its bytes encoded as text using the binary encoding named by $encoding, such as base64 or hex.

An absolute remote path begins with /. A relative path is interpreted relative to the authenticated SSH user's home directory.

Binary encoding versus charset: $encoding selects a text representation of arbitrary bytes; it is not a character set and does not decode the remote file as text. Use DownloadString when the remote file contains text that must be decoded with a charset.
Memory use: The complete file and its encoded representation are held in memory. Encodings such as Base64 also increase the amount of data returned.

On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns null). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

top
DownloadFile
public function DownloadFile(string $remotePath, string $localPath): bool
Introduced in version 9.5.0.51

Downloads the file at $remotePath from the SSH server and writes its bytes to the local filesystem path in $localPath.

An absolute remote path begins with /. A relative remote path is interpreted relative to the authenticated SSH user's home directory. The application must have permission to create or replace the local destination file.

Streaming transfer: This method is the preferred download method for large files because the data is written to disk rather than returned as one in-memory byte array or string.

Returns true on success. On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns false). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

top
DownloadString
public function DownloadString(string $remotePath, string $charset): ?string
Introduced in version 9.5.0.51

Downloads the file at $remotePath, decodes its bytes using the character encoding named by $charset, and returns the resulting text.

An absolute remote path begins with /. A relative path is interpreted relative to the authenticated SSH user's home directory.

Charset matters: $charset describes how the remote file’s bytes represent characters, for example utf-8, windows-1252, or iso-8859-1. Using the wrong charset can produce incorrect characters. Use a binary download method for files that are not text.

On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns null). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

More Information and Examples
top
SyncTreeDownload
public function SyncTreeDownload(string $remoteRoot, string $localRoot, int $mode, bool $bRecurse): bool
Introduced in version 9.5.0.51

Synchronizes files from the remote directory tree rooted at $remoteRoot to the local directory rooted at $localRoot. $bRecurse controls recursion: set it to true to descend into subdirectories, or false to process only files directly in the root directory.

An absolute remote root begins with /; a relative remote root is interpreted relative to the authenticated SSH user's home directory. A relative local root is interpreted relative to the application's current working directory.

ModeFiles transferred
0Download every eligible file.
1Download files that do not already exist locally.
2Download files that are missing locally or whose remote last-modified time is newer than the local file.
3Download only files whose remote last-modified time is newer. A remote file that has no local counterpart is not downloaded.
5Download files that are missing locally or whose size differs from the local file.
6Download files that are missing locally, differ in size, or have a newer remote last-modified time.

The filename and directory filters in SyncMustMatch, SyncMustNotMatch, SyncMustMatchDir, and SyncMustNotMatchDir are applied during traversal. After completion, SyncedFiles lists the full local paths of files actually downloaded.

Timestamp-based modes: Modes 2, 3, and 6 compare last-modified times. Incorrect server timestamps or clock differences between systems can affect which file is considered newer.

Returns true on success. On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns false). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

More Information and Examples
top
SyncTreeUpload
public function SyncTreeUpload(string $localBaseDir, string $remoteBaseDir, int $mode, bool $bRecurse): bool
Introduced in version 9.5.0.51

Synchronizes files from the local directory tree rooted at $localBaseDir to the remote directory rooted at $remoteBaseDir. $bRecurse controls recursion: set it to true to descend into subdirectories, or false to process only files directly in the local base directory.

A relative local base directory is interpreted relative to the application's current working directory. An absolute remote base directory begins with /; a relative remote base directory is interpreted relative to the authenticated SSH user's home directory.

ModeFiles transferred
0Upload every eligible file.
1Upload files that do not already exist on the remote server.
2Upload files that are missing remotely or whose local last-modified time is newer than the remote file.
3Upload only files whose local last-modified time is newer. A local file that has no remote counterpart is not uploaded.
4Upload files that are missing remotely or whose size differs from the remote file.
5Upload files that are missing remotely, differ in size, or have a newer local last-modified time.

The filename and directory filters in SyncMustMatch, SyncMustNotMatch, SyncMustMatchDir, and SyncMustNotMatchDir are applied during traversal. After completion, SyncedFiles lists the full local paths of files actually uploaded.

Timestamp-based modes: Modes 2, 3, and 5 compare last-modified times. Incorrect server timestamps or clock differences between systems can affect which file is considered newer.

Returns true on success. On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns false). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

top
UploadBd
public function UploadBd(string $remotePath, BinData $bd): bool
Introduced in version 9.5.0.77

Uploads all bytes currently contained in the BinData object in $bd to the remote file at $remotePath. The data is transferred without character decoding or other transformation.

An absolute remote path begins with /. A relative path is interpreted relative to the authenticated SSH user's home directory. The remote parent directory must already exist.

Source object: The upload reads the current contents of $bd and does not remove or modify those bytes.

Returns true on success. On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns false). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

top
UploadBinaryEncoded
public function UploadBinaryEncoded(string $remotePath, string $encodedData, string $encoding): bool
Introduced in version 9.5.0.51

Decodes the text in $encodedData using the binary encoding named by $encoding, then uploads the resulting bytes to the remote file at $remotePath. Typical encoding names include base64 and hex.

An absolute remote path begins with /. A relative path is interpreted relative to the authenticated SSH user's home directory. The remote parent directory must already exist.

The encoded text is not uploaded literally: For example, when $encoding is base64, Chilkat Base64-decodes $encodedData and transfers the decoded binary bytes. This method is for encoded binary representations, not character-set conversion.

Returns true on success. On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns false). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

top
UploadFile
public function UploadFile(string $localPath, string $remotePath): bool
Introduced in version 9.5.0.51

Uploads the local filesystem file at $localPath to the remote path in $remotePath. The file is transferred as raw bytes.

An absolute remote path begins with /. A relative remote path is interpreted relative to the authenticated SSH user's home directory. The remote parent directory must already exist, and the SSH account must have permission to create or replace the destination file.

Remote permissions are normally derived from the local file. Set UnixPermOverride when a specific remote UNIX mode is required.

SCP is not FTP: There is no ASCII or binary transfer mode. UploadFile copies the file bytes without line-ending or character-set conversion.

Returns true on success. On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns false). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

top
UploadString
public function UploadString(string $remotePath, string $textData, string $charset): bool
Introduced in version 9.5.0.51

Encodes the text in $textData using the character encoding named by $charset, then uploads the resulting bytes to the remote file at $remotePath.

An absolute remote path begins with /. A relative path is interpreted relative to the authenticated SSH user's home directory. The remote parent directory must already exist.

Text encoding: $charset controls how characters are converted to bytes, for example utf-8, windows-1252, or iso-8859-1. SCP itself has no text mode; any line-ending characters already present in $textData are encoded and transferred as part of the text.

Returns true on success. On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns false). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

More Information and Examples
top
UseSsh
public function UseSsh(Ssh $sshConnection): bool
Introduced in version 9.5.0.51

Associates this Scp object with the connected and authenticated Ssh object in $sshConnection. Subsequent SCP operations use that existing SSH session rather than opening a separate network connection.

Connection, proxy, timeout, host-key verification, algorithm, logging, and other transport-related settings belong to the Ssh object and therefore apply to the SCP operations performed through it. Keep the SSH object connected and available for as long as the Scp object is using it.

SCP and SFTP are different protocols: Scp performs SCP-style transfers over SSH and requires compatible SCP support on the remote system. Use Chilkat.SFtp when the server expects the SSH File Transfer Protocol subsystem or when directory listing and remote file-management features are needed.

Returns true on success. On failure it throws Chilkat2\Exception (or, with RaiseError set to false, returns false). $e->getMessage() (or the object's LastErrorText) explains why, and the object remains usable.

top

Events

All Chilkat methods are synchronous: the call returns when the work is done. During a long-running call, Scp reports progress to handlers installed with three methods, each taking any PHP callable (a closure, an arrow function, $this->method(...), an invokable object) and returning the object, so the calls chain:

$scp->onPercentDone(function (int $pctDone): bool {
        echo "$pctDone%\n";
        return false;           // return true to abort the method in progress
    })
    ->onProgressInfo(function (string $name, string $value): void {
        echo "$name: $value\n";
    });
$scp->HeartbeatMs = 250;   // the AbortCheck handler is called 4 times per second
public function onAbortCheck(?callable $callback): static
public function onPercentDone(?callable $callback): static
public function onProgressInfo(?callable $callback): static

Each installs the handler for one event, replacing the one installed before; null removes it. A callable that does not exist is a TypeError right away.

The AbortCheck handler is called at the interval set by the HeartbeatMs property (0, the default, disables it); PercentDone is called when an operation's completion percentage is known; ProgressInfo delivers named progress values. A truthy return from the AbortCheck or PercentDone handler aborts the running method, which then fails in the usual way (Chilkat2\Exception, or false / null with RaiseError off). PHP's set_time_limit() does not interrupt a Chilkat call; an AbortCheck handler is how a script enforces its own limit.

Handlers run during the method call, in the same request. Inside a handler, the object's properties (such as $scp->AbortCurrent = true) and other objects may be used, but calling a method of the same object throws Error. An exception thrown by a handler aborts the running method and propagates from it; the object remains usable. A closure that captures $scp itself makes a reference cycle, which PHP's cycle collector frees.

AbortCheck
// handler: function (): bool -- return true to abort
public function onAbortCheck(?callable $callback): static

Enables a method call to be aborted by triggering the AbortCheck event at intervals defined by the HeartbeatMs property. If HeartbeatMs is set to its default value of 0, no events will occur. For instance, set HeartbeatMs to 200 to trigger 5 AbortCheck events per second.

More Information and Examples

Example

$deadline = microtime(true) + 30;                     // give up after 30 seconds
$scp->HeartbeatMs = 250;                       // call the handler 4 times per second
$scp->onAbortCheck(fn(): bool => microtime(true) > $deadline);
top
PercentDone
// handler: function (int $pctDone): bool -- return true to abort
public function onPercentDone(?callable $callback): static

This provides the percentage completion for any method involving network communications or time-consuming processing, assuming the progress can be measured as a percentage. This event is triggered only when it's possible and logical to express the operation's progress as a percentage. The pctDone argument will range from 1 to 100. For methods that finish quickly, the number of PercentDone callbacks may vary, but the final callback will have pctDone equal to 100. For longer operations, callbacks will not exceed one per percentage point (e.g., 1, 2, 3, ..., 98, 99, 100).

The PercentDone callback also acts as an AbortCheck event. For fast methods where PercentDone fires, an AbortCheck event may not trigger since the PercentDone callback already provides an opportunity to abort. For longer operations, where time between PercentDone callbacks is extended, AbortCheck callbacks enable more responsive operation termination.

To abort the operation, set the abort output argument to true. This will cause the method to terminate and return a failure status or corresponding failure value.

More Information and Examples

Example

$scp->onPercentDone(function (int $pctDone): bool {
    // $pctDone ranges from 0 to 100.
    echo "Percent done: $pctDone\n";
    return false;   // return true to abort the method in progress
});
top
ProgressInfo
// handler: function (string $name, string $value): void
public function onProgressInfo(?callable $callback): static

This event callback provides tag name/value pairs that detail what occurs during a method call. To discover existing tag names, create code to handle the event, emit the pairs, and review them. Most tag names are self-explanatory.

Note: Some Chilkat methods don't fire any ProgressInfo events.

More Information and Examples

Example

$scp->onProgressInfo(function (string $name, string $value): void {
    echo "$name: $value\n";
});
top