cvs/JSOC/config.local.template

__DEFS__

# NetDRMS local site configuration info
# edit the values in the second column of each line in this file to reflect
#   the values appropriate to your site

# a marker to indicate whether this file has been checked/edited. You MUST
# either change its value to yes (or anything but NO) or comment it out.
LOCAL_CONFIG_SET        NO

# the next three entries must almost certainly be changed to reflect your
#   local configuration

# the name of the NetDRMS database; the SUMS database will be assumed to
#   have the same name with "_sums" appended
DRMS_DATABASE   mydb

# the host name of the default database server you will be accessing; you
#   should include the internet domain (e.g. host.subnet.net) if the server is
#   not on your subnet; but if it is on your subnet it may be better not to
# the default value is only really appropriate if you are running in a
#   single-user environment, such as a laptop; whether it is the default
#   or a named host depends on how the postgres database named above and
#   its dependent _sums have been configured in their pg_hba.conf files:
#   localhost for METHOD "trust", a named host for METHOD "ident sameuser"
DBSERVER_HOST   localhost

# the port number for the DRMS database server - default should be okay
#   unless in use otherwise
DRMS_DBPORT     5432

# a 15-bit numerical site identifier; values < 16384 (0x4000) are for
#   publicly exporting sites, and must be registered to assure uniqueness
# the default value is for a private unregistered site, and may not provide
#   access to publicly exporting sites
DRMS_SITE_CODE  0x4000

# the default values for the following five entries may or may not be
#   appropriate for your site configuration, depending on how and where
#   third-party software has been set up and installed

# the user name of the postgres administrative account; normally "postgres"
#   if you have followed the PostgreSQL installation suggestions
POSTGRES_ADMIN  postgres

# a sample namespace appropriate to your site; this is only used for a
#   couple of database initialization scripts and is not important for
#   subsequent installations/updates
DRMS_SAMPLE_NAMESPACE   drms

# The remaining definitions only need to be reviewed and modified as
#   appropriate if you will be doing a "make sums" as or in behalf of the
#   SUMS_MANAGER; they do not affect the functioning of the libraries and
#   applications  built by a regular user with plain "make"; nevertheless
#   it is probably a good idea to keep them consistent for the site

# The following entries are for slony processing of mirrored data archives;
#   they are not currently used in the "make"

# the postgres user name of the slony administrative account; normally "slony"
SLONY_ADMIN     slony

# the base directory for slony logs
SLONY_LOG_BASEDIR       /usr/local/logs/slony

# the user name(s) or email addresses for slony problem notifications
SLONY_NOTIFY    production

# The following entries are specific to the SUMS configuration

# the user name of the SUMS administrator account - a special account is
#   recommended for multi-user systems, but not required
SUMS_MANAGER    production

# the group name for users permitted to add data to DRMS/SUMS; not
#   currently used in code, but should match the group ownership of
#   the SUMS root directories /SUM*
SUMS_GROUP      drms

# the host name of the default SUMS server you will be using; this is the
#   the machine that the SUMS storage units are mounted on, not necessarily
#   the machine serving the Postgres SUMS database
SUMS_SERVER_HOST        localhost

# the port number for the DRMS database server - default should be okay
#   unless in use otherwise
SUMS_DBPORT     5434

# the number of sum_svc processes, per sum service (e.g., SUM_get, SUM_alloc) to start, 
# by default, when multi-SUMS starts up.
SUM_NUMSUM    3

# the maximum number of sum_svc processes, per sums service.
SUM_MAXNUMSUM 8

# the base directory for SUMS logs and configuration files; used by
#   base/sums/apps/sum_svc.c and sum_rm.c
SUMS_LOG_BASEDIR        /usr/local/logs/SUM

# the directory in which the binary of sum_chmown, a root setuid program,
#   is installed; must be mounted locally on the machine on which the
#   SUMS partition are mounted; used by base/sums/apps/sum_svc_proc.c
SUMS_BIN_BASEDIR        /usr/local/bin

# whether a tape archive service is available for SUMS or not; set to a
#   non-zero value if it is
SUMS_TAPE_AVAILABLE     0

# whether or not there exist multiple SUMS partition sets
SUMS_MULTIPLE_PARTNSETS      0

# If AUTOSELCOMP is 1, then the configure script will automatically select
# the 'best' compiler for use with the make system (choosing icc over gcc).
# Set this to 0 to permit manual selection via the JSOC_COMPILER and JSOC_FCOMPILER
# environment variables, or via editing of make_basic.mk
AUTOSELCOMP (1)

SUMS_DEBUG 0

# SUMS Export - specify how to construct 4 arguments that represent the
#   transfer program (e.g. scp), the user, the host, and the port to be used
#   in a command line for fetching SUMS data from a server via sum_export_svc.
#   Use a printf format string, followed by any combination of the following
#   string variables: meth, user, host, domain, port. These string variables
#   are populated from the SUMS_URL value in jsoc.drms_sites, which has the
#   form:
#
#   <meth>://<user>@<host>.<domain>:<port>
#
# The meth variable is assigned the string <meth>, the user variable is
#   assigned the string <user>, and so on.
#
# The 4 arguments will be used as follows to construct a command line:
#     METH -P PORT USER@HOST:file destfile (if PORT is not 0)
#     METH USER@HOST:file destfile (if PORT is 0)
#
# N.B. The default values, as provided in the commented-out definitions below,
#   will result in a command of the form:
#     METH -P PORT USER@HOST.DOMAIN:file destfile (if PORT is not 0)
#     METH USER@HOST.DOMAIN:file destfile (if PORT is 0)
#   It is only necessary to uncomment the definitions if you need to provide
#   a different command, for example,
#     METH USER@HOST-PORT:file destfile
#   in which case you would have to define:
#     SUMEXP_HOSTFMT    "%s-%s", host, port
#   and
#     SUMEXP_PORTFMT    "0"

# METH argument - The transfer program name (eg., scp-hpn)
#SUMEXP_METHFMT  "%s", meth

# USER argument - The user account name on the HOST containing the source file
#SUMEXP_USERFMT  "%s", user

# HOST argument - The host machine containing the source file
#SUMEXP_HOSTFMT  "%s.%s", host, domain

# PORT argument - The port on the host machine to connect to
#SUMEXP_PORTFMT  "%s", port

__MAKE__

# Third-party libraries required in order to make NetDRMS binaries. Specify
# a default and also machine-specific locations (if desired). The default will
# be used if no machine-specific entry exists.

# *** PostgreSQL ***

#   defaults
#     PostgreSQL API headers (must contain libpq-fe.h)
POSTGRES_INCS:X86_64    /usr/include
POSTGRES_INCS:IA32      /usr/include
#     the location of the PostgreSQL libs; likely to be either
#     /usr/lib or /usr/lib64 or /usr/local/pgsql/lib
POSTGRES_LIBS:X86_64    /usr/lib64
POSTGRES_LIBS:IA32      /usr/lib

#     actual library names
POSTGRES_LIB            pq

#   machine-specific
#     The following is an example:
#     POSTGRES_LIBS:N02     /usr/lib64

# *** end PostgreSQL ***

# *** CFITSIO ***

#   defaults
#     CFITSIO API headers (must contain fitsio.h)
CFITSIO_INCS:X86_64     /home/jsoc/include
CFITSIO_INCS:IA32       /home/jsoc/include

#     the location of the cfitsio libraries
CFITSIO_LIBS:X86_64     /home/jsoc/lib/linux-x86_64
CFITSIO_LIBS:IA32       /home/jsoc/lib/linux-ia32

#     actual library names
CFITSIO_LIB             cfitsio

#   machine-specific
#     The following is an example:
#     CFITSIO_LIBS:N02  /usr/lib64

# *** end CFITSIO ***

# NetDRMS users can request subdirectories from the Stanford proj directories 
# (e.g., JSOC/proj/util). These users will need to contact Stanford and obtain
# the source subdirectories desired. They will then place these subdirectories
# in the JSOC/proj directory of their NetDRMS release. To properly build 
# targets in these subdirectories, using the JSOC make system, the user needs
# to add entries to this configuration file - one entry for each subdirectory
# that contains source code to be compiled. Each entry is a space-separated pair
# of strings: the string "PROJDIR" followed by a subdirectory (of the proj 
# directory).  For example:
#
# PROJDIR     util/apps
# PROJDIR     util/libs
# 
# NOTE: It is not sufficient to list only a parent directory, like util. Source code
# in child directories will not automatically be compiled.
Revision:	1.16
Committed:	Wed Sep 14 22:56:27 2011 UTC (12 years ago) by arta
Branch:	MAIN
CVS Tags:	NetDRMS_Ver_6-2, NetDRMS_Ver_6-3, NetDRMS_Ver_6-0, NetDRMS_Ver_6-1, NetDRMS_Ver_2-7
Changes since 1.15:	+2 -0 lines
Log Message:	Localize the SUMS tape-system code. Remote sites will not use it. The SUMS_TAPE_AVAILABLE config.local parameter controls whether or not a tape-system is present.
#	Content
1	__DEFS__
2
3	# NetDRMS local site configuration info
4	# edit the values in the second column of each line in this file to reflect
5	# the values appropriate to your site
6
7	# a marker to indicate whether this file has been checked/edited. You MUST
8	# either change its value to yes (or anything but NO) or comment it out.
9	LOCAL_CONFIG_SET NO
10
11	# the next three entries must almost certainly be changed to reflect your
12	# local configuration
13
14	# the name of the NetDRMS database; the SUMS database will be assumed to
15	# have the same name with "_sums" appended
16	DRMS_DATABASE mydb
17
18	# the host name of the default database server you will be accessing; you
19	# should include the internet domain (e.g. host.subnet.net) if the server is
20	# not on your subnet; but if it is on your subnet it may be better not to
21	# the default value is only really appropriate if you are running in a
22	# single-user environment, such as a laptop; whether it is the default
23	# or a named host depends on how the postgres database named above and
24	# its dependent _sums have been configured in their pg_hba.conf files:
25	# localhost for METHOD "trust", a named host for METHOD "ident sameuser"
26	DBSERVER_HOST localhost
27
28	# the port number for the DRMS database server - default should be okay
29	# unless in use otherwise
30	DRMS_DBPORT 5432
31
32	# a 15-bit numerical site identifier; values < 16384 (0x4000) are for
33	# publicly exporting sites, and must be registered to assure uniqueness
34	# the default value is for a private unregistered site, and may not provide
35	# access to publicly exporting sites
36	DRMS_SITE_CODE 0x4000
37
38	# the default values for the following five entries may or may not be
39	# appropriate for your site configuration, depending on how and where
40	# third-party software has been set up and installed
41
42	# the user name of the postgres administrative account; normally "postgres"
43	# if you have followed the PostgreSQL installation suggestions
44	POSTGRES_ADMIN postgres
45
46	# a sample namespace appropriate to your site; this is only used for a
47	# couple of database initialization scripts and is not important for
48	# subsequent installations/updates
49	DRMS_SAMPLE_NAMESPACE drms
50
51	# The remaining definitions only need to be reviewed and modified as
52	# appropriate if you will be doing a "make sums" as or in behalf of the
53	# SUMS_MANAGER; they do not affect the functioning of the libraries and
54	# applications built by a regular user with plain "make"; nevertheless
55	# it is probably a good idea to keep them consistent for the site
56
57	# The following entries are for slony processing of mirrored data archives;
58	# they are not currently used in the "make"
59
60	# the postgres user name of the slony administrative account; normally "slony"
61	SLONY_ADMIN slony
62
63	# the base directory for slony logs
64	SLONY_LOG_BASEDIR /usr/local/logs/slony
65
66	# the user name(s) or email addresses for slony problem notifications
67	SLONY_NOTIFY production
68
69	# The following entries are specific to the SUMS configuration
70
71	# the user name of the SUMS administrator account - a special account is
72	# recommended for multi-user systems, but not required
73	SUMS_MANAGER production
74
75	# the group name for users permitted to add data to DRMS/SUMS; not
76	# currently used in code, but should match the group ownership of
77	# the SUMS root directories /SUM*
78	SUMS_GROUP drms
79
80	# the host name of the default SUMS server you will be using; this is the
81	# the machine that the SUMS storage units are mounted on, not necessarily
82	# the machine serving the Postgres SUMS database
83	SUMS_SERVER_HOST localhost
84
85	# the port number for the DRMS database server - default should be okay
86	# unless in use otherwise
87	SUMS_DBPORT 5434
88
89	# the number of sum_svc processes, per sum service (e.g., SUM_get, SUM_alloc) to start,
90	# by default, when multi-SUMS starts up.
91	SUM_NUMSUM 3
92
93	# the maximum number of sum_svc processes, per sums service.
94	SUM_MAXNUMSUM 8
95
96	# the base directory for SUMS logs and configuration files; used by
97	# base/sums/apps/sum_svc.c and sum_rm.c
98	SUMS_LOG_BASEDIR /usr/local/logs/SUM
99
100	# the directory in which the binary of sum_chmown, a root setuid program,
101	# is installed; must be mounted locally on the machine on which the
102	# SUMS partition are mounted; used by base/sums/apps/sum_svc_proc.c
103	SUMS_BIN_BASEDIR /usr/local/bin
104
105	# whether a tape archive service is available for SUMS or not; set to a
106	# non-zero value if it is
107	SUMS_TAPE_AVAILABLE 0
108
109	# whether or not there exist multiple SUMS partition sets
110	SUMS_MULTIPLE_PARTNSETS 0
111
112	# If AUTOSELCOMP is 1, then the configure script will automatically select
113	# the 'best' compiler for use with the make system (choosing icc over gcc).
114	# Set this to 0 to permit manual selection via the JSOC_COMPILER and JSOC_FCOMPILER
115	# environment variables, or via editing of make_basic.mk
116	AUTOSELCOMP (1)
117
118	SUMS_DEBUG 0
119
120	# SUMS Export - specify how to construct 4 arguments that represent the
121	# transfer program (e.g. scp), the user, the host, and the port to be used
122	# in a command line for fetching SUMS data from a server via sum_export_svc.
123	# Use a printf format string, followed by any combination of the following
124	# string variables: meth, user, host, domain, port. These string variables
125	# are populated from the SUMS_URL value in jsoc.drms_sites, which has the
126	# form:
127	#
128	# <meth>://<user>@<host>.<domain>:<port>
129	#
130	# The meth variable is assigned the string <meth>, the user variable is
131	# assigned the string <user>, and so on.
132	#
133	# The 4 arguments will be used as follows to construct a command line:
134	# METH -P PORT USER@HOST:file destfile (if PORT is not 0)
135	# METH USER@HOST:file destfile (if PORT is 0)
136	#
137	# N.B. The default values, as provided in the commented-out definitions below,
138	# will result in a command of the form:
139	# METH -P PORT USER@HOST.DOMAIN:file destfile (if PORT is not 0)
140	# METH USER@HOST.DOMAIN:file destfile (if PORT is 0)
141	# It is only necessary to uncomment the definitions if you need to provide
142	# a different command, for example,
143	# METH USER@HOST-PORT:file destfile
144	# in which case you would have to define:
145	# SUMEXP_HOSTFMT "%s-%s", host, port
146	# and
147	# SUMEXP_PORTFMT "0"
148
149	# METH argument - The transfer program name (eg., scp-hpn)
150	#SUMEXP_METHFMT "%s", meth
151
152	# USER argument - The user account name on the HOST containing the source file
153	#SUMEXP_USERFMT "%s", user
154
155	# HOST argument - The host machine containing the source file
156	#SUMEXP_HOSTFMT "%s.%s", host, domain
157
158	# PORT argument - The port on the host machine to connect to
159	#SUMEXP_PORTFMT "%s", port
160
161	__MAKE__
162
163	# Third-party libraries required in order to make NetDRMS binaries. Specify
164	# a default and also machine-specific locations (if desired). The default will
165	# be used if no machine-specific entry exists.
166
167	# * PostgreSQL *
168
169	# defaults
170	# PostgreSQL API headers (must contain libpq-fe.h)
171	POSTGRES_INCS:X86_64 /usr/include
172	POSTGRES_INCS:IA32 /usr/include
173	# the location of the PostgreSQL libs; likely to be either
174	# /usr/lib or /usr/lib64 or /usr/local/pgsql/lib
175	POSTGRES_LIBS:X86_64 /usr/lib64
176	POSTGRES_LIBS:IA32 /usr/lib
177
178	# actual library names
179	POSTGRES_LIB pq
180
181	# machine-specific
182	# The following is an example:
183	# POSTGRES_LIBS:N02 /usr/lib64
184
185	# * end PostgreSQL *
186
187	# * CFITSIO *
188
189	# defaults
190	# CFITSIO API headers (must contain fitsio.h)
191	CFITSIO_INCS:X86_64 /home/jsoc/include
192	CFITSIO_INCS:IA32 /home/jsoc/include
193
194	# the location of the cfitsio libraries
195	CFITSIO_LIBS:X86_64 /home/jsoc/lib/linux-x86_64
196	CFITSIO_LIBS:IA32 /home/jsoc/lib/linux-ia32
197
198	# actual library names
199	CFITSIO_LIB cfitsio
200
201	# machine-specific
202	# The following is an example:
203	# CFITSIO_LIBS:N02 /usr/lib64
204
205	# * end CFITSIO *
206
207	# NetDRMS users can request subdirectories from the Stanford proj directories
208	# (e.g., JSOC/proj/util). These users will need to contact Stanford and obtain
209	# the source subdirectories desired. They will then place these subdirectories
210	# in the JSOC/proj directory of their NetDRMS release. To properly build
211	# targets in these subdirectories, using the JSOC make system, the user needs
212	# to add entries to this configuration file - one entry for each subdirectory
213	# that contains source code to be compiled. Each entry is a space-separated pair
214	# of strings: the string "PROJDIR" followed by a subdirectory (of the proj
215	# directory). For example:
216	#
217	# PROJDIR util/apps
218	# PROJDIR util/libs
219	#
220	# NOTE: It is not sufficient to list only a parent directory, like util. Source code
221	# in child directories will not automatically be compiled.