GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- swinstall problem
Operating System - HP-UX
1850504
Members
2182
Online
104054
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2000 07:01 AM
06-30-2000 07:01 AM
swinstall problem
Hi
New L class(HPUX 11), insatlling ADSM client using following
swinstall -x mount_all_filesystems=false -v -s /tmp/adsm IBMADSM
I have done this many times before new/old systems, now I get an error
"you do not have req'd permissions"
I am ROOT, I have looked at swacl all seems ok - this is standard HP build
Any ideas
Steve
New L class(HPUX 11), insatlling ADSM client using following
swinstall -x mount_all_filesystems=false -v -s /tmp/adsm IBMADSM
I have done this many times before new/old systems, now I get an error
"you do not have req'd permissions"
I am ROOT, I have looked at swacl all seems ok - this is standard HP build
Any ideas
Steve
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2000 07:09 AM
06-30-2000 07:09 AM
Re: swinstall problem
These errors can be caused by confusion within the Software Distributor. There are different
sources of confusion are usually cleared up by following these instructions:
1.Login as root
2.Move the directory /var/adm/sw/security and its contents to /var/adm/sw/security.old
mv /var/adm/sw/security /var/adm/sw/security.old
3.Make an new /var/adm/sw/security directory
mkdir /var/adm/sw/security
4.Change the owner of the /var/adm/sw/security directory
chown bin:bin security
5.Change the mode of the /var/adm/sw/security directory
chmod 755 security
6.If installing from a cdrom unmount the cd.
umount /cdrom
7.Change the mode of the cdrom mount direcotry.
chmod 777 /cdrom
8.Stop the swagentd daemon.
/sbin/init.d/swagentd stop
NOTE: Execute this command on both local and remote machines, if applicable.
9.Register the source as a depot:
If the file is on the local machine:
swreg -l depot /tmp/PHxx_yyyy.depot
If the cdrom is on local machine:
swreg -l depot /cdrom
If the cdrom is on remote machine:
swreg -l depot @ "hostname":/cdrom
10.Restart the swagentd daemon.
/sbin/init.d/swagentd start
NOTE: Execute this command on both local and remote machines, if applicable.
11.If installing from a cdrom remount the cd.
mount /cdrom
12.Now re-install the software. swinstall
Of course, these errors may actually be a function of a non-root user attempting to execute
swinstall or some other Software Distributor function. To allow a non-root user to install
patches read the following.
sources of confusion are usually cleared up by following these instructions:
1.Login as root
2.Move the directory /var/adm/sw/security and its contents to /var/adm/sw/security.old
mv /var/adm/sw/security /var/adm/sw/security.old
3.Make an new /var/adm/sw/security directory
mkdir /var/adm/sw/security
4.Change the owner of the /var/adm/sw/security directory
chown bin:bin security
5.Change the mode of the /var/adm/sw/security directory
chmod 755 security
6.If installing from a cdrom unmount the cd.
umount /cdrom
7.Change the mode of the cdrom mount direcotry.
chmod 777 /cdrom
8.Stop the swagentd daemon.
/sbin/init.d/swagentd stop
NOTE: Execute this command on both local and remote machines, if applicable.
9.Register the source as a depot:
If the file is on the local machine:
swreg -l depot /tmp/PHxx_yyyy.depot
If the cdrom is on local machine:
swreg -l depot /cdrom
If the cdrom is on remote machine:
swreg -l depot @ "hostname":/cdrom
10.Restart the swagentd daemon.
/sbin/init.d/swagentd start
NOTE: Execute this command on both local and remote machines, if applicable.
11.If installing from a cdrom remount the cd.
mount /cdrom
12.Now re-install the software. swinstall
Of course, these errors may actually be a function of a non-root user attempting to execute
swinstall or some other Software Distributor function. To allow a non-root user to install
patches read the following.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2000 07:13 AM
06-30-2000 07:13 AM
Re: swinstall problem
Have you restarted the swagent deamon?
# swagentd -r
Then try the swinstall again.
# swagentd -r
Then try the swinstall again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2000 07:13 AM
06-30-2000 07:13 AM
Re: swinstall problem
Hello!
If it is a new machine, you should ensure yourself:
a) your machine knows who it is: try: 1. #uname ?a and #hostname, you shoud get the name of the machine
2. ping machine_name being login in the new machine (ping yourself).
b) if pcts a and b are ok, restart the swagent (kill the swagentd daemon and restart it: /usr/sbin/swagentd ?r).
Check as well the logfile (/var/adm/sw/swagentd.log). Come back with details if not working.
If it is a new machine, you should ensure yourself:
a) your machine knows who it is: try: 1. #uname ?a and #hostname, you shoud get the name of the machine
2. ping machine_name being login in the new machine (ping yourself).
b) if pcts a and b are ok, restart the swagent (kill the swagentd daemon and restart it: /usr/sbin/swagentd ?r).
Check as well the logfile (/var/adm/sw/swagentd.log). Come back with details if not working.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP