clients/, disobedience/: Add `-u' option to override user config file.
[disorder] / doc / disorder_config.5.in
... / ...
CommitLineData
1.\"
2.\" Copyright (C) 2004-2011, 2013 Richard Kettlewell
3.\"
4.\" This program is free software: you can redistribute it and/or modify
5.\" it under the terms of the GNU General Public License as published by
6.\" the Free Software Foundation, either version 3 of the License, or
7.\" (at your option) any later version.
8.\"
9.\" This program is distributed in the hope that it will be useful,
10.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
11.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12.\" GNU General Public License for more details.
13.\"
14.\" You should have received a copy of the GNU General Public License
15.\" along with this program. If not, see <http://www.gnu.org/licenses/>.
16.\"
17.TH disorder_config 5
18.SH NAME
19pkgconfdir/config - DisOrder jukebox configuration
20.SH DESCRIPTION
21The purpose of DisOrder is to organize and play digital audio files, under the
22control of multiple users.
23\fIpkgconfdir/config\fR is the primary configuration file; the web interface
24uses a number of others (see \fBdisorder.cgi\fR(8)).
25.SS Tracks
26DisOrder can be configured with multiple collections of tracks, indexing them
27by their filename, and picking players on the basis of filename patterns (for
28instance, "*.mp3").
29.PP
30Although the model is of filenames, it is not inherent that there are
31corresponding real files - merely that they can be interpreted by the chosen
32player.
33See \fBdisorder\fR(3) for more details about this.
34.PP
35Each track can have a set of preferences associated with it.
36These are simple key-value pairs; they can be used for anything you
37like, but a number of keys have specific meanings.
38See \fBdisorder_preferences\fR(5) for more details about these.
39.SS "Track Names"
40Track names are derived from filenames under the control of regular
41expressions, rather than attempting to interpret format-specific embedded name
42information.
43They can be overridden by setting preferences.
44.PP
45Names for display are distinguished from names for sorting, so with the right
46underlying filenames an album can be displayed in its original order even if
47the displayed track titles are not lexically sorted.
48.SS "Server State"
49A collection of global preferences define various bits of server state: whether
50random play is enabled, what tags to check for when picking at random, etc.
51See \fBdisorder_preferences\fR(5) for more information.
52.SS "Users And Access Control"
53DisOrder distinguishes between multiple users.
54This is for access control and reporting, not to provide different
55views of the world: i.e. preferences and so on are global.
56.PP
57Each user has an associated set of rights which control which commands they may
58execute.
59Normally you would give all users most rights, and expect them to
60cooperate (they are after all presumed to be in a shared sound environment).
61.PP
62The full set of rights are:
63.TP
64.B read
65User can perform read-only operations
66.TP
67.B play
68User can add tracks to the queue
69.TP
70.B "move any"
71User can move any track
72.TP
73.B "move mine"
74User can move their own tracks
75.TP
76.B "move random"
77User can move randomly chosen tracks
78.TP
79.B "remove any"
80User can remove any track
81.TP
82.B "remove mine"
83User can remove their own tracks
84.TP
85.B "remove random"
86User can remove randomly chosen tracks
87.TP
88.B "scratch any"
89User can scratch any track
90.TP
91.B "scratch mine"
92User can scratch their own tracks
93.TP
94.B "scratch random"
95User can scratch randomly chosen tracks
96.TP
97.B volume
98User can change the volume
99.TP
100.B admin
101User can perform admin operations
102.TP
103.B rescan
104User can initiate a rescan
105.TP
106.B register
107User can register new users.
108Normally only the
109.B guest
110user would have this right.
111.TP
112.B userinfo
113User can edit their own userinfo
114.TP
115.B prefs
116User can modify track preferences
117.TP
118.B "global prefs"
119User can modify global preferences
120.TP
121.B pause
122User can pause/resume
123.PP
124Access control is entirely used-based.
125If you configure DisOrder to listen for TCP/IP connections then it will
126accept a connection from anywhere provided the right password is
127available.
128Passwords are never transmitted over TCP/IP connections in clear,
129but everything else is.
130The expected model is that host-based access control is imposed at
131the network layer.
132.SS "Web Interface"
133The web interface is controlled by a collection of template files, one for each
134kind of page, and a collection of option files.
135These are split up and separate from the main configuration file to
136.PP
137See \fBdisorder.cgi\fR(8) for more information.
138.SS "Searching And Tags"
139Search strings contain a list of search terms separated by spaces.
140A search term can either be a single word or a tag, prefixed with "tag:".
141.PP
142Search words are compared without regard to letter case or accents; thus, all
143of the following will be considered to be equal to one another:
144.PP
145.nf
146 LATIN CAPITAL LETTER E
147 LATIN SMALL LETTER E
148 LATIN CAPITAL LETTER E WITH GRAVE
149 LATIN SMALL LETTER E WITH GRAVE
150 LATIN CAPITAL LETTER E plus COMBINING GRAVE ACCENT
151 LATIN SMALL LETTER E plus COMBINING GRAVE ACCENT
152.fi
153.PP
154The same rules apply to tags but in addition leading and trailing whitespace is
155disregarded and all whitespace sequences are treated as equal when they appear
156as internal whitespace.
157.PP
158Where several tags are listed, for instance the tags preference for a track,
159the tags are separated by commas.
160Therefore tags may not contain commas.
161.SH "CONFIGURATION FILE"
162.SS "General Syntax"
163Lines are split into fields separated by whitespace (space, tab, line
164feed, carriage return, form feed).
165Comments are started by the number sign ("#").
166.PP
167Fields may be unquoted (in which case they may not contain spaces and
168may not start with a quotation mark or apostrophe) or quoted by either
169quotation marks or apostrophes.
170Inside quoted fields every character stands for itself, except that
171a backslash can only appear as part of one of the following escape sequences:
172.TP
173.B \e\e
174Backslash
175.TP
176.B \e"
177Quotation mark
178.\" "
179.TP
180.B \e\(aq
181Apostrophe
182.TP
183.B \en
184Line feed
185.PP
186No other escape sequences are allowed.
187.PP
188Within any line the first field is a configuration command and any
189further fields are parameters.
190Lines with no fields are ignored.
191.PP
192After editing the config file use \fBdisorder reconfigure\fR to make
193it re-read it.
194If there is anything wrong with it the daemon will record a log
195message and ignore the new config file.
196(You should fix it before next terminating and restarting the daemon,
197as it cannot start up without a valid config file.)
198.SS "Configuration Files"
199Configuration files are read in the following order:
200.TP
201.I pkgconfdir/config
202Or
203.BR $DISORDER_CONFIG ,
204if that's set; overridden by
205.B \-c
206.RB ( \-\-config )
207command line option, except in
208.BR disrder-playrtp (1),
209which uses
210.BR \-C .
211.TP
212.I pkgconfdir/config.private
213Or
214.BR $DISORDER_PRIVCONFIG ,
215if that's set, else
216.BR $DISORDER_CONFIG.private .
217Should be readable only by the jukebox group.
218Not really useful any more and will be abolished in future.
219.TP
220.I ~\fRUSERNAME\fI/.disorder/passwd
221Or
222.BR $DISORDER_USERCONFIG ,
223if that's set; else
224.BR $DISORDER_HOME/passwd ;
225overridden by
226.B \-u
227.RB ( \-\-user-config )
228command-line option.
229Per-user client configuration.
230Optional but if it exists must be readable only by the relevant user.
231Would normally contain a \fBpassword\fR directive.
232.TP
233.I pkgconfdir/config.\fRUSERNAME
234(Or
235.BR $DISORDER_USERCONFIG_SYS ,
236if that's set; else
237.BR $DISORDER_CONFIG.\fIUSERNAME .)
238Per-user system-controlled client configuration.
239Optional but if it exists must be readable only by the relevant user.
240Would normally contain a \fBpassword\fR directive.
241.IP
242The prefererred location for per-user passwords is \fI~/.disorder/passwd\fR and
243\fBdisorder authorize\fR writes there now.
244.SS "Global Configuration"
245.TP
246.B home \fIDIRECTORY\fR
247The home directory for state files.
248Defaults to
249.IR pkgstatedir .
250The server will create this directory on startup if it does not exist.
251.IP
252This setting cannot be changed during the lifetime of the server.
253.TP
254.B plugins \fIPATH\fR
255Adds a directory to the plugin path.
256(This is also used by the web interface.)
257.IP
258Plugins are opened the first time they are required and never after,
259so after changing a plugin you must restart the server before it is
260guaranteed to take effect.
261.IP
262If
263.B plugins
264is used without arguments the plugin path is cleared.
265.SS "Server Configuration"
266.TP
267.B alias \fIPATTERN\fR
268Defines the pattern use construct virtual filenames from \fBtrackname_\fR
269preferences.
270.IP
271Most characters stand for themselves, the exception being \fB{\fR which is used
272to insert a track name part in the form \fB{\fIname\fB}\fR or
273\fB{/\fIname\fB}\fR.
274.IP
275The difference is that the first form just inserts the name part while the
276second prefixes it with a \fB/\fR if it is nonempty.
277.IP
278The pattern should not attempt to include the collection root, which is
279automatically included, but should include the proper extension.
280.IP
281The default is \fB{/artist}{/album}{/title}{ext}\fR.
282.IP
283This setting cannot be changed during the lifetime of the server.
284.TP
285.B api \fINAME\fR
286Selects the backend used to play sound and to set the volume.
287The following options are available:
288.RS
289.TP
290.B alsa
291Use the ALSA API.
292This is only available on Linux systems, on which it is the default.
293.TP
294.B coreaudio
295Use Apple Core Audio.
296This only available on OS X systems, on which it is the default.
297.TP
298.B oss
299Use the OSS (/dev/dsp) API.
300Not available on all platforms.
301.TP
302.B command
303Execute a command.
304This is the default if
305.B speaker_command
306is specified, or if no native is available.
307.IP
308You might want to set
309.B pause_mode
310with this backend.
311.TP
312.B rtp
313Transmit audio over the network.
314This is the default if \fBbroadcast\fR is specified.
315You can use
316.BR disorder-playrtp (1)
317to receive and play the resulting stream on Linux and OS X.
318.B network
319is a deprecated synonym for this API.
320.RE
321.TP
322.B authorization_algorithm \fIALGORITHM\fR
323Defines the algorithm used to authenticate clients.
324The valid options are sha1 (the default), sha256, sha384 and sha512.
325See
326.BR disorder_protocol (5)
327for more details.
328.TP
329.B broadcast \fR[\fIFAMILY\fR] \fIADDRESS\fR \fIPORT\fR
330Transmit sound data to \fIADDRESS\fR using UDP port \fIPORT\fR.
331This implies \fBapi rtp\fR.
332.IP
333\fIFAMILY\fR can be \fB-4\fR or \fB-6\fR to force IPv4 or IPv6, if this is not
334implied by \fIADDRESS\fR.
335Note that IPv6 is not currently well tested.
336.IP
337See also \fBmulticast_loop\fR and \fBmulticast_ttl\fR.
338.TP
339.B broadcast_from \fR[\fIFAMILY\fR] \fIADDRESS\fR \fIPORT\fR
340Sets the (local) source address used by \fBbroadcast\fR.
341.IP
342\fIFAMILY\fR can be \fB-4\fR or \fB-6\fR to force IPv4 or IPv6, if this is not
343implied by \fIADDRESS\fR.
344Note that IPv6 is not currently well tested.
345.TP
346.B channel \fICHANNEL\fR
347The mixer channel that the volume control should use.
348.IP
349For \fBapi oss\fR the possible values are:
350.RS
351.TP 8
352.B pcm
353Output level for the audio device.
354This is probably what you want and is the default.
355.TP
356.B speaker
357Output level for the PC speaker, if that is connected to the sound card.
358.TP
359.B pcm2
360Output level for alternative codec device.
361.TP
362.B vol
363Master output level.
364The OSS documentation recommends against using this, as it affects all
365output devices.
366.RE
367.IP
368You can also specify channels by number, if you know the right value.
369.IP
370For \fBapi alsa\fR, this is the name of the mixer control to use.
371The default is \fBPCM\fR.
372Use \fBamixer scontrols\fR or similar to get a full list.
373.IP
374For \fBapi coreaudio\fR, volume setting is not currently supported.
375.TP
376.B collection \fIMODULE\fR \fIENCODING\fR \fIROOT\fR
377.TP
378.B collection \fIMODULE\fR \fIROOT\fR
379.TP
380.B collection \fIROOT\fR
381Define a collection of tracks.
382.IP
383\fIMODULE\fR defines which plugin module should be used for this
384collection.
385Use the supplied \fBfs\fR module for tracks that exist as ordinary
386files in the filesystem.
387If no \fIMODULE\fR is specified then \fBfs\fR is assumed.
388.IP
389\fIENCODING\fR defines the encoding of filenames in this collection.
390For \fBfs\fR this would be the encoding you use for filenames.
391Examples might be \fBiso\-8859\-1\fR or \fButf\-8\fR.
392If no encoding is specified then the current locale's character encoding
393is used.
394.IP
395NB that this default depends on the locale the server runs in, which is not
396necessarily the same as that of ordinary users, depending how the system is
397configured.
398It's best to explicitly specify it to be certain.
399.IP
400\fIROOT\fR is the root in the filesystem of the filenames and is
401passed to the plugin module.
402It must be an absolute path and should not end with a "/".
403.TP
404.B cookie_key_lifetime \fISECONDS\fR
405Lifetime of the signing key used in constructing cookies. The default is one
406week.
407.IP
408If this is changed during the lifetime of the server, the current key doesn't
409hvave its lifetime retroactively changed.
410.TP
411.B cookie_login_lifetime \fISECONDS\fR
412Lifetime of a cookie enforced by the server. When the cookie expires the user
413will have to log in again even if their browser has remembered the cookie that
414long. The default is one day.
415.IP
416If this is changed during the lifetime of the server, cookies that have already
417een generated don't hvave their lifetime retroactively changed.
418.TP
419.B default_rights \fIRIGHTS\fR
420Defines the set of rights given to new users.
421The argument is a comma-separated list of rights.
422For the possible values see
423.B "Users And Access Control"
424above.
425.IP
426The default is to allow everything except \fBadmin\fR and \fBregister\fR.
427.TP
428.B device \fINAME\fR
429Sound output device.
430.IP
431For \fBapi oss\fR this is the path to the device to use.
432If it is set to \fBdefault\fR then \fI/dev/dsp\fR and \fI/dev/audio\fR
433will be tried.
434.IP
435For \fBapi alsa\fR this is the device name to use.
436.IP
437For \fBapi coreaudio\fR this can be either the UID or the human-readable
438name of the desired device.
439For a list of names, visit System Preferences -> Sound and look at the Type column.
440For example, you might use "Built-in Output" for the built-in speaker
441or "Built-in Line Output" if you have connected external speakers.
442Remember to quote the name.
443.IP
444The default is \fBdefault\fR, which is intended to map to whatever the system's
445default is.
446.TP
447.B history \fIINTEGER\fR
448Specifies the number of recently played tracks to remember (including
449failed tracks and scratches).
450.IP
451If this is changed during the lifetime of the server, it won't actually reduce
452the size of the list until it is next modified.
453.TP
454.B listen \fR[\fIFAMILY\fR] \fR[\fIHOST\fR] \fISERVICE\fR
455Listen for connections on the address specified by \fIHOST\fR and port
456specified by \fISERVICE\fR.
457If \fIHOST\fR is omitted, or is \fB*\fR, then listens on all local addresses.
458.IP
459\fIFAMILY\fR can be \fB-4\fR or \fB-6\fR to force IPv4 or IPv6, if this is not
460implied by \fIHOST\fR.
461Note that IPv6 is not currently well tested.
462.IP
463Normally the server only listens on a UNIX domain socket.
464.TP
465.B mixer \fIDEVICE\fR
466The mixer device name, if it needs to be specified separately from
467\fBdevice\fR.
468.IP
469For \fBapi oss\fR this should be the path to the mixer device and the default
470is \fI/dev/mixer\fR.
471.IP
472For \fBapi alsa\fR, this is the index of the mixer control to use.
473The default is 0.
474.IP
475For \fBapi coreaudio\fR, volume setting is not currently supported.
476.TP
477.B mount_rescan yes\fR|\fBno
478Determines whether mounts and unmounts will cause an automatic rescan.
479The default is \fByes\fR.
480.TP
481.B multicast_loop yes\fR|\fBno
482Determines whether multicast packets are loop backed to the sending host.
483The default is \fByes\fR.
484This only applies if \fBapi\fR is set to \fBrtp\fR and \fBbroadcast\fR
485is actually a multicast address.
486.TP
487.B multicast_ttl \fIHOPS\fR
488Set the maximum number of hops to send multicast packets.
489This only applies if \fBapi\fR is set to \fBrtp\fR and
490\fBbroadcast\fR is actually a multicast address.
491The default is 1.
492.TP
493.B namepart \fIPART\fR \fIREGEXP\fR \fISUBST\fR [\fICONTEXT\fR [\fIREFLAGS\fR]]
494Determines how to extract trackname part \fIPART\fR from a
495track name (with the collection root part removed).
496Used in \fB@recent@\fR, \fB@playing@\fR and \fB@search@\fR.
497.IP
498Track names can be different in different contexts.
499For instance the sort string might include an initial track number,
500but this would be stripped for the display string.
501\fICONTEXT\fR should be a glob pattern matching the
502contexts in which this directive will be used.
503.IP
504Valid contexts are \fBsort\fR and \fBdisplay\fR.
505.IP
506All the \fBnamepart\fR directives are considered in order.
507The first directive for the right part, that matches the desired context,
508and with a \fIREGEXP\fR that
509matches the track is used, and the value chosen is constructed from
510\fISUBST\fR according to the substitution rules below.
511.IP
512Note that searches use the raw track name and \fBtrackname_\fR preferences but
513not (currently) the results of \fBnamepart\fR, so generating words via this option
514that aren't in the original track name will lead to confusing results.
515.IP
516If you supply no \fBnamepart\fR directives at all then a default set will be
517supplied automatically.
518But if you supply even one then you must supply all of them.
519The defaults are equivalent to:
520.PP
521.nf
522namepart title "/([0-9]+ *[-:] *)?([^/]+)\\.[a-zA-Z0-9]+$" $2 display
523namepart title "/([^/]+)\\.[a-zA-Z0-9]+$" $1 sort
524namepart album "/([^/]+)/[^/]+$" $1 *
525namepart artist "/([^/]+)/[^/]+/[^/]+$" $1 *
526namepart ext "(\\.[a-zA-Z0-9]+)$" $1 *
527.fi
528.IP
529This setting cannot be changed during the lifetime of the server.
530.TP
531.B new_bias \fIWEIGHT\fR
532The weight for new tracks.
533The default is 450000, i.e. recently added tracks are a fifty times as likely
534to be picked as normal.
535.IP
536New values of this option may be picked up from the configuration file even
537without a reload.
538.TP
539.B new_bias_age \fISECONDS\fR
540The maximum age of tracks that \fBnew_bias\fR applies to, in seconds.
541The default is one week.
542.IP
543New values of this option may be picked up from the configuration file even
544without a reload.
545.TP
546.B new_max \fIMAX\fR
547The maximum number of tracks to list when reporting newly noticed tracks.
548The default is 100.
549.TP
550.B nice_rescan \fIPRIORITY\fR
551Set the recan subprocess priority.
552The default is 10.
553.IP
554(Note that higher values mean the process gets less CPU time; UNIX priority
555values are backwards.)
556.TP
557.B nice_server \fIPRIORITY\fR
558Set the server priority.
559This is applied to the server at startup time (and not when you reload
560configuration).
561The server does not use much CPU itself but this value is inherited
562by programs it executes.
563If you have limited CPU then it might help to set this to a small
564negative value.
565The default is 0.
566.IP
567Changes to this value during the lifetime of the server are ignored.
568.TP
569.B nice_speaker \fIPRIORITY\fR
570Set the speaker process priority.
571This is applied to the speaker process at startup time (and not when
572you reload the configuration).
573The speaker process is not massively CPU intensive by today's
574standards but depends on reasonably timely scheduling.
575If you have limited CPU then it might help to set this to a small
576negative value.
577The default is 0.
578.IP
579Changes to this value during the lifetime of the server are ignored.
580.TP
581.B noticed_history
582The maximum days that a track can survive in the database of newly added
583tracks.
584The default is 31.
585.TP
586.B pause_mode \fIMODE
587Sets the pause mode for the \fBcommand\fR backend.
588The possible values are:
589.RS
590.TP
591.B silence
592Send silent (0-value) samples when paused.
593This is the default.
594.TP
595.B suspend
596Stop writing when paused.
597.RE
598.TP
599.B player \fIPATTERN\fR \fIMODULE\fR [\fIOPTIONS.. [\fB\-\-\fR]] \fIARGS\fR...
600Specifies the player for files matching the glob \fIPATTERN\fR.
601\fIMODULE\fR specifies which plugin module to use.
602.IP
603The following options are supported:
604.RS
605.TP
606.B \-\-
607Defines the end of the list of options.
608Needed if the first argument to the plugin starts with a "\-".
609.RE
610.IP
611The following are the standard modules:
612.RS
613.TP
614.B exec \fICOMMAND\fR \fIARGS\fR...
615The command is executed via \fBexecvp\fR(3), not via the shell.
616The \fBPATH\fR environment variable is searched for the executable if it is not
617an absolute path.
618The command is expected to know how to open its own sound device.
619.TP
620.B execraw \fICOMMAND\fR \fIARGS\fR...
621Identical to the \fBexec\fR except that the player is expected to use the
622DisOrder raw player protocol.
623.BR disorder-decode (8)
624can decode several common audio file formats to this format.
625.TP
626.B shell \fR[\fISHELL\fR] \fICOMMAND\fR
627The command is executed using the shell.
628If \fISHELL\fR is specified then that is used, otherwise \fBsh\fR will be used.
629In either case the \fBPATH\fR environment variable is searched for the shell
630executable if it is not an absolute path.
631The track name is stored in the environment variable
632\fBTRACK\fR.
633.IP
634Be careful of the interaction between the configuration file quoting rules and
635the shell quoting rules.
636.RE
637.IP
638If multiple player commands match a track then the first match is used.
639.IP
640For the server to be able to calculate track lengths, there should be a
641.B tracklength
642command corresponding to each
643.B player
644command.
645.IP
646If
647.B player
648is used without arguments, the list of players is cleared.
649.IP
650Although players can be changed during the lifetime of the server, note that
651background decoders will not be stopped and restarted using changed
652configuration once they have been started.
653.TP
654.B queue_pad \fICOUNT\fR
655The target size of the queue.
656If random play is enabled then randomly picked tracks will be added until
657the queue is at least this big.
658The default is 10.
659.IP
660If this is reduced during the lifetime of the server, the queue won't be
661reduced in size to fit; it just won't start growing again until it is under the
662new value.
663However, if it is increased, new tracks will start being added immediately.
664.TP
665.B reminder_interval \fISECONDS\fR
666The minimum number of seconds that must elapse between password reminders.
667The default is 600, i.e. 10 minutes.
668.TP
669.B remote_userman yes\fR|\fBno
670User management over TCP connection is only allowed if this is set to
671\fByes\fR. By default it is set to \fBno\fR.
672.TP
673.B replay_min \fISECONDS\fR
674The minimum number of seconds that must elapse after a track has been played
675before it can be picked at random. The default is 8 hours. If this is set to
6760 then there is no limit, though current \fBdisorder-choose\fR will not pick
677anything currently listed in the recently-played list.
678.IP
679New values of this option may be picked up from the configuration file even
680without a reload.
681.TP
682.B rtp_always_request yes\fR|\fBno
683If
684.B yes
685then
686.BR disorder-playrtp (1)
687will always request a dedicated RTP stream,
688rather than contacting the server to discover
689a broadcast or multicast address.
690(This behaviour can be overridden by
691setting a suitable address on the command-line.)
692The default is
693.BR no .
694.IP
695This option is experimental,
696and may change or be removed in a future release.
697.TP
698.B rtp_maxbuffer \fIFRAMES\fR
699Set
700.BR disorder-playrtp (1)'s
701buffer size to the given number of
702.IR FRAMES .
703If this is zero, then
704.B disorder-playrtp
705will select a default buffer size.
706(This setting can be overridden by passing
707a suitable command-line option.)
708The default value is
709.BR 0 .
710.IP
711This option is experimental,
712and may change or be removed in a future release.
713.TP
714.B rtp_max_payload \fBYTES\fR
715Don't send RTP packets with a UDP payload larger than
716.I BYTES
717(including the 12-byte RTP header). If you know that you will be transmitting
718RTP over networks with an unusually low MTU size, then it is probably useful to
719set this option.
720.IP
721This option is experimental,
722and may change or be removed in a future release.
723.TP
724.B rtp_minbuffer \fIFRAMES\fR
725Set
726.BR disorder-playrtp (1)'s
727buffer low-water-mark to the given number of
728.IR FRAMES .
729If this is zero, then
730.B disorder-playrtp
731will select a default low-water-mark.
732(This setting can be overridden by passing
733a suitable command-line option.)
734.IP
735This option is experimental,
736and may change or be removed in a future release.
737The default value is
738.BR 0 .
739.IP
740This option is experimental, and may change or be removed in a future release.
741.TP
742.B rtp_mode \fIMODE\fR
743The network transmission mode for the \fBrtp\fR backend.
744Possible values are:
745.RS
746.TP
747.B unicast
748Unicast transmission to the address given by \fBbroadcast\fR.
749.TP
750.B broadcast
751Broadcast transmission to the address given by \fBbroadcast\fR.
752.TP
753.B multicast
754Multicast transmission to the address given by \fBbroadcast\fR.
755.TP
756.B request
757Unicast transmission to addresses requested by clients.
758.TP
759.B auto
760Choose one of the above based on the destination address.
761This is the default, for backwards compatibility reasons.
762.RE
763.TP
764.B rtp_mtu_discovery \fIOPTION\fR
765Control whether the system attemps path-MTU discovery using RTP packets
766transmitted over IPv4. (This is not configurable in IPv6.) Possible values
767are:
768.RS
769.TP
770.B default
771Do whatever the kernel usually does with UDP packets. This is, err, the
772default.
773.TP
774.B yes
775Force path-MTU disocvery. The `don't fragment' bit is set on outgoing packets
776and we assume that the kernel will handle ICMP `fragmentation needed' errors
777coming back and fragment accordingly.
778.TP
779.B no
780Disable path-MTU discovery. Packets will be sent without the `don't fragment'
781bit, and routers will be expected to fragment packets as necessary.
782.RE
783.IP
784This option is experimental, and may change or be removed in a future release.
785.TP
786.B rtp_rcvbuf \fISIZE\fR
787Set
788.BR disorder-playrtp (1)'s
789socket receive buffer to at least
790.IB SIZE .
791(This setting can be overridden by passing
792a suitable command-line option.)
793The default value is
794.BR 0 .
795.IP
796This option is experimental,
797and may change or be removed in a future release.
798.TP
799.B rtp_request_address \fR[\fIFAMILY\fR] \fR[\fIHOST\fR] \fISERVICE\fR
800If
801.BR disorder-playrtp (1)
802is to request a unicast RTP stream,
803then it should establish its receiving socket
804to listen on the given address.
805The
806.I FAMILY
807and
808.I HOST
809may be omitted, in which case
810.B disorder-playrtp
811uses heuristics to determine suitable values.
812The
813.I PORT
814may be omitted, in which case
815.B disorder-playrtp
816uses a kernel-allocated port.
817(This setting can be overridden by passing
818a suitable address on the command line.)
819The default is
820.RB ` "\- 0" ',
821which uses a heuristically-chosen address and a kernel-allocated port.
822.IP
823This option is experimental,
824and may change or be removed in a future release.
825.TP
826.B sample_format \fIBITS\fB/\fIRATE\fB/\fICHANNELS
827Describes the sample format expected by the \fBspeaker_command\fR (below).
828The components of the format specification are as follows:
829.RS
830.TP 10
831.I BITS
832The number of bits per sample.
833Optionally, may be suffixed by \fBb\fR or \fBl\fR for big-endian and
834little-endian words.
835If neither is used the native byte order is assumed.
836.TP
837.I RATE
838The number of samples per second.
839.TP
840.I CHANNELS
841The number of channels.
842.PP
843The default is
844.BR 16/44100/2 .
845.PP
846With the
847.B rtp
848backend the sample format is forced to
849.B 16b/44100/2
850and with the
851.B coreaudio
852backend it is forced to
853.BR 16/44100/2 ,
854in both cases regardless of what is specified in the configuration file.
855.RE
856.TP
857.B signal \fINAME\fR
858Defines the signal to be sent to track player process groups when tracks are
859scratched.
860The default is \fBSIGKILL\fR.
861.IP
862Signals are specified by their full C name, i.e. \fBSIGINT\fR and not \fBINT\fR
863or \fBInterrupted\fR or whatever.
864.TP
865.B sox_generation \fB0\fR|\fB1
866Determines whether calls to \fBsox\fR(1) should use \fB\-b\fR, \fB\-x\fR, etc (if
867the generation is 0) or \fB\-\fIbits\fR, \fB\-L\fR etc (if it is 1).
868See the documentation for your installed copy of \fBsox\fR to determine
869which you need.
870The default is set according to the version of sox found when DisOrder was
871built.
872If you run on a system with a different version of sox, you will need to
873set this option.
874.TP
875.B speaker_backend \fINAME
876This is an alias for \fBapi\fR; see above.
877.TP
878.B speaker_command \fICOMMAND
879Causes the speaker subprocess to pipe audio data into shell command
880\fICOMMAND\fR, rather than writing to a local sound card.
881The sample format is determine by
882.B sample_format
883above.
884.IP
885Note that if the sample format is wrong then
886.BR sox (1)
887is invoked to translate it.
888If
889.B sox
890is not installed then this will not work.
891.TP
892.B scratch \fIPATH\fR
893Specifies a scratch.
894When a track is scratched, a scratch track is played at random.
895Scratches are played using the same logic as other tracks.
896.IP
897At least for the time being, path names of scratches must be encoded using
898UTF-8 (which means that ASCII will do).
899.IP
900If \fBscratch\fR is used without arguments then the list of scratches is
901cleared.
902.TP
903.B stopword \fIWORD\fR ...
904Specifies one or more stopwords that should not take part in searches
905over track names.
906.IP
907If \fBstopword\fR is used without arguments then the list of stopwords is
908cleared.
909.IP
910There is a default set of stopwords built in, but this option can be used to
911augment or replace that list.
912.IP
913This setting cannot be changed during the lifetime of the server.
914.TP
915.B tracklength \fIPATTERN\fR \fIMODULE\fR
916Specifies the module used to calculate the length of files matching
917\fIPATTERN\fR.
918\fIMODULE\fR specifies which plugin module to use.
919.IP
920If \fBtracklength\fR is used without arguments then the list of modules is
921cleared.
922.IP
923Track lengths are cached in the database, and changing this setting won't cause
924them to be regenerated.
925.TP
926.B user \fIUSERNAME\fR
927Specifies the user to run as.
928Only makes sense if invoked as root (or the target user).
929.IP
930This setting cannot be changed during the lifetime of the server
931(and if it is changed with a restart, you will need to adjust file permissions
932on the server's database).
933.SS "Client Configuration"
934These options would normally be used in \fI~\fRUSERNAME\fI/.disorder/passwd\fR
935or
936\fIpkgconfdir/config.\fRUSERNAME.
937.TP
938.B connect \fR[\fIFAMILY\fR] \fIHOST SERVICE\fR
939Connect to the address specified by \fIHOST\fR and port specified by
940\fISERVICE\fR.
941.IP
942\fIFAMILY\fR can be \fB-4\fR or \fB-6\fR to force IPv4 or IPv6, if this is not
943implied by \fIHOST\fR.
944Note that IPv6 is not currently well tested.
945.TP
946.B password \fIPASSWORD\fR
947Specify password.
948.TP
949.B username \fIUSERNAME\fR
950Specify username.
951The default is inferred from the current UID.
952.SS "Web Interface Configuration"
953.\" TODO this section is misnamed really...
954.TP
955.B mail_sender \fIADDRESS\fR
956The email address that appears in the From: field of any mail messages sent by
957the web interface.
958This must be set if you have online registration enabled.
959.TP
960.B refresh \fISECONDS\fR
961Specifies the maximum refresh period in seconds.
962The refresh period is the time after which the web interface's queue and manage
963pages will automatically reload themselves.
964Default 15.
965.TP
966.B refresh_min \fISECONDS\fR
967Specifies the minimum refresh period in seconds.
968Default 1.
969.TP
970.B sendmail \fIPATH\fR
971The path to the Sendmail executable.
972This must support the \fB-bs\fR option (Postfix, Exim and Sendmail should all
973work).
974The default is the sendmail executable found at compile time.
975.TP
976.B short_display \fICHARACTERS\fR
977Defines the maximum number of characters to include in a \fBshort\fR name
978part.
979Default 30.
980.TP
981.B smtp_server \fIHOSTNAME\fR
982The hostname (or address) of the SMTP server to use for sending mail.
983The default is 127.0.0.1.
984If \fBsendmail\fR is set then that is used instead.
985.TP
986.B transform \fITYPE\fR \fIREGEXP\fR \fISUBST\fR [\fICONTEXT\fR [\fIREFLAGS\fR]]
987Determines how names are sorted and displayed in track choice displays.
988.IP
989\fITYPE\fR is the type of transformation; usually \fBtrack\fR or
990\fBdir\fR but you can define your own.
991.IP
992\fICONTEXT\fR is a glob pattern matching the context.
993Standard contexts are \fBsort\fR (which determines how directory names
994are sorted) and \fBdisplay\fR (which determines how they are displayed).
995Again, you can define your own.
996.IP
997All the \fBtransform\fR directives are considered in order.
998If the \fITYPE\fR, \fIREGEXP\fR and the \fICONTEXT\fR match
999then a new track name is constructed from
1000\fISUBST\fR according to the substitution rules below.
1001If several match then each is executed in order.
1002.IP
1003If you supply no \fBtransform\fR directives at all then a default set will be
1004supplied automatically.
1005But if you supply even one then you must supply all of them.
1006The defaults are:
1007.PP
1008.nf
1009transform track "^.*/([0-9]+ *[-:] *)?([^/]+)\\.[a-zA-Z0-9]+$" $2 display
1010transform track "^.*/([^/]+)\\.[a-zA-Z0-9]+$" $1 sort
1011transform dir "^.*/([^/]+)$" $1 *
1012transform dir "^(the) ([^/]*)" "$2 $1" sort i
1013transform dir "[[:punct:]]" "" sort g
1014.fi
1015.TP
1016.B url \fIURL\fR
1017Specifies the URL of the web interface.
1018This URL will be used in generated web pages.
1019The default is inferred at runtime, so this option no
1020longer needs to be specified.
1021.IP
1022This must be the full URL, e.g. \fBhttp://myhost/cgi-bin/jukebox\fR and not
1023\fB/cgi-bin/jukebox\fR.
1024.SH "REGEXP SUBSTITUTION RULES"
1025Regexps are PCRE regexps, as defined in \fBpcrepattern\fR(3).
1026The only option used is \fBPCRE_UTF8\fR.
1027Remember that the configuration file syntax means you have to
1028escape backslashes and quotes inside quoted strings.
1029.PP
1030In a \fISUBST\fR string the following sequences are interpreted
1031specially:
1032.TP
1033.B $1 \fR... \fB$9
1034These expand to the first to ninth bracketed subexpression.
1035.TP
1036.B $&
1037This expands to the matched part of the subject string.
1038.TP
1039.B $$
1040This expands to a single \fB$\fR symbol.
1041.PP
1042All other pairs starting with \fB$\fR are undefined (and might be used
1043for something else in the future, so don't rely on the current
1044behaviour.)
1045.PP
1046If \fBi\fR is present in \fIREFLAGS\fR then the match is case-independent.
1047If \fBg\fR is present then all matches are replaced, otherwise only the first
1048match is replaced.
1049.SH "TRACK NAME PARTS"
1050The traditional track name parts are \fBartist\fR, \fBalbum\fR and \fBtitle\fR,
1051with the obvious intended meaning.
1052These are controlled by configuration and by \fBtrackname_\fR preferences.
1053.PP
1054In addition there are two built-in parts, \fBpath\fR which is the whole path
1055name and \fBext\fR which is the filename extension, including the initial dot
1056(or the empty string if there is not extension).
1057.SH "SEE ALSO"
1058\fBdisorder\fR(1), \fBsox\fR(1), \fBdisorderd\fR(8), \fBdisorder\-dump\fR(8),
1059\fBpcrepattern\fR(3), \fBdisorder_templates\fR(5), \fBdisorder_actions\fR(5),
1060\fBdisorder.cgi\fR(8), \fBdisorder_preferences\fR(5)
1061.\" Local Variables:
1062.\" mode:nroff
1063.\" fill-column:79
1064.\" End: