GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Alternative to volume renames
Operating System - HP-UX
1847491
Members
3700
Online
110265
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
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
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-22-2004 05:24 AM
06-22-2004 05:24 AM
Alternative to volume renames
This is a good one:
We have two systems that have the same volume names, they are not done so for any other reason but to be simplistic. However, when we remote login to a system from the other one, and then trying to run scripts (on a cross mounted disk), the path is not unique.
Any ideas on how to aleviate this? We can rename the volumes, but what is the fallout from this?
Thanks,
Scott
We have two systems that have the same volume names, they are not done so for any other reason but to be simplistic. However, when we remote login to a system from the other one, and then trying to run scripts (on a cross mounted disk), the path is not unique.
Any ideas on how to aleviate this? We can rename the volumes, but what is the fallout from this?
Thanks,
Scott
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2004 05:30 AM
06-22-2004 05:30 AM
Re: Alternative to volume renames
When you say cross mounted, do you mean NFS, CIFS, Veritas Cluster ???
With NFS, you just use a different "root" name for the mount.
live free or die
harry
With NFS, you just use a different "root" name for the mount.
live free or die
harry
Live Free or Die
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2004 05:39 AM
06-22-2004 05:39 AM
Re: Alternative to volume renames
harry,
nfs.
sorry bout that
nfs.
sorry bout that
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