File: config.h

package info (click to toggle)
diald 0.99.4-9
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 1,148 kB
  • ctags: 935
  • sloc: ansic: 7,109; tcl: 977; sh: 880; perl: 306; makefile: 109
file content (128 lines) | stat: -rw-r--r-- 4,702 bytes parent folder | download | duplicates (4)
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
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
/*
 * config.h - Configuration options for diald.
 *
 * Copyright (c) 1994, 1995, 1996 Eric Schenk.
 * Copyright (c) 1999 Mike Jagdis.
 * All rights reserved. Please see the file LICENSE which should be
 * distributed with this software for terms of use.
 *
 * These are the compile time defaults for various system files.
 * You may want to edit these to match your system before you compile diald.
 * However, if you didn't, don't panic. Almost all of these locations can be
 * configured at run time if necessary. The only thing you can't configure
 * at run time is the location of the main diald configuration files.
 *
 */

/*
 * Diald needs to be able to find its default configuration files.
 * These paths should match the installation path in the Makefile!
 * THIS MUST BE CONFIGURED AT COMPILE TIME IF YOU WANT TO CHANGE IT!
 */
#define DIALD_CONFIG_FILE "/etc/diald/diald.options"
#define DIALD_DEFS_FILE "/etc/diald/diald.defs"

/*
 * The default access to be allowed on monitor connections. Note
 * that connections on the control fifo can always do anything
 * because there is no way to determine who asked. This only
 * applies to TCP monitor connections. The full list of access
 * flags can be found in access.h.
 *   N.B. If ACCESS_CONTROL is not set then *anything* received
 * on the pipe is treated as a message and no commands are possible.
 * If ACCESS_AUTH is not set then the "auth" command may not
 * be used to get other than the default access capabilities.
 */
#define CONFIG_DEFAULT_ACCESS \
	(ACCESS_CONTROL | ACCESS_AUTH \
	| ACCESS_MONITOR)

#if 0
/* This is not needed. See the TODO file. */

/* The PORT_MASQ_BEGIN and PORT_MASQ_END defines specify the range
 * of ports which may be used by the kernel masquerade code under Linux.
 * Some sites that need to masquerade many connections at once may have
 * increased this range. If so you should change the defines here. For a
 * truely general diald you should leave both undefined but this adds some
 * usually unnecessary overhead.
 *  N.B. The demasquerading needs to be enabled using the "demasq" option.
 * FIXME: This probably isn't a big killer unless you have lots of
 * short lived connections?
 */
#define PORT_MASQ_BEGIN	61000
#define PORT_MASQ_END	(PORT_MASQ_BEGIN + 4096)
#endif


/*****************************************************************************
 * EVERYTHING BELOW HERE IS RUN TIME CONFIGURABLE
 * You can change these things if you want to save yourself some
 * entries in your configuration files.
 ****************************************************************************/

/*
 * Your lock files are probably somewhere else unless you
 * happen to be running a newer distribution that is compiliant
 * the the Linux File System Standard. On older distributions
 * you will usually find them in /var/spool/uucp or /usr/spool/uucp.
 */
#define LOCK_PREFIX	"/var/lock/LCK.."

/*
 * If your lock files should contain binary PID's then
 * set the following to 0. I think most linux
 * distributions want ASCII PID's in the lock files.
 */
#define PIDSTRING 1

/*
 * Define where to put the diald.pid file. Under the FSSTD this 
 * should be in /var/run, but you're system might have them
 * elsewhere. Check and be sure.
 */

#define RUN_PREFIX	"/var/run"


/* The following will all be searched for in /sbin:/usr/sbin:/bin:/usr/bin
 * so you do not, normally, need to define any of these paths. If you
 * have a really strange setup you can either define paths here or
 * use the run time path-* options.
 */
#if 0
/*
 * Diald needs to use some external binaries to set up
 * routing tables and to bring up the proxy device. If
 * you do not define the paths here diald will look for
 * each program first in /sbin and then in /usr/sbin.
 * If you wish to use a specific binary instead of the
 * defined or search located binary you may use the path-*
 * config options to override them.
 */
#undef PATH_ROUTE	"/sbin/route"
#undef PATH_IFCONFIG	"/sbin/ifconfig"

/*
 * The "ip" program is the preferred way to set routes on Linux 2.2
 * and beyond. Either specify the path here or use the "path-ip"
 * config option. The "ip" program you use needs to understand
 * the "metric" keyword - some older ones do not. You can find
 * "ip" on: ftp://ftp.inr.ac.ru/ip-routing/
 */
#undef PATH_IP		"/usr/sbin/ip"

/*
 * Diald needs to know where to find the bootpc binary in order to
 * use the bootp protocol for dynamic slip address determination.
 */

#undef PATH_BOOTPC	"/usr/sbin/bootpc"

/*
 * If you're never going to use pppd don't worry if this is wrong.
 * Otherwise, find your pppd executable and set this path to match its
 * location.
 */
#undef PATH_PPPD	"/usr/sbin/pppd"
#endif