HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- XDC config file raid.conf can't be renamed
Operating System - Linux
1832489
Members
4404
Online
110043
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
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-30-2009 05:06 AM
03-30-2009 05:06 AM
XDC config file raid.conf can't be renamed
Hi,
We're currently working with eXtended Distance Cluster on legacy packages, and we have a problem with the raid.conf file.
It seems that the configuration file cannot be renamed despite the editable XDC_CONFIG_FILE variable in the package control file.
Looking at the "raid_control" script, it apears to expect the file to be named exactly "raid.conf".
Is it intended? Is there a way to turn around this problem? We would like to rename it to "raid_.conf" in order to avoid confusion on clusters hosting many packages.
Thanks in advance
M. Pauliac
excerpt from /usr/local/cmcluster/bin/raid_control :
-----------------------------------------------
(...)
else
# Set package type to LEGACY
PKG_TYPE="LEGACY"
#These variables hold the values of the parameters which are passed to this script
ACT="$1"
if [[ $(echo ${3##*/}) == "raid.conf" ]]; then
VG=( `echo "$2"`)
CONF_FILE="$3"
elif [[ $(echo ${2##*/}) == "raid.conf" ]]; then
VG=( `echo "$3"`)
CONF_FILE="$2"
fi
(...)
-----------------------------------------------
# rpm -qa|egrep '^xdc|^serviceg'
xdc-A.01.02-0.rhel4
serviceguard-A.11.18.04-0.rhel4
We're currently working with eXtended Distance Cluster on legacy packages, and we have a problem with the raid.conf file.
It seems that the configuration file cannot be renamed despite the editable XDC_CONFIG_FILE variable in the package control file.
Looking at the "raid_control" script, it apears to expect the file to be named exactly "raid.conf".
Is it intended? Is there a way to turn around this problem? We would like to rename it to "raid_
Thanks in advance
M. Pauliac
excerpt from /usr/local/cmcluster/bin/raid_control :
-----------------------------------------------
(...)
else
# Set package type to LEGACY
PKG_TYPE="LEGACY"
#These variables hold the values of the parameters which are passed to this script
ACT="$1"
if [[ $(echo ${3##*/}) == "raid.conf" ]]; then
VG=( `echo "$2"`)
CONF_FILE="$3"
elif [[ $(echo ${2##*/}) == "raid.conf" ]]; then
VG=( `echo "$3"`)
CONF_FILE="$2"
fi
(...)
-----------------------------------------------
# rpm -qa|egrep '^xdc|^serviceg'
xdc-A.01.02-0.rhel4
serviceguard-A.11.18.04-0.rhel4
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2009 12:47 PM
05-28-2009 12:47 PM
Re: XDC config file raid.conf can't be renamed
Hi,
we work with XDC and SGeSAP on SGLX (11.18) and with LEGACY Packages. My workaround for this problem, create directories:
Example for the SAP Packages:
$SGCONF/{SID}/RAIDCONFIG_dbci{SID}/raid.conf
/RAIDCONFIG_d01{SID}/raid.conf
2 packages in die {SID} directory with
2 different raid.conf
regards
Ruediger
we work with XDC and SGeSAP on SGLX (11.18) and with LEGACY Packages. My workaround for this problem, create directories:
Example for the SAP Packages:
$SGCONF/{SID}/RAIDCONFIG_dbci{SID}/raid.conf
/RAIDCONFIG_d01{SID}/raid.conf
2 packages in die {SID} directory with
2 different raid.conf
regards
Ruediger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2009 07:49 AM
06-02-2009 07:49 AM
Re: XDC config file raid.conf can't be renamed
Hi,
We're using a similar workaround but I still believe that we should be allowed to use a different filename.
Either that or the variable should be named XDC_CONFIG_DIR instead of XDC_CONFIG_FILE, since the filename 'raid.conf' is set in stone.
Anyway thank you for taking the time to reply.
M. Pauliac
We're using a similar workaround but I still believe that we should be allowed to use a different filename.
Either that or the variable should be named XDC_CONFIG_DIR instead of XDC_CONFIG_FILE, since the filename 'raid.conf' is set in stone.
Anyway thank you for taking the time to reply.
M. Pauliac
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2009 07:51 AM
06-02-2009 07:51 AM
Re: XDC config file raid.conf can't be renamed
Workaround already discussed, thread closed.
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