Hello all,
        We are trying a test in an attempt to resolve a NDMP backup
issue with our mail appliance.  What we are doing is installing a Linux
media server to backup the NDMP device, which should fix the NDMP issue.
Upon install of NBU on Linux, we get to installing PBX.  Here's what we
see:

Installing VRTSpbx...
 
                    VERITAS Private Branch Exchange 1.2.2.41
 
Checking system communication:
 
    Checking OS version on sharptop.longwood.edu ....... Linux
2.4.21-40.EL
    Checking system support for sharptop.longwood.edu ... Linux
2.4.21-40.EL supported by PBX
    Checking VRTSpbx package ................................ not
installed
 
Using rsh and rcp to communicate with remote systems.
 
Initial system check completed successfully.
 
                    VERITAS Private Branch Exchange 1.2.2.41
 
                    VERITAS Private Branch Exchange 1.2.2.41
 
                    VERITAS Private Branch Exchange 1.2.2.41
 
installics will install the following PBX packages on Linux target
systems:
sharptop.longwood.edu
 
VRTSicsco        VERITAS Common Infrastructure
VRTSpbx          VERITAS Private Branch Exchange
 
                    VERITAS Private Branch Exchange 1.2.2.41
 
Checking system installation requirements:
 
Checking PBX installation requirements on Linux target systems:
sharptop.longwood.edu
 
Checking PBX installation requirements on sharptop.longwood.edu:
 
    Checking for external dependencies ... all external dependencies
satisfied
    Checking file system space ................ required space is
available
    Stopping Private Branch Exchange daemon V-9-0-0 Cannot determine
localhost's dns domain name. This can cause
problems during installation if you have entered localhost's fully
qualified
domain name as an installation target. Please use only the hostname when
installing to this host.
 
                    VERITAS Private Branch Exchange 1.2.2.41
 
The installics log is saved at:
 
    /var/tmp/installics1020151519/installics.log


What we can't figure out is that the machine can resolve it's own name,
and it did earlier in the install.  Any suggestions on how to deal with
this?  As of right now, we don't have support for Linux - this is a
test, so I'm not sure where we would turn.

Thanks,
Jason

------------
Jason Brooks
Computer Systems Engineer
IITS - Longwood University
voice - (434) 395-2916
fax - (434) 395-2035
mailto:<brooksje at longwood.edu>