Setting up a non-standard Proof cluster

Hi,
I have used Proof-lite for a while now and would like to move on to a full-blown proof cluster. I find the documentation to be rather sparse as soon as any of the setup is non-standard, which mine certainly is.
I have a number of questions and I will post them here as a I go along.

I am running on a cluster where other people may be using the /tmp in ways that I cannot control. So I would prefer to manage my own temp directory.

And here’s my first question: How do I get proof to use a different temporary directory than /tmp?
I’ve tried exporting TMP and I’ve tried setting “xpd.tmp /hep/simonhe/jobs” in the config file. My config file is:

### Load the XrdProofd protocol xrd.protocol xproofd libXrdProofd.so xpd.tmp /hep/simonhe/jobs
But what I see is:

simonhe@fend02 jobs> xproofd -c proof/xpd.simple.cf 110427 10:02:55 001 Scalla is starting. . . Copr. 2010 Stanford University, xrd version v20100913-0630-root-5 ++++++ xproofd anon@fend02.dcsc.ku.dk initialization started. Config using configuration file proof/xpd.simple.cf =====> xrd.protocol xproofd libXrdProofd.so Config maximum number of connections restricted to 1024 110427 10:02:55 001 xpd-I: Manager::Config: configuring 110427 10:02:55 001 xpd-I: Manager::Config: listening on port 1093 110427 10:02:55 001 xpd-I: Manager::Config: using temp dir: /tmp 110427 10:02:55 001 xpd-I: Manager::Config: role set to: any 110427 10:02:55 001 xpd-I: Manager::Config: admin path set to: /tmp/.xproofd.1093 110427 10:02:55 001 xpd-I: Manager::Config: unix sockets under: /tmp/.xproofd.1093/socks ............
So /tmp is still used. What should I do?

Hi,

I am not able to reproduce the problem: which ROOT version are you using? On which platform?

G. Ganis