[torqueusers] Troubleshooting qsub -I interactive queue jobs
Atwood, Robert C
r.atwood at imperial.ac.uk
Wed Sep 5 13:45:47 MDT 2007
Yes I have tried solution (1) below with success, so far, but I may
resort to solution (0), not use dhcp on the external interface, the
external network people have admitted that it would be ok to do so, all
they really need is that I alter the external netmask to reflect the
expanded subnet, this can be done statically and will not need doing
again until the subnet is further expanded but .. probably there will be
a different computer cluster by that time!
Thanks for all the help, even though peripheral to TORQUE itself.
> -----Original Message-----
> From: James J Coyle [mailto:jjc at iastate.edu]
> Sent: 05 September 2007 17:15
> To: Atwood, Robert C
> Cc: Aaron Knister; torqueusers at supercluster.org
> Subject: Re: [torqueusers] Troubleshooting qsub -I
> interactive queue jobs
> To get /etc/resolv.conf to take precedence you'll need to
> change the file
> Try changing the entry for hosts in the file /etc/nsswitch.conf to:
> hosts: files dns
> This will read your /etc/hosts file first when resolving names.
> You may need to reboot for this to take effect.
> A better solution would be have correct settings in /etc/resolv.conf
> by either
> 1) Stopping dhcp from over-writing /etc/resolv.conf in the first place
> 2) Over-writing /etc/resolv.conf on reboots yourself by:
> A) Making a correct /etc/resolv.conf
> B) Copying this to /etc/resolv.conf.correct on each node.
> C) On each node edit the file /etc/rc3.d/S99local to append
> the command /bin/cp -f /etc/resolv.conf.correct
> (I am assuming that you come up in run level 3 and
> S99local is the
> last rc script run.)
> It is possible that you may need to your network after getting a
> correct resolv.conf in place. That is likely done by
> /sbin/service network restart
> or by invoking the correct rc3.d script with an argument of restart.
More information about the torqueusers