Re: Dynamicallhy Changing Linux Guest Network
Lionel, We just tested such a scenario at a DR exercise this past week. A common script was installed on all our Linux servers and set to execute at an early run-level prior to network initialization. The script reads a shared CMS file using the cmsfs package then updates config files accordingly. The input file contains network configuration items for both home and DR. By externalizing the data on a CMS disk customization of each Linux server is not required - one script fits all. We plan to use the script for initial builds at home as well. It worked like a charm. If anyone is interested in the details, please contact me off-list. ...Nick. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Lionel Dyck Sent: Friday, August 14, 2009 11:01 AM To: LINUX-390@VM.MARIST.EDU Subject: Dynamicallhy Changing Linux Guest Network Does anyone have a z/vm and/or linux script that they could share that can be used to dynamically change the linux servers network when the server is brought up at a dr site and/or when the network addressing is changed? I've tried playing with it without success - keep missing a piece here or there. thx Lionel B. Dyck, z/Linux Virtualization Specialist IBM Global Services - Kaiser Permanente Team Linux on System z Service Delivery Team 925-926-5332 (8-473-5332) | E-Mail: ld...@us.ibm.com AIM: lbdyck | Yahoo IM: lbdyck I never guess. It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. - Sir Arthur Conan Doyle -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 This e-mail message and any attachments contain confidential information from Medco. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
NFS V4 Server for SLES9
We are implementing WebSphere clustering with dynamic failover on SLES9 servers. This clustering configuration requires each server to write its log files on a shared directory that can be accessed by other servers in the cluster. WebSphere uses a file locking mechanism to determine if servers in the cluster are up or down. We discovered that the NFS server distributed with SLES9 does not support file locking. This feature is provided in V4 NFS servers. SLES10 is distributed with a V4 NFS server, but not SLES9. Has anyone tried to install the SLES10 V4 NFS server on a SLES9 system? I'm guessing it would not be supported, but will it work? Does anyone know of a V4 NFS server supported on SLES9? Thanks for any suggestions.. Nick Said Insurance Services Office Office: (201) 469-3263 Cell: (845) 551-1018 This email is intended for the recipient only. If you are not the intended recipient please disregard, and do not use the information for any purpose. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: NFS V4 Server for SLES9
This is the issue, Mark. Thanks for the feedback. Our move to SLES10 is
becoming more imminent.
...Nick.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Perry
Sent: Friday, March 21, 2008 11:47 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: NFS V4 Server for SLES9
Sorry!
I do see the potential problem you are in - if Websphere is using
flock().
The source code explicitly state no BSD flocks
* No BSD flocks over NFS allowed.' (See code excerpt below)
The code on SLES10 has an flock() function and it looks to me like it
will convert flock() to a POSIX lock.
Not sure if thats what you want, but I think using SLES10 is your only
option. (With NFS V3 or V4)
mark
From fs/nfs/file.c:
/*
* Lock a (portion of) a file
*/
int
nfs_lock(struct file *filp, int cmd, struct file_lock *fl)
{
struct inode * inode = filp-f_mapping-host;
int status = 0;
int status2;
dprintk(NFS: nfs_lock(f=%s/%ld, t=%x, fl=%x, r=%Ld:%Ld)\n,
inode-i_sb-s_id, inode-i_ino,
fl-fl_type, fl-fl_flags,
(long long)fl-fl_start, (long long)fl-fl_end);
if (!inode)
return -EINVAL;
/* No mandatory locks over NFS */
if ((inode-i_mode (S_ISGID | S_IXGRP)) == S_ISGID)
return -ENOLCK;
if (NFS_PROTO(inode)-version != 4) {
/* Fake OK code if mounted without NLM support */
if (NFS_SERVER(inode)-flags NFS_MOUNT_NONLM) {
if (IS_GETLK(cmd))
status = LOCK_USE_CLNT;
goto out_ok;
}
}
/*
* No BSD flocks over NFS allowed.
* Note: we could try to fake a POSIX lock request here by
* using ((u32) filp | 0x8000) or some such as the pid.
* Not sure whether that would be unique, though, or whether
* that would break in other places.
*/
if (!fl-fl_owner || !(fl-fl_flags FL_POSIX))
return -ENOLCK;
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
This email is intended for the recipient only. If you are not the intended
recipient please disregard, and do not use the information for any purpose.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
