[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] append_files for stdout/err in local universe
- Date: Thu, 20 Sep 2018 07:57:48 +0200 (CEST)
- From: "Beyer, Christoph" <christoph.beyer@xxxxxxx>
- Subject: Re: [HTCondor-users] append_files for stdout/err in local universe
Is naming the output file $(Cluster).out an option ?
All you need to do is cat the .out files in the end ?
Building 02b, Room 009
----- UrsprÃngliche Mail -----
Von: Jameson Graef Rollins <jrollins@xxxxxxxxxxxxxxxx>
An: Condor-Users Mail List <condor-users@xxxxxxxxxxx>
Gesendet: Thu, 20 Sep 2018 06:24:13 +0200 (CEST)
Betreff: [HTCondor-users] append_files for stdout/err in local universe
Hello. I have a persistent, long-running job that I'm trying to manage
with condor in the local universe. I have configured condor to relaunch
the job if it exits. However, every time it relaunches it truncates and
writes over the old stdout and stderr log files, which is quite
annoying, and makes it know what went wrong.
I'm curious why the append_files directive , which would apparently
allow me to configure the log files to be appended instead of
overwritten, is only available in the standard universe. Why isn't this
available in the local universe?
Does anyone have any suggestions for how to deal with the issue I'm
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: