Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: torque (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/360827
[Lucid pkgs] everything starts up and runs ok with the fixes listed
above, one last detail: '/etc/init.d/torque-server stop' fails. It seems
the server.lock file in /var/lib/torque/serv_priv/ does not contain a
PID (??; look for another closed launchpad but report which speaks of
this, maybe
Hi,
for any Lucid / 10.04 LTS users who find themselves stuck on this--
I had to get it working on a number of machines so put together all the
above steps, and a few more into a fix-it script. It is assumed that
upgrading to the maverick+ packages will also solve these problems
without such
This also bug affects Lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/360827
Title:
A missing directory and wrong init-scripts in torque-2.3.6 in Jaunty
--
ubuntu-bugs mailing list
The torque 2.4 packages have arrived in Maverick. Please kindly
investigate if the bug is still valid.
--
A missing directory and wrong init-scripts in torque-2.3.6 in Jaunty
https://bugs.launchpad.net/bugs/360827
You received this bug notification because you are a member of Ubuntu
Bugs, which
Dear all,
Dominique, Morten and Jordi have now completed working on a 2.4-based packaging
of Torque and this should hit the Ubuntu servers any time soon. For the time
speaking it is Debian unstable for the very last four days now.
To do so add
deb-src http://ftp2.de.debian.org/debian/
Confirmed that this is still an issue in Karmic.
--
A missing directory and wrong init-scripts in torque-2.3.6 in Jaunty
https://bugs.launchpad.net/bugs/360827
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
After spending a bit of time, more than necessary, I got the server
working, but only after a number of times seeing /etc/init.d/torque-
server clobbering established node files.
To help others out in the same situation (i.e. people who don't read
carefully) I want to clarify the first bug report
A similar bug exists in version 2.1.8 (locally backported to feisty):
Setting up torque-mom (2.1.8+dfsg-0ubuntu1-bionmr2) ...
* Starting Torque Mom:
pbs_mom: No such file or directory (2) in chk_file_sec, Security violation with
These issues seem to be fixed in SVN.
--
A missing directory and wrong init-scripts in torque-2.3.6 in Jaunty
https://bugs.launchpad.net/bugs/360827
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
these changes were necessary (and worked) for me as well.
small exception: /etc/init.d/torque-sched is called /etc/init.d/torque-
scheduler
and: i had to create (and # chmod 1777) the following directories:
/var/lib/torque/spool
/var/lib/torque/undelivered
now torque works fine in my
** Visibility changed to: Public
--
A missing directory and wrong init-scripts in torque-2.3.6 in Jaunty
https://bugs.launchpad.net/bugs/360827
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
12 matches
Mail list logo
