| Main index | Section 1 | Options |
By default uhsoctl detaches from the terminal upon on a successful connection, a few command-line options exists that allows this behavior to be changed.
uhsoctl attempts to find a usable controlling serial port based on the provided network interface. If this fails you might specify a serial port manually.
| | |
| Specify APN to connect to. | |
| | |
| Specify CID (Context ID) to use, by default CID 1 is used. If an APN has been configured once, it's enough to specify the CID used for further accesses. | |
| | |
| Specify SIM PIN. | |
| | |
| Specify username. | |
| | |
| Specify username. | |
| | |
| Path to resolv.conf, default /etc/resolv.conf. Use /dev/null to disable updating of name servers. | |
| | |
| Explicitly set the serial port to use as controlling terminal. Might be needed if the automatic detection fails. | |
| | |
| Fork into background directly, before a connection has been established. | |
| | |
| Never fork into background, run entirely in foreground. | |
uhsoctl -a apn.example.com -p 1234 uhso0
Disconnect from a previously established connection.
uhsoctl -d uhso0
| UHSOCTL (1) | August 12, 2009 |
| Main index | Section 1 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
| “ | "I liken starting one's computing career with Unix, say as an undergraduate, to being born in East Africa. It is intolerably hot, your body is covered with lice and flies, you are malnourished and you suffer from numerous curable diseases. But, as far as young East Africans can tell, this is simply the natural condition and they live within it. By the time they find out differently, it is too late. They already think that the writing of shell scripts is a natural act." | ” |
| — Ken Pier, Xerox PARC | ||