If the scripts are common for all nodes that hard coded in the exs.pm is
fine since not sure all the customized scripts need be added
into /etc/vmware/init/init.d/. Or changing the name of 95.updatestatus to
95.update so that any customized change can be added into this script.
If the script is spe
Hi Bob,
Yes, the /etc/resolv.conf on your management node seems correct.
Have you checked the ownership of /var/named directory? it should be
root:named or named:named.
After that, run makedns -n.
Best Regards,
-
Sun Jing(孙靖)
IBM China Software Development Labor
Dear all,
We finally figured out how to add our own init scripts to esxi hypervisors.
Here's what we did:
- create an updatestatus script
[root@xcat ~]# cat /opt/xcat/share/xcat/netboot/esxi/95.updatestatus
#!/bin/sh
/bin/echo installstatus booted | /bin/nc 172.31.32.254 3002
[root@xcat ~]#
- ad
Yes, this is the classic debate/issue of code formatting. It is tough for
all developers to agree on formatting style. Everyone has their own
preference. So we chose to put a higher priority on more substantial
coding practices, like comments, error checking, fault tolerance, code
reuse, etc. I
The /etc/resolv.conf file is fine:
[root@bp-xcat-01eth0 firmware]# cat /etc/resolv.conf
nameserver 172.20.224.51
search bp.cluster
Bob Krull
IBM Research
Emerging Technologies Solutions Development
rkr...@us.ibm.com
914-945-3801 / tie 862-3801-
Some code used perltidy when first checked in, but after that it is
pretty much up to the user. We try to not change more than the required
lines after that so that we can easily compare old and new versions.I
am afraid with the thousands of lines of xCAT code, it is a little late and
it ne
Hello all,
Correct me if I'm wrong please, but looking at the source code, I can't
find a pattern on the identation or any style at all. Is this
information correct? In affirmative case, I would suggest a pattern, so
we could improve the code maintainability, turning easy to read and make
patc
/etc/resolv.conf should have a line with nameserver set to site.master
and search set to site.domain. Then run makedns -n
Lissa K. Valletta
2-3/T12
Poughkeepsie, NY 12601
(tie 293) 433-3102
From: Robert W Krull/Watson/IBM@IBMUS
To: xcat-user@lists.sourceforge.net
Date: 08/22/2011
The ::1 has given me problems in the past, using makehosts to create your
hosts file. For example it would be something like ::1 mgt and fixing it
would result in something like:
172.20.0.1 mgt
127.0.0.1 localhost.localdomain localhost mgt
::1 mgt
Hi Robert,
* Set-up the /etc/resolv.conf correctly to point to the MN
* make sure /var/named has permissions named:named
* make suer selinux is turned off
* run makedhcp -n
I hope that helps
Arif Ali
catch me on freenode IRC, username: arif-ali
On 22/08/11 16:43, Robert W Krull wrote:
Hi,
Ju
Hi,
Just installed the latest xcat level on a new xcat server.
I have a pretty basic env:
[root@bp-xcat-01eth0 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4
localhost4.localdomain4
::1 localhost localhost.localdomain localhost6
localhost6.localdomain6
9.12.16
11 matches
Mail list logo
