Technical article 105504

Updating the number of pseudo ttys is not reflected in scoadmin/netconfig.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5

Written · Last revised

Problem

I used either "scoadmin network configuration manager" ("netconfig"),
"mkdev ptty", or "configure" to update the number of pseudo ttys
that the system has available.  However, when I bring up netconfig
again to view or modify the protocol configuration, the number of
pseudo ttys is listed as 32.  No matter how many pseudo ttys I
specify, netconfig always lists 32 as the number being configured.

Cause

Netconfig fails to read the current configuration value of the NSPTTY parameter as specified in the /etc/conf/cf.d/stune or mtune file, but instead always reports 32 as the configuration.

Solution

Using "configure" to increase the number of pseudo ttys is not
recommended since configure only updates the kernel tunable
parameter; it does not add the necessary device nodes.  If
"configure" was used to adjust NSPTTY, it is recommended
that NSPTTY be reset to the original value, and then adjusted
as desired using "mkdev ptty" as detailed below.
If either scoadmin/netconfig or "mkdev ptty" was used to adjust
the number of pseudo ttys, netconfig will still report that the
number of pseudo ttys configured is 32, however the update
performed was effective.  The stune file was updated and entries
were added to the spt and mpt files under the /etc/conf/node.d
directory.

To confirm the actual number of pseudo ttys configured, type this command at the shell prompt:

mkdev ptty
and select the option to display the number of pseudo ttys
configured.  If you wish to change the existing value, using
"mkdev ptty" is the recommended method.

This problem has been reported to SCO Engineering.

See also

netconfig(ADM), mkdev(ADM), configure(ADM), mtune(F), stune(F),
scohelp(XC)

Documents/scohelp: SCO Performance Guide, Appendix B, section "TTY and console configuration"

From the Xinuos technical article database, record 105504. Reproduced with permission. The original is at www.sco.com/ta/105504, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.