-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Daniel,
On 29/01/14 08:15, Daniel M. Weeks wrote:
> Yes, I quite agree. Please see the attached (rough) patch that we
> use on our production install. It could easily be adapted to other
> implementations.
I had a quick play with that and didn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
Found another xCAT bug, this time with the /opt/xcat/sbin/configmic
that is used to bring the MIC cards up.
For some reason on our system when this script runs the values of
$nodename is the short form hostname and $nodename_short is the long
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/01/14 14:08, Guang Cheng Li wrote:
> A nice catch, I updated the changes into xCAT 2.8.4 and 2.9.
No worries, thanks for committing it so quickly!
All the best,
Chris
- --
Christopher SamuelSenior Systems Administrator
VLSCI - Victo
HI Christopher,
A nice catch, I updated the changes into xCAT 2.8.4 and 2.9.
2.8.4: commit 5ac1ebaa633e42101bb7eb8a7c26db241dfaa4f2
2.9: commit 179a62145be1d9c46d23a1978c220cc40834db5f
Thanks,
-
Li,Guang Cheng (李光成)
IBM Ch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
We were puzzled when upgrading from xCAT 2.8.2 to 2.8.3 about why our
IB interfaces were suddenly not coming up any more, confignics was
saying (for example):
confignics on barcoo064: unknown nic type for ib0: 10.4.102.64 .
I was worried i
On 01/28/2014 12:16 AM, Christopher Samuel wrote:
> Hi folks,
>
> One thing that we notice with stateless nodes and software kits is
> that it can take quite a while to compress with bzip2.
>
> However, for RHEL EPEL there are two parallel bzip2 implementations
> (pbzip2 and lbzip2) and a paralle
Ok, solved my own problem. I changed the serial port number from 0 to 1 in
nodehm. These are first non IBM nodes in the cluster, a bit of a learning curve
dealing with them.
-- ddj
Dave Johnson
> On Jan 28, 2014, at 3:26 PM, Linda Mellor wrote:
>
> Is this a diskless image? I see some stu
Is this a diskless image? I see some stuff in genimage that
creates /etc/init.d/gettyset, and has some comments about RHEL6
open($cfgfile,">","$rootimg_dir/etc/init.d/gettyset");
:
print $cfgfile " if [ -x /sbin/initctl ]; then\n"; # Upstart
style
I'm baffled where gettyset actually comes from... in any case, the there are
error messages coming from gettyset since we moved from RHEL 5 to RHEL 6.
Machines with console redirection on ttyS0 seem to end up working OK, but I
have new machines where the console is on ttyS1. No booting info sh
