problems witht cell!=default

Bug #261190 reported by Peter Cordes
4
Affects Status Importance Assigned to Milestone
gridengine (Debian)
Fix Released
Undecided
Unassigned
gridengine (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I built the Intrepid source packages (6.2~beta2-2) on a Hardy AMD64 system. After installing, I configured with debconf. I chose the cell name equal to my cluster's name. Something must still be assuming SGE_CELL=default, though:

$ sudo -u sgeadmin qconf -au peter users
 error: cell directory "/var/lib/gridengine/default" doesn't exist

 I do have a /var/lib/gridengine/perun directory, though.

 I'm in a hurry, so I'm just going to reinstall SGE with cell=default

 I haven't seen a good tutorial about setting up grid engine, although I have used it on a Sun cluster.

Revision history for this message
Peter Cordes (peter-cordes) wrote :

This is probably because gridengine-common.postinst does
chown 644 ${TMPFILE}
instead of
chmod 644 ${TMPFILE}

so other tools can't read /etc/default/gridengine

Revision history for this message
Peter Cordes (peter-cordes) wrote :

sent email to Debian Grid Engine Maintainers <email address hidden>
to notify them of this and the csh dep bug. The bugs are too small to be worth filing on the Debian BTS too.

 BTW, I'm now sure that the chmod thing was the cause of my problems with CELL != default. It would be good if the prompts told you that most people do use CELL=default, not their hostname or anything.

Revision history for this message
Peter Cordes (peter-cordes) wrote :

fixed in Debian's 6.2-2, along with a documentation bug I reported to Debian's BTS. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497103

 The depend-on-csh bug isn't fixed, though.

Revision history for this message
Peter Cordes (peter-cordes) wrote :

Debian released the fix for this in 6.2-2

Changed in gridengine:
status: New → Fix Released
status: New → Confirmed
Revision history for this message
Phillip Susi (psusi) wrote :
Changed in gridengine (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.