Slashdot Mirror
Debian Developer Imprisoned In Russia Over Alleged Role In Riots (itwire.com)
An anonymous reader writes:
"Dmitry Bogatov, Debian developer and Tor node admin, is still being held in a Moscow jail," tweeted the EFF Saturday. IT Wire reports that the 25-year-old math teacher was arrested earlier this month "on suspicion of organizing riots," and is expected to be held in custody until June 8. "The panel investigating the protests claims Bogatov posted several incitory messages on the sysadmin.ru forum; for example, one claim said he was asking people to bring 'bottles, fabric, gasoline, turpentine, foam plastic' to Red Square, according to a post at Hacker News. The messages were sent in the name of one Airat Bashirov and happened to be transmitted through the Tor node that Bogatov was running. The Hacker News post said Bogatov's lawyer had produced surveillance video footage to show that he was elsewhere at the time when the messages were posted.
"After Dmitry's arrest," reports the Free Bogatov site, "Airat Bashirov continue to post messages. News outlets 'Open Russia' and 'Mediazona' even got a chance to speak with him."
Earlier this month the Debian GNU/Linux project also posted a message of support, noting Dmitry maintains several packages for command line and system tools, and saying their group "honours his good work and strong dedication to Debian and Free Software... we hope he is back as soon as possible to his endeavours... In the meantime, the Debian Project has taken measures to secure its systems by removing Dmitry's keys in the case that they are compromised."
"After Dmitry's arrest," reports the Free Bogatov site, "Airat Bashirov continue to post messages. News outlets 'Open Russia' and 'Mediazona' even got a chance to speak with him."
Earlier this month the Debian GNU/Linux project also posted a message of support, noting Dmitry maintains several packages for command line and system tools, and saying their group "honours his good work and strong dedication to Debian and Free Software... we hope he is back as soon as possible to his endeavours... In the meantime, the Debian Project has taken measures to secure its systems by removing Dmitry's keys in the case that they are compromised."
This. That fact has made my life a living hell. Before systemd, we could look at /var/log/messages to typically see problems, but now systemd just deletes log messages.
Meanwhile the man they're protesting about, Putin, rigs elections, poisons people with polonium, shoots opposition leaders, throws journalists off buildings....
Are you using Fedora or something? Debian configured systemd to leave /var/log/messages working just the way it always has.
It doesn't actually "drop" them, it just doesn't send them to the syslogs by default. You're supposed to use journalctl to read them! The logging behavior of systemd is a configuration option
All systemd logging can be forwarded to syslog in plain text format, standard feature enabled by a single edit in: /etc/systemd/journald.conf
It can also be enabled on a per boot basis with a simple addition to the kernel boot parameters
ForwardToSyslog=, ForwardToKMsg=, ForwardToConsole=, ForwardToWall=
Control whether log messages received by the journal daemon shall
be forwarded to a traditional syslog daemon, to the kernel log
buffer (kmsg), to the system console, or sent as wall messages to
all logged-in users. These options take boolean arguments. If
forwarding to syslog is enabled but nothing reads messages from the
socket, forwarding to syslog has no effect. By default, only
forwarding to wall is enabled. These settings may be overridden at
boot time with the kernel command line options
"systemd.journald.forward_to_syslog=",
"systemd.journald.forward_to_kmsg=",
"systemd.journald.forward_to_console=", and
"systemd.journald.forward_to_wall=". When forwarding to the
console, the TTY to log to can be changed with TTYPath=, described
below.