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://www.itresourcecenter.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: Wed Aug 15 3:10:04 PDT 2001

Table of Contents:

Document ID Title
--------------- -----------
2200104314 SYS ADM: tar(1) command behavior; relative versus absolute pa
1200129979 X.25, J2793B: x25idmap not in kernel, recovery of root disk ch
2200123495 SYSADM: lpstat(1) -a, -p options; acceptance versus enabled/d
3200070937 SYS ADM: How to create Swap or Dump logical volumes

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


Document ID: 2200104314
Date Loaded: 20010811
      Title: SYS ADM: tar(1) command behavior; relative versus absolute paths

PROBLEM

The tar(1) command seems to hang when attempting to restore files
from a tape. For example:

     # tar xvf /dev/rmt/0m /ABC.def/g/

appears to hang. However, the tape drive light is blinking.

The following command

     # tar tvf /dev/rmt/0m

displays a listing of all files and directories.

What is causing this problem?

CONFIGURATION

Operating System - HP-UX
Version - 10.20
Subsystem - SYS ADM

RESOLUTION

A listing of the contents of a tape may be obtained with

     # tar tf /dev/rmt/0m > contents_file

Files which appear as:

     ABC.def/g/
     ABC/dev/g/example/a/50/filename
     ...

would have been copied to tape with a RELATIVE path. Note that
no slash "/" appears at the beginning of the paths above.

This explains why the use of "/ABC.def/g/..." failed to restore
any files. The following command will restore files and
directories RELATIVE to the current working directory:

     # tar xvf /dev/rmt/0m ABC.def/g/

With the tar command that contained the ABSOLUTE path of
/ABC.def/g/, it is likely that the tape drive light was blinking
because the tar command continued to search for an ABSOLUTE path
that did not exist on the tape.

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


Document ID: 1200129979
Date Loaded: 20010811
      Title: X.25, J2793B: x25idmap not in kernel, recovery of root disk changed major number

PROBLEM

After recovering a root disk on an HP-UX 11.0 computer, the
X.25 link product, Product Number J2793B, was no longer
functional. This product was running as expected prior to
recovering the root disk.

How can this problem be resolved?

CONFIGURATION

Operating System - HP-UX
Version - 11.0
Subsystem - X.25

RESOLUTION

The following investigation was performed:

     1. A symptom was that /dev/x25ipmap had not been
         configured in the kernel.

     2. These commands indicated that the major number of the
         dev file was lower than the major number reported by
         lsdev(1M).

              # lsdev | grep x25idmap

              # grep x25idmap /stand/system

              # ll /dev/x25idmap

         The lsdev major numbers had been reshuffled.

To resolve the problem, it was necessary to adapt the dev files
by rerunning the scripts used by swinstall(1M) as follows:

     # swconfig -x reconfig=true J2793B

     # /sbin/init.d/x25 start

An alternative method would be to do the following:

     # swlist -l fileset J2793B

       This points to the SX25* and SYNC-WAN* directories

     # cd /var/adm/sw/products

     # find S[XY]* -name configure | xargs grep mknod

       Rerun the scripts to execute mknod(1M) all dev files
       depending on the current output of lsdev(1M).

     # /sbin/init.d/x25 start

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


Document ID: 2200123495
Date Loaded: 20010807
      Title: SYSADM: lpstat(1) -a, -p options; acceptance versus enabled/disabled

PROBLEM

The lpstat(1) command appears to differentiate between the various
states of a print queue. A queue that is "down" is still able to
accept requests until a reject command is issued.

Please confirm what the lpstat(1) options -a and -p mean.

CONFIGURATION

Operating System - HP-UX
Subsystem - SYSADM

RESOLUTION

The key is to understand the meaning of acceptance versus enabled/
disabled.

Acceptance is the ability to accept requests. This allows to
accept/deny requests. Optionally, a "deny reason" may be specified.

Enable/disable: In both cases, if the acceptance is granted, a new
print request will be saved under /var/spool/request/<lpname>.

If a printer is enabled, the request is printed while if it is
disabled, the reque will not be printed but will stay in the queue.

The following example illustrates this concept:

     # lpstat -p
     printer lp1 is idle. enabled since Jul 23 13:17
             fence priority : 0

     # lpstat -alp1
     lp1 accepting requests since Jul 23 13:19

     # disable lp1
     printer "lp1" now disabled

     # ll | lp -dlp1
     request id is lp1-31 (standard input)

     # lpstat -t
     scheduler is running
     no system default destination
     device for lp1: /dev/null
     lp1 accepting requests since Jul 23 13:19
     printer lp1 disabled since Jul 23 13:25 -
             reason unknown
             fence priority : 0
     lp1-31 root priority 0 Jul 23 13:27
             (standard input) 70 bytes

     NOTE: The request has been accepted and stays queued because
            the printer has been disabled.

     # enable lp1
     printer "lp1" now enabled

     To change the acceptance status, use the reject(1M) command:

     # reject -r"toner on order, use an other printer" lp1
     destination "lp1" will no longer accept requests

     # lpstat -alp1
     lp1 not accepting requests since Jul 23 13:31 -
             toner in order, use an other printer

     Now, attempts to send a new print request produce this error:

     # ll | lp -dlp1
     lp: can't accept requests for destination "lp1" -
             toner in order, use an other printer

     To re-activate the acceptance, use the accept command:

     # accept lp1
     destination "lp1" now accepting requests

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


Document ID: 3200070937
Date Loaded: 20010720
      Title: SYS ADM: How to create Swap or Dump logical volumes

PROBLEM

Please describe how to create swap or dump logical volumes
on an HP-UX 11.0 computer.

CONFIGURATION

Operating System - HP-UX
Version - 11.0
Subsystem - SYS ADM

RESOLUTION

To create a dump logical volume, do the following:

     Note: The dump devices have to be part of vg00.

     1. Create a contiguous logical volume inside vg00 with bad
         block reallocation turned off:

         lvcreate -L size -C y -r n /dev/vg00

     2. Turn on the dump device for the logical volume just
         created:

         lvlnboot -d /dev/vg00/lvolX

To create a swap logical volume, do the following:

     Note: The swap and dump can be created on the same logical
            volumes. The swap devices do not need to be part of
            vg00, but they can be.

     1. Create a contiguous logical volume:

         lvcreate -L size -C y /dev/vgX

     2. Turn swap on in the logical volume:

         swapon /dev/vgX/lvolY

     IMPORTANT: The default priority for swap is "1". It is a
                 recommended to have all the swap devices set to
                 the same priority.

     3. Edit the /etc/fstab so that swap will be turned on at
         boot-up; add the following line:

         /dev/vgX/lvolY ... swap defaults 0 2

     NOTE: If you want to remove swap or change the priority of
            swap, then it is necessary to edit the /etc/fstab and
            then reboot the system.

The difference between file system swap and device swap is as
follows:

File system swap:

    o can be configured dynamically.

    o allows a process to use an existing file system if it
       needs more than the designated device swap space.

    o is used only when device swap space is insufficient to
       meet demand-paging needs.

    o consumes a variable amount of space because it only uses
       that portion of a file system that it needs.

Once a file system has been enabled for file system swap, it is
not possible to unmount that file system until the swap is
disabled at the next reboot. It is possible to limit file system
swap to a fixed size to prevent it from consuming too much space.

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

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