HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Fileset count mismatch
Operating System - HP-UX
1833874
Members
1917
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
Go to solution
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
04-04-2007 11:14 AM
04-04-2007 11:14 AM
Hello,
I am preparing to patch the Prod server and have an issue matching the fileset count between the create_depot script, swinstall -p and swlist -l fileset commands.
I just built a depot from a recent patch assessment with PH patches and the GOLDQPK11i depot.
My concerns are:
- why does the result of swinstall -p have such low fileset numbers compared to create_depot and swlist cmd ? Does swinstall group the filesets into subproducts and t hus report a fewer filesets ?
The swjob cmd after a create_depot script gives:
* 1151 of 1151 filesets had no Errors or Warnings.
The swjob list after an swinstall -p -d command shows:
* Summary of Analysis Phase:
* 34 of 341 filesets will be Skipped.
* 307 of 341 filesets had no Errors or Warnings.
And, the swlist -l fileset gives:
swlist -l fileset -d @ |grep -v "#"|wc -l
1152
OR: 1583 - with dependencies (#) included.
Thanks,
Warren
I am preparing to patch the Prod server and have an issue matching the fileset count between the create_depot script, swinstall -p and swlist -l fileset commands.
I just built a depot from a recent patch assessment with PH patches and the GOLDQPK11i depot.
My concerns are:
- why does the result of swinstall -p have such low fileset numbers compared to create_depot and swlist cmd ? Does swinstall group the filesets into subproducts and t hus report a fewer filesets ?
The swjob cmd after a create_depot script gives:
* 1151 of 1151 filesets had no Errors or Warnings.
The swjob list after an swinstall -p -d
* Summary of Analysis Phase:
* 34 of 341 filesets will be Skipped.
* 307 of 341 filesets had no Errors or Warnings.
And, the swlist -l fileset
swlist -l fileset -d @
1152
OR: 1583 - with dependencies (#) included.
Thanks,
Warren
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2007 10:29 PM
04-04-2007 10:29 PM
Solution
Either you or I'm confused. (I hate it when commands have two different ways of doing things.)
I found you never use -d with SD except some very few commands. Instead use -s for source and "@" for target.
So what do these say:
# swinstall -p -s
# swlist -l fileset -s |grep -v "#"|wc -l
Also swlist will list everything and swinstall will only list what can be installed or hasn't been installed.
I found you never use -d with SD except some very few commands. Instead use -s for source and "@" for target.
So what do these say:
# swinstall -p -s
# swlist -l fileset -s
Also swlist will list everything and swinstall will only list what can be installed or hasn't been installed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2007 08:07 AM
04-05-2007 08:07 AM
Re: Fileset count mismatch
Thanks for the information on what swlist and swinstall returns. I can live with the fileset counts now. Also, sorry I did not mention I have the patch_match_target=true, which is probably the reason for your confusion and mine. The numbers look better using the command:
swinstall -p -s
with result:
* Summary of Analysis Phase:
* 594 of 898 filesets will be Skipped.
* 304 of 898 filesets had no Errors or Warnings.
Yes two ways to do the same command is confusing to me. I now understand I can write the same command as:
swlist -l fileset -s
swlist -l fileset -d @ /patches/april32007/depot|grep -v "#"|wc -l
thanks again
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 2025 Hewlett Packard Enterprise Development LP