blob: 6a52b7083208cc50a5c6192b41faf9d33e08f91d [file] [log] [blame]
Harald Welte4ff37fe2016-02-20 10:56:10 +01001== Running OsmoPCU
2
3The OsmoPCU executable (`osmo-pcu`) offers the following command-line
4options:
5
6
7=== SYNOPSIS
8
9*osmo-pcu* [-h|-V] [-D] [-c 'CONFIGFILE'] [-r 'PRIO'] [-m 'MCC'] [-n 'MNC']
10
11
12=== OPTIONS
13
14*-h, --help*::
15 Print a short help message about the supported options
16*-V, --version*::
Harald Weltec925ccc2019-12-01 14:27:19 +010017 Print the compile-time version number of the program
Harald Welte4ff37fe2016-02-20 10:56:10 +010018//*-D, --daemonize*::
19// Fork the process as a daemon into background.
20*-c, --config-file 'CONFIGFILE'*::
21 Specify the file and path name of the configuration file to be
22 used. If none is specified, use `osmo-pcu.cfg` in the current
23 working directory.
24*-r, --realtime 'PRIO'*::
25 Enable use of the Linux kernel realtime priority scheduler with
26 the specified priority.
27 It is recommended you use this option on low-performance
28 embedded systems or systems that encounter high non-GSM/GPRS
29 load.
30*-m, --mcc 'MCC'*::
31 Use the given MCC instead of that provided by BTS via PCU socket
32*-n, --mnc 'MNC'*::
33 Use the given MNC instead of that provided by BTS via PCU socket