Hi, Quoting Hilmar Preusse (2023-12-01 23:10:36) > I run sbuild as following: > > sbuild --no-run-lintian --arch-all --dist=sid *.dsc -d unstable-amd64-sbuild > > , where unstable-amd64-sbuild references a chroot. Updating the chroot is > done: > > sudo sbuild-update -udcar unstable-amd64-sbuild > > Both commands generate weird messages in /var/log/syslog like this: > > 2023-12-01T09:36:52.230653+01:00 haka2 schroot[3182]: [unstable- > amd64-sbuild-327cf8c2-30d1-4469-aa7b-9bc3653dbc45 chroot] (root->root) Running > command: "perl -e #012 use strict;#012 > use warnings;#012 use POSIX;#012 <snip> > > Sample file is attached. These #012 are page feed chars IIRC. Unfortunately > logcheck is not able to handle the situation and generates E-Mails, which > report the full command line by line. There is definitely a white list rule > for > schroot in /etc/logcheck/ignore.d.server/schroot, but it is not able to handle > the lot of special characters. Consider to not print the full perl script into > the log file (if possible). > > It may be an issue in logcheck, but rather prefer to avoid message instead of > trying to white list afterwards.
it may also be an issue with schroot, no? I do not think sbuild at any point tells schroot to write anything to syslog. What should sbuild do to fix this? Thanks! cheers, josch
signature.asc
Description: signature
