HP Support Information Digests

===============================================================================
o IT Resource Center World Wide Web Service
   ---------------------------------------------------

   If you subscribed through the IT Resource Center and would
   like to be REMOVED from this mailing list, access the
   IT Resource Center on the World Wide Web at:

     http://support.itrc.hp.com/

   Login using your IT Resource Center User ID and Password.
   Then select Support Information Digests (located under
   Maintenance and Support). You may then unsubscribe from the
   appropriate digest.
===============================================================================


Digest Name: monthly HP-UX technical tips digest
    Created: Sun Dec 15 6:10:04 EST 2002

Table of Contents:

Document ID Title
--------------- -----------
4000041319 Behavior of ksh(1) and sh-posix(1) shells for HISTFILE
4000029382 HP-UX, can inted specify a specific TCP port for an RPC proces
4000027644 HP-UX system unable to boot into single-user or maintenance mo
2200287563 HP-UX mk_kernel fails with "Ignoring -s option" erro

The documents are listed below.
-------------------------------------------------------------------------------


Document ID: 4000041319
Date Loaded: 20021212
      Title: Behavior of ksh(1) and sh-posix(1) shells for HISTFILE

PROBLEM

The ksh(1) and sh-posix(1) shells appear to ignore a HISTFILE
definition "export HISTFILE=sh_hist.test" in .profile as
illustrated by the following:

     1. Define a test function such as abcsi() and include
         it at the end of /etc/profile:

              abcsi() {
                echo hallo
              };

     2. Login with rlogin(1) or telnet(1) and note that the
         sh_hist.test is not used, even though the setting is:

              $ echo $HISTFILE
              sh_hist.test

Why does this behavior occur?

CONFIGURATION

Operating System - HP-UX
Version - 10.X, 11.X
Subsystem - Shells

RESOLUTION

The reason for this behavior in the Korn and POSIX shell is
documented in

     Morris I. Bolsky, David G. Korn
     The Kornshell
     Command and Programming Language
     Prentice Hall 1989
     ISBN 0-13-516972-0

At the following web site, under the "HISTFILE" definition,
search for "nolog":

     http://www.UNIX-systems.org/single_unix_specification_v2/xcu/sh.html

The first function definition causes the shell to open the history
file if "nolog" is NOT set. Since this is the default, and since
the function definition in /etc/profile precedes the definition of
HISTFILE in ~/.profile, the history file is opened with the default
name. To avoid this, use "set -o nolog" in /etc/profile.

ALT KEYWORDS

histfile
posix
-----End of Document ID: 4000041319------------------------------------------


Document ID: 4000029382
Date Loaded: 20021212
      Title: HP-UX, can inted specify a specific TCP port for an RPC process?

PROBLEM

The inetd service is used to start an RPC server based process
on an HP-UX 11.0 system in order to tunnel through a networking
firewall. Thus, the server based process needs to listen on a
specific TCP port.

Is it possible to configure inetd to start the RPC service such
that it listens on a specific TCP port?

CONFIGURATION

Operating System - HP-UX
Version - 11.0

RESOLUTION

No. The inetd (Internet Services Daemon) starts off the RPC
server based process just fine, however, there is no means of
configuring which TCP port that RPC server process will bind
and listen to/on. If the RPC server process needs to bind to
a specific port then, instead of using inetd, it would be
necessary to reproduce all the RPC server code in the
application.

It is possible to bind to a specific port on the server ok
(e.g. nfsd does this), just not through inetd. The following
O'Reilly publication is a very good reference that explains
how this can be done:

     Power Programming with RPC
          by John Bloomer

<!-- ALT KEYWORDS -->
-----End of Document ID: 4000029382------------------------------------------


Document ID: 4000027644
Date Loaded: 20021212
      Title: HP-UX system unable to boot into single-user or maintenance mode

PROBLEM

An HP-UX 11.0 system hangs when booting to single-user or
LVM maintenance mode. The last message printed to the
console is

     /sbin/ioinitrc:

The system boots fine to multiuser mode.

How can this problem be resolved?

CONFIGURATION

Operating System - HP-UX
Version - 11.0

RESOLUTION

The /dev/systty file (and also /dev/syscon linked to
/dev/systty) were found to be regular files rather than
what they should be - special files.

The following steps resolved this problem:

     1. Remove the old files:

         # rm /dev/systty

         # rm /dev/syscon

     2. Create the special file:

         # mknod /dev/systty c 0x0 0x000000

     3. Define the necessary link to the special file:

         # ln /dev/systty /dev/syscon

     4. Set permissions:

         # chmod 622 /dev/systty

     5. Verify all is correct:

         # ll /dev/sys*

     6. Boot the system to test for a successful boot to
         single-user and maintenance mode. The problem
         should be resolved.

<!-- ALT KEYWORDS -->
-----End of Document ID: 4000027644------------------------------------------


Document ID: 2200287563
Date Loaded: 20021212
      Title: HP-UX mk_kernel fails with &quot;Ignoring -s option&quot; error

PROBLEM

The following error occurs when attempting to regenerate
a kernel on an HP-UX 11.0 system:

     # mk_kernel
     Generating module: krm...
     /usr/ccs/bin/ld: (Warning) Ignoring -s option. -r will
override -s
     /usr/ccs/bin/ld: (Warning) Ignoring -s option. -r will
override -s
     Compiling /stand/build/conf.c...
     Loading the kernel...
     Generating kernel symbol table...

     Usage: bstab input_data symbol_cnt strtbl_size kernel_file
output_file

     *** Error exit code 1
     Stop.
     config: make did an exit(1)

What is causing this problem and how can it be corrected?

CONFIGURATION

Operating System - HP-UX
Version - 11.0

RESOLUTION

This problem was caused by the environment parameter LDOPTS
that was defined with a "-s" included. This will strip the
symbols of the executable and produce the error described
above.

To correct this problem, unset LDOPTS before doing a
mk_kernel(1M). For example:

     # unset LDOPTS

     # mk_kernel
     Generating module: krm...
     Compiling /stand/build/conf.c...
     Loading the kernel...
     Generating kernel symbol table...

<!-- ALT KEYWORDS -->
-----End of Document ID: 2200287563------------------------------------------

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]