[Condor-users] In a multi-startd setup, how do you prevent starter log collisions?

[Ian Chesal <ichesal@xxxxxxxxxxxxxxxxxx>]

Better subject would be: how do you prevent starter log collisions and keep the log files named sensibly. I'd like to be able to distinguish which log file goes with which slot without log file diving in startd logs.

I have the following mulit-startd configuration working:

# Define the first STARTD on this machine

STARTD1 = $(STARTD)

STARTD1_ARGS = -f -local-name S1

STARTD1_LOG = $(LOCAL_DIR)/log/StartdLog.1

STARTD1_EXECUTE = $(LOCAL_DIR)/execute.1

STARTD.S1.NUM_SLOTS = 2

STARTD.S1.STARTD_NAME = S1

STARTD.S1.STARTD_LOG = $(STARTD1_LOG)

STARTD.S1.STARTD_EXEUTE = $(STARTD1_EXECUTE)

DAEMON_LIST = $(DAEMON_LIST), STARTD1

# Define the second STARTD on this machine

STARTD2 = $(STARTD)

STARTD2_ARGS = -f -local-name S2

STARTD2_LOG = $(LOCAL_DIR)/log/StartdLog.2

STARTD2_EXECUTE = $(LOCAL_DIR)/execute.2

STARTD.S2.NUM_SLOTS = 2

STARTD.S2.STARTD_NAME = S2

STARTD.S2.STARTD_LOG = $(STARTD2_LOG)

STARTD.S2.STARTD_EXEUTE = $(STARTD2_EXECUTE)

DAEMON_LIST = $(DAEMON_LIST), STARTD2

DC_DAEMON_LIST = +STARTD1 STARTD2

But the StartLog.# files are colliding for the startd pairs.

Without resorting to something like $(PID) in the starter log file names, is there a way to prevent the collisions?

Thanks!

- Ian

---

Ian Chesal

Cycle Computing, LLC

Leader in Open Compute Solutions for Clouds, Servers, and Desktops

Enterprise Condor Support and Management Tools

http://www.cyclecomputing.com

http://www.cyclecloud.com

http://twitter.com/cyclecomputing