blob: 79447620e5d2663a108e84c47655fb1a3f73cbf7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
$NetBSD: patch-ae,v 1.1.1.1 2004/03/28 19:44:10 xtraeme Exp $
--- etc/router.xml.in.orig 2003-11-05 01:19:46.000000000 +0100
+++ etc/router.xml.in 2003-11-05 01:20:44.000000000 +0100
@@ -6,7 +6,7 @@
<!-- The process ID file. comment this out if you don't need to know
to know the process ID from outside the process (eg for control
scripts) -->
- <pidfile>@localstatedir@/jabberd/pid/router.pid</pidfile>
+ <pidfile>@PIDDIR@/router.pid</pidfile>
<!-- Log configuration - type is "syslog", "file" or "stdout" -->
<log type='syslog'>
@@ -19,7 +19,7 @@
<!-- If logging to file, this is the filename of the logfile -->
<!--
- <file>@localstatedir@/jabberd/log/router.log</file>
+ <file>@LOGDIR@/router.log</file>
-->
</log>
@@ -34,7 +34,7 @@
<!-- File containing the user table. This is where the router gets
its component and secret information from for component
authentication.-->
- <users>@sysconfdir@/router-users.xml</users>
+ <users>@PKG_SYSCONFDIR@/router-users.xml</users>
<!-- Shared secret used to identify legacy components (that is,
"jabber:component:accept" components that authenticate using
@@ -46,7 +46,7 @@
connections. If this is commented out, connecting components
will not be able to request a SSL-encrypted channel. -->
<!--
- <pemfile>@sysconfdir@/server.pem</pemfile>
+ <pemfile>@SSLCERTS@/server.pem</pemfile>
-->
</local>
|
