Stress Test: hupctl

### TEST NAME

> hupctl - verify that the HUPCTL property works

### SYNOPSIS

> `hupcli -d` devicename `-b` baudrate

> `hupclo -d` devicename `-b` baudrate

### DESCRIPTION

> The `hupctl` program verifies the standard terminal/modem property `Hang up on last close`. It uses the `termio`(7I) implementation.

> The `hupcli` command is started on the transmitter side. The `hupclo` command is started on the receiver side.

> `hupcli` runs for a predetermined period of time, based on the value of the `RUNTIME` environment variable. When `HUPCTL` occurs, that is, when `hupclo` completes its reading (receiving), the device opened by `hupclo` is also closed.

### OPERANDS

> `-d` devicename
>   Device for communication. The device name should follow the full path. Usually all dialout device paths start with `/dev/cua/`.

> `-b` baudrate
>   Baud rate. This must be the one specified in the `termio`(7I) man page.

### DURATION

> 10 minutes

### POSSIBLE CONCURRENT TESTS

> No other concurrent tests are possible on the same port. That is, no other concurrent tests are possible on the port specified by devicename.

### EXAMPLES

> If:

> - Receiver device is `/dev/cua/a`
> - Transmitter device is `/dev/cua/b`
> - Receiver baud rate is 38400
> - Transmitter baud rate is 38400

> Then, on the receiver side:

> > `# hupcli -d /dev/cua/a -b 38400`

> On the transmitter side:

> > `# hupclo -d /dev/cua/b -b 38400`

> NOTE: The receiver and transmitter can be on the same machine or on different machines, but they must be physically connected.

### REFERENCES

> `termio`(7I)

Copyright 2005 Sun Microsystems, Inc. All rights reserved.