[torqueusers] upgrading 2.3.6 and /dev/null issue

[Gus Correa]

Hi Jack

This thread may help. It has various interesting insights on
how to upgrade Torque:

http://www.clusterresources.com/pipermail/torqueusers/2008-April/007224.html

Besides, in another thread that I cannot find now,
somebody whom I should thank and give credit if
I could find the thread, gave this excellent suggestion
of saving your current server configuration with:

qmgr -c 'p s' > current_torque_setup

then reading it back after the new server is installed,

qmgr -c < current_torque_setup

I hope this helps,
Gus Correa

On 06/13/2012 12:12 PM, David Beer wrote:
> According to TORQUE's CHANGELOG, this was fixed in 2.5.2.
>
> David
>
> On Wed, Jun 13, 2012 at 9:34 AM, Jack Fowler <fowler at hep.brown.edu
> <mailto:fowler at hep.brown.edu>> wrote:
>
>     Hi All,
>       We have the /dev/null bug as described here:
>     http://www.clusterresources.com/bugzilla/show_bug.cgi?id=61. We have
>     a default torque-2.3.6
>     installation on an old Scientific Linux 4.5 system. I'm thinking of
>     upgrading to torque-2.5.12. Note
>     that upgrading to a newer SL isn't possible at this time.
>       Will this fix the /dev/null issue? Is this the correct version?
>       Can I use the installation
>     procedure in the Admin Manual or are there additional issues/gotchas
>     I need to look at?
>
>     thanks,
>     Jack
>     _______________________________________________
>     torqueusers mailing list
>     torqueusers at supercluster.org <mailto:torqueusers at supercluster.org>
>     http://www.supercluster.org/mailman/listinfo/torqueusers
>
>
>
>
> --
> David Beer | Software Engineer
> Adaptive Computing
>
>
>
> _______________________________________________
> torqueusers mailing list
> torqueusers at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torqueusers