- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Delivering configuration files in SD packages
Operating System - HP-UX
1748014
Members
4741
Online
108757
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
Discussions
Discussions
Forums
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
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
тАО03-07-2010 04:00 PM
тАО03-07-2010 04:00 PM
Hi,
I'm creating a package of some software that will deliver a configuration file (e.g., /etc/opt/rt/myprogram.conf). I'd like to deliver a default configuration file that allows the program to work, but also allow the user to edit the configuration file, and not have their changes overwritten if they upgrade my package.
I assume one way to do this is to deliver the configuration file to /usr/newconfig, and have my postinstall script copy it to /etc if it doesn't already exist there. This would let the user examine the new file for any changes they might need to make to their existing configuration.
Alternatively, I see there's a 'volatile' flag that can be set on files in the PSF -- but it's not clear if this is sufficient to prevent the file being overwritten on upgrade, or if it just prevents swverify from complaining if it's edited.
Is there a recommended (or documented) way to do this?
Thanks.
I'm creating a package of some software that will deliver a configuration file (e.g., /etc/opt/rt/myprogram.conf). I'd like to deliver a default configuration file that allows the program to work, but also allow the user to edit the configuration file, and not have their changes overwritten if they upgrade my package.
I assume one way to do this is to deliver the configuration file to /usr/newconfig, and have my postinstall script copy it to /etc if it doesn't already exist there. This would let the user examine the new file for any changes they might need to make to their existing configuration.
Alternatively, I see there's a 'volatile' flag that can be set on files in the PSF -- but it's not clear if this is sufficient to prevent the file being overwritten on upgrade, or if it just prevents swverify from complaining if it's edited.
Is there a recommended (or documented) way to do this?
Thanks.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2010 07:14 PM
тАО03-07-2010 07:14 PM
Solution
>I assume one way to do this is to deliver the configuration file to /usr/newconfig, and have my postinstall script
I would suggest a configure script.
>it's not clear if this is sufficient to prevent the file being overwritten on upgrade, or if it just prevents swverify from complaining if it's edited.
Only the latter.
>Is there a recommended
Your /usr/newconfig/ idea seems best.
I would suggest a configure script.
>it's not clear if this is sufficient to prevent the file being overwritten on upgrade, or if it just prevents swverify from complaining if it's edited.
Only the latter.
>Is there a recommended
Your /usr/newconfig/ idea seems best.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2010 10:14 PM
тАО03-08-2010 10:14 PM
Re: Delivering configuration files in SD packages
Thanks - I'll go with that then.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP