blob: 7d89bf625c0125a025b350b310eacf4d5ceaa4f7 (
plain) (
blame)
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
|
Protocol for talking to the log server:
Pure line-based text protocol. Tcp to some port on the log server:
From log daemon (or anything, really) to server:
service <service>
component <service> <component>
state <service> <component> <levels>
This tells the log daemon that service <service> exists, and that it
has a component named <component>.
<levels> syntax:
fatal=forward,error=forward,warning=store,info=store,event=forward,debug=off,spam=off
ie: level=<status>[,...]*
Where <status> is one of:
forward : store and send to log server
store : store locally only (to file)
off : do not even generate the message in the program
From server to whoever is interested:
setstate <service> <component> <levels>
Exactly same syntax. Levels that are not mentioned are not modified.
list services
list components <service>
list states <service> <component>
(list commands are replied to with service/component/state commands).
|
