Difference between revisions of "OS4X Core binaries"

From OS4X
Jump to navigation Jump to search
Line 73: Line 73:
 
The main OS4X receive daemon which is responsible for accepting OFTP sessions. This daemon starts several processes:
 
The main OS4X receive daemon which is responsible for accepting OFTP sessions. This daemon starts several processes:
 
*<code>os4xrd</code>: the management process which manages all subsequent child processes
 
*<code>os4xrd</code>: the management process which manages all subsequent child processes
*<code>os4xrd_tcpip</code>: main receive process for incoming TCP/IP connections. After having accepted a connection, this processes created a new child process:
+
*<code>os4xrd_tcpip</code>: main receive process for incoming TCP/IP connections. After having accepted a connection, this processes creates a new child process:
 
**<code>os4xrd_tcpip_active</code>: an active TCP/IP OFTP connection
 
**<code>os4xrd_tcpip_active</code>: an active TCP/IP OFTP connection
*<code>os4xrd_tcpip_tls</code>: main receive process for incoming TLS secured TCP/IP connections. After having accepted a connection, this processes created a new child process:
+
*<code>os4xrd_tcpip_tls</code>: main receive process for incoming TLS secured TCP/IP connections. After having accepted a connection, this processes creates a new child process:
 
**<code>os4xrd_tcpip_active</code>: an active TLS secured TCP/IP OFTP connection
 
**<code>os4xrd_tcpip_active</code>: an active TLS secured TCP/IP OFTP connection
*<code>os4xrd_capi_[number]</code>: main receive process for incoming ISDN connections. After having accepted a call, this processes created a new child process:
+
*<code>os4xrd_capi_[number]</code>: main receive process for incoming ISDN connections. The number is the index value of the CAPI configuration row. After having accepted a call, this processes creates a new child process:
 
**<code>os4xrd_capi_[number]_active</code>: an active CAPI OFTP connection
 
**<code>os4xrd_capi_[number]_active</code>: an active CAPI OFTP connection

Revision as of 14:28, 30 June 2007

os4xeq / os4xeq2

Add a file to the send queue.

input parameters

  • -h: printf this help text
  • -C <configfile>: use given config file (default: /etc/os4x.conf)
  • -p <partner shortname>
  • -f <filename with absolute path>
  • -v <virtual filename>
  • -c <comment (max. 255 chars./without special chars.)>
  • -q <alternative SSID for this file (originator)>
  • -r <alternative SSID for this file (destination)>
  • -s <alternative SFID for this file (originator)>
  • -t <alternative SFID for this file (destination)>
  • -w <alternative password for this file (originator)>
  • -x <alternative password for this file (destination)>
  • -u <priority, default: 0>
  • -i <server ID, default: 0>
  • -P: add file passive to send queue (let partner fetch it from remote)
  • -d: <optional file description in OFTPv2 session>
  • -V: print out version and exit

os4xlic

This tool displays the OS4X ID, an installation specific hash value, which identifies this copy of OS4X.

input parameters

  • -h: help text
  • -I: display OS4X ID only (without headers)
  • -v: display version information and exit

examples

localhost:~/tmp username$ ./os4xlic 
OS4X license tool v2.0

your OS4X ID is:
8b6c03222dc17af20d4c022d6cf92d502cb8d51b230467582b8d111a39e7b0bcv2

(all in one line)
localhost:~/tmp username$ ./os4xlic -I
8b6c03222dc17af20d4c022d6cf92d502cb8d51b230467582b8d111a39e7b0bcv2

os4x_licinfo

Display the information encoded in an OS4X license file.

input parameters

  • -h: help text
  • -C configfile: use given config file (default: /etc/os4x.conf)
  • -f license file: use the given license file as input
  • -d: display end date of validity
  • -I: display licensed OS4X ID
  • -p: display amount of licensed partners
  • -a: display licensed functions
  • -A: display licensed functions, as numeric value
  • -v: display version information and exit

examples

localhost:~/tmp username$ ./os4x_licinfo -I
8b6c03222dc17af20d4c022d6cf92d502cb8d51b230467582b8d111a39e7b0bcv2
localhost:~/tmp username$ ./os4x_licinfo -f /opt/os4x/bin/license.key -d
20080331

os4xrd / os4xrd2

The main OS4X receive daemon which is responsible for accepting OFTP sessions. This daemon starts several processes:

  • os4xrd: the management process which manages all subsequent child processes
  • os4xrd_tcpip: main receive process for incoming TCP/IP connections. After having accepted a connection, this processes creates a new child process:
    • os4xrd_tcpip_active: an active TCP/IP OFTP connection
  • os4xrd_tcpip_tls: main receive process for incoming TLS secured TCP/IP connections. After having accepted a connection, this processes creates a new child process:
    • os4xrd_tcpip_active: an active TLS secured TCP/IP OFTP connection
  • os4xrd_capi_[number]: main receive process for incoming ISDN connections. The number is the index value of the CAPI configuration row. After having accepted a call, this processes creates a new child process:
    • os4xrd_capi_[number]_active: an active CAPI OFTP connection