README.Debian
1logcheck for Debian
2-------------------
3
4Configuration
5~~~~~~~~~~~~~
6Logcheck configuration is done in the file /etc/logcheck/logcheck.conf.
7To change the email address to which reports are sent, change the line:
8 SENDMAILTO="root"
9to:
10 SENDMAILTO="emailaddress@some.domain.tld"
11
12The reportlevel (that is, the degree of filtering applied to "routine" system
13events) can be reduced from the default by changing the line:
14 REPORTLEVEL="server"
15to:
16 REPORTLEVEL="workstation"
17or increased:
18 REPORTLEVEL="paranoid"
19
20Note that "server" includes "paranoid" and "workstation" includes "server"
21(which includes "paranoid").
22
23There are a number of other options which are documented in
24/etc/logcheck/logcheck.conf itself.
25
26By default logcheck is set to run once an hour. This can be changed by editing
27/etc/cron.d/logcheck.
28
29Please note that the permissions of rulefiles installed with
30dh_installlogcheck after installing logcheck will differ from those included
31in logcheck-database. This is because dh_installlogcheck cannot yet assume
32that the logcheck user exists. This may be changed in a future version of
33Debian.
34
35Getting the source/contributing
36~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
37The Debian logcheck package is now maintained with git:
38 https://salsa.debian.org/debian/logcheck.git
39
40Also see: README.source
41
README.source
1Logcheck - git
2
3The logcheck git repository is available via for online browsing:
4<https://salsa.debian.org/debian/logcheck>
5
6To obtain the source, you clone it:
7
8git clone https://salsa.debian.org/debian/logcheck.git
9
10To submit patches, please follow this document:
11<http://repo.or.cz/w/git.git?a=blob;f=Documentation/SubmittingPatches;hb=HEAD>
12
13And send your patches via email to the Debian BTS:
14<https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=logcheck>
15
16First, the setup, which you only have to do once on each machine you work
17with:
18
19# leave out --global if you want to set your identity only for logcheck
20git config --global user.name 'your name'
21git config --global user.email 'your@email.address'
22# the next two are not needed but ensure that git does not send patches to
23# your own email address.
24git config sendemail.signedoffcc false
25git config sendemail.suppressfrom true
26git clone https://salsa.debian.org/debian/logcheck.git
27
28To prepare the actual patch, do the following:
29
30git pull
31git checkout -b some-name-identifying-my-work
32while not finished:
33 // if resuming after a while, maybe update your branch:
34 git rebase master
35 // edit files
36 git add files
37 git commit
38 ...
39end
40
41After you've brought your change to a state where you want to submit it,
42please squash it into logical single commits. If you only made one change,
43then this will do:
44
45git checkout -b temp-squash master
46git merge --squash some-name-identifying-my-work
47git commit // ... remove the "Squashed commit of the following:" leader
48git format-patch -M -s master
49// now inspect the files this created in $PWD
50// check that it's okay and send the patch to Debian BTS
51
52For multiple logical changes, cherry-pick or squash-merge every commit
53belonging to a change to the integration branch and then commit it.
54
55Also, read the git-send-email manpage in case you're submitting multiple
56logical changes, in case you want to thread them.
57
58The manpage also includes information about adding a prologue message
59explaining your patch, or how to insert it into an existing thread
60(in-reply-to).
61
62Developers with write access to the repository may also push their
63changes, using the ssh transport instead of the git protocol.
64