public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Christoph Junghans" <ottxor@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sys-cluster/htcondor/files/
Date: Mon, 12 Jan 2015 00:00:24 +0000 (UTC)	[thread overview]
Message-ID: <1421002339.19a85a847f3602e1f96aff7f5dac7bdfc3ff9ff5.ottxor@gentoo> (raw)

commit:     19a85a847f3602e1f96aff7f5dac7bdfc3ff9ff5
Author:     Marius Brehler <marbre <AT> linux <DOT> sungazer <DOT> de>
AuthorDate: Sun Jan 11 18:52:19 2015 +0000
Commit:     Christoph Junghans <ottxor <AT> gentoo <DOT> org>
CommitDate: Sun Jan 11 18:52:19 2015 +0000
URL:        http://sources.gentoo.org/gitweb/?p=proj/sci.git;a=commit;h=19a85a84

sys-cluster/htcondor: Add condor_config.generic-8.3.2.patch

---
 .../files/condor_config.generic-8.3.2.patch        | 43 ++++++++++++++++++++++
 1 file changed, 43 insertions(+)

diff --git a/sys-cluster/htcondor/files/condor_config.generic-8.3.2.patch b/sys-cluster/htcondor/files/condor_config.generic-8.3.2.patch
new file mode 100644
index 0000000..8e8fac9
--- /dev/null
+++ b/sys-cluster/htcondor/files/condor_config.generic-8.3.2.patch
@@ -0,0 +1,43 @@
+--- b/src/condor_examples/condor_config.generic	2015-01-11 19:34:36.000000000 +0100
++++ a/src/condor_examples/condor_config.generic	2015-01-11 19:38:18.000000000 +0100
+@@ -19,7 +19,7 @@
+ ######################################################################
+ 
+ ##  Where have you installed the bin, sbin and lib condor directories?   
+-RELEASE_DIR = /usr/local/condor
++RELEASE_DIR = /usr
+ 
+ ##  Where is the local condor directory for each host?  This is where the local config file(s), logs and
+ ##  spool/execute directories are located. this is the default for Linux and Unix systems.
+@@ -27,18 +27,22 @@ RELEASE_DIR = /usr/local/condor
+ ##  this is the default on Windows sytems
+ #LOCAL_DIR = $(RELEASE_DIR)
+ 
+-##  Where is the machine-specific local config file for each host?
+-LOCAL_CONFIG_FILE = $(LOCAL_DIR)/condor_config.local
+-##  If your configuration is on a shared file system, then this might be a better default
+-#LOCAL_CONFIG_FILE = $(RELEASE_DIR)/etc/$(HOSTNAME).local
++## Looking for LOCAL_CONFIG_FILE? You will not find it here. Instead
++## put a file in the LOCAL_CONFIG_DIR below. It is a more extensible
++## means to manage configuration. The order in which configuration
++## files are read from the LOCAL_CONFIG_DIR is lexicographic. For
++## instance, config in 00MyConfig will be overridden by config in
++## 97MyConfig.
+ ##  If the local config file is not present, is it an error? (WARNING: This is a potential security issue.)
+-#REQUIRE_LOCAL_CONFIG_FILE = true
++REQUIRE_LOCAL_CONFIG_FILE = false
+ 
+-##  The normal way to do configuration with RPMs is to read all of the
+-##  files in a given directory that don't match a regex as configuration files.
++##  Where are optional machine-specific local config files located?
+ ##  Config files are read in lexicographic order.
+-LOCAL_CONFIG_DIR = $(LOCAL_DIR)/config
+-#LOCAL_CONFIG_DIR_EXCLUDE_REGEXP = ^((\..*)|(.*~)|(#.*)|(.*\.rpmsave)|(.*\.rpmnew))$
++##  No default.
++LOCAL_CONFIG_DIR        = $(ETC)/config.d
++
++## Blacklist for file processing in the LOCAL_CONFIG_DIR
++LOCAL_CONFIG_DIR_EXCLUDE_REGEXP = ^((\..*)|(.*~)|(#.*)|(.*\.rpmsave)|(.*\.rpmnew))$
+ 
+ ##  Use a host-based security policy. By default CONDOR_HOST and the local machine will be allowed
+ use SECURITY : HOST_BASED


             reply	other threads:[~2015-01-12  0:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12  0:00 Christoph Junghans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-25 16:39 [gentoo-commits] proj/sci:master commit in: sys-cluster/htcondor/files/ Justin Lecher
2015-01-12  0:00 Christoph Junghans
2015-01-12  0:00 Christoph Junghans
2015-01-12  0:00 Christoph Junghans
2013-07-12 17:37 Sebastien Fabbro
2013-07-12 17:37 Sebastien Fabbro
2013-07-12 17:37 Sebastien Fabbro
2013-07-12 17:37 Sebastien Fabbro
2013-07-12 17:37 Sebastien Fabbro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1421002339.19a85a847f3602e1f96aff7f5dac7bdfc3ff9ff5.ottxor@gentoo \
    --to=ottxor@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox