Le 13/04/2018 à 03:09, Arnau a écrit :
> Hi,
>
> $ cat /etc/debian_version
> 9.4
>
> $ dpkg -l|grep ssl
> ii libflac8:amd64 1.3.2-1
> amd64 Free Lossless Audio Codec - runtime C library
> ii libssl-doc 1.1.0f-3+deb9u2
Hi,
thought I post this here FYI: the integration of TensorFlow with Grid Engine
covered in this blog
https://blogs.univa.com/2018/04/integrating-distributed-tensorflow-with-grid-engine/
is described for Univa Grid Engine and should be working for other versions of
Grid Engine as well, at
On Mon, 16 Apr 2018, William Hay wrote:
...
I don't think that can be right given that the qmaster complains about
multiple user files on start up. If it gave up after the first then
presumably it wouldn't complain about the others.
All I know is that, when we had this sort of problem, most
On Mon, Apr 16, 2018 at 12:16:26PM +0100, Mark Dixon wrote:
> Hi William,
>
> I've seen this before back in the SGE 6.2u5 days when it used to write out
> core binding options it couldn't subsequently read back in.
>
> IIRC, users are read from disk at startup in turn and then the files are
>
Hi William,
I've seen this before back in the SGE 6.2u5 days when it used to write out
core binding options it couldn't subsequently read back in.
IIRC, users are read from disk at startup in turn and then the files are
only written to from then on - so this sort of thing only tends to be
We had a user report that one of their array jobs wasn't scheduling A
bit of poking around showed that qconf -suser knew nothing of the user
despite them having a queued job. However there was a file in the spool
that should have defined the user. Several other users appear to be
affected as
