# syslog Published articles for syslog. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## journalctl: domina los logs de systemd DevFeed: [journalctl: domina los logs de systemd]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-01T08:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [systemd](), [Boot Process, passwd, systemd]() Tags: [crash](), [logs](), [sysadmins](), [syslog](), [systemd]() ### AI overview A practical guide to using journalctl with systemd. It covers persistent and volatile journals, filtering logs by service, time, and priority, following logs in real time, and reviewing boot and kernel messages. ### Source excerpt Domina journalctl para filtrar logs de systemd por servicio, prioridad y fecha, seguirlos en tiempo real y controlar el espacio que ocupan. ## Transmission: Permission Denied to Downloads directory DevFeed: [Transmission: Permission Denied to Downloads directory]() Original publisher: [Read original article]() Author: Tom Published: 2025-12-26T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Ubuntu](), [configuration](), [bug]() Tags: [apparmor](), [complain-mode](), [configuration](), [downloads-directory](), [how-to](), [localized-folders](), [permission](), [permissions](), [security](), [syslog](), [transmission](), [ubuntu](), [xdg-user-dirs]() ### AI overview A Transmission AppArmor profile on Ubuntu may deny access to localized Downloads directories because it expects English directory names. The article explains how to update the profile with localized paths and restart AppArmor to restore downloads. ### Source excerpt Transmission on Ubuntu may be denied access to localized Downloads directories due to AppArmor profiles expecting English folder names. Here's how to fix it. ## Writing an Async Logger in Nim DevFeed: [Writing an Async Logger in Nim]() Original publisher: [Read original article]() Published: 2016-01-27T23:00:00Z Content type: tutorial Language: en Sources: [Dennis Felsing]() Topics: [Nim](), [Logging](), [async](), [Programming](), [Code](), [Server](), [client]() Tags: [async](), [logging](), [nim](), [programming](), [programming-language](), [syslog](), [terminal]() ### AI overview A step-by-step Nim tutorial that builds an asynchronous logger for a game server and client. It discusses configurable output to files or stdout, non-blocking disk writes, performance, logging formats, compile-time caller information, and existing Nim logger implementations. ### Source excerpt Surprisingly I'm working on HookRace again. I might share a few interesting code snippets and thoughts in this blog along the way. I'm still going with Nim as the programming language. For an easy start let's write a logging module that can be used everywhere in the game's server as well as client. There are mostly three aspects that I care about: Can be configured to write to different files and/or stdout Writes to the disk asynchronously, preventing any blocking when the disk is overloaded Reasonable performance Follow along if you want to witness how fun it is to write code in Nim! Motivation A few logger implementations for Nim already exist: logging: A simple logger in the standard library. Configurable, but no async writing omnilog: An advanced logger with lots of features, no async writing syslog: A bit too high level for my taste and no Windows support We could adapt the logging or omnilog modules to our requirements, mainly by adding async writing. For now let's write our own simple logging module from scratch instead. If it turns out to be usable after a few iterations one might merge it with an existing module. Also, this post would be rather boring if I just ended up using an existing logger. Implementation Let's start with the simplest logger possible: proc log*(text: string) = echo text log "Hello World!" We have a procedure log that is exported (*). It takes a value text of type string and prints this text to the standard output. Super simple and can be used like this from another file (or the same one): import logger log "Hello World!" This simply prints Hello World to the terminal for now when we execute it. We want to keep using the logger in this exact format. Next step: Add a fancy logging format: import strutils, times proc log*(text: string) = echo "[$# $#]: $#" % [getDateStr(), getClockStr(), text] This uses the strutils and times modules from Nim's standard library. The % operator formats the string "[$# $#]: $#" with a date, clock and our te ## clogger(1) -- a campfire logger DevFeed: [clogger(1) -- a campfire logger]() Original publisher: [Read original article]() Published: 2013-11-15T18:24:12Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [Logging](), [Messaging]() Tags: [command](), [interface](), [logger](), [messages](), [simple](), [syslog]() ### AI overview clogger(1) is a simple logging and messaging interface analogous to the common logger(1) command. It sends messages to Campfire instead of syslog(3). ### Source excerpt clogger(1) implements a simple logging/messaging interface analogous to the common logger(1) command. However, instead of logging messages to syslog(3), clogger(1) will write the message to Campfire. ## Ochrona usług przed atakami brute force z fail2ban'em DevFeed: [Ochrona usług przed atakami brute force z fail2ban'em]() Original publisher: [Read original article]() Author: Tom Published: 2011-10-03T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [Fail2ban](), [Logging](), [ssh]() Tags: [admin](), [apache](), [debian](), [fail2ban](), [linux](), [postfix](), [sasl](), [security](), [spam](), [ssh](), [syslog]() ### AI overview This Polish article explains how Fail2ban can monitor authentication failures in syslog and protect publicly accessible services from brute-force attacks and other abusive activity. It discusses basic configuration, supported services, modular filters and actions, performance considerations, and installation on Debian. ### Source excerpt Bardzo często konfigurując usługi dostępne publicznie poświęca się sporo czasu na maksymalne zwiększenie bezpieczeństwa przez "dopieszczanie" konfiguracji (certyfikaty z mocnym szyfrowaniem, ochronę pewnych stron hasłem, dostęp do SSH tylko kluczami, itd.) ale całkowicie pomija się przygotowanie systemu aktywnie monitorującego błędne próby autoryzacji. Oczywiście nie można umniejszać wagi pierwszego z wymienionych etapów ale zdecydowanie nie powinno pomijać się też tego drugiego. Przecież każdy admin chciałby wiedzieć gdy ktoś próbuje włamać się na jego serwer (FTP, HTTP, SSH, itp.) - tylko ilu z Nas zadaje sobie trud by uruchomić taki system? ## Syslog Howto DevFeed: [Syslog Howto]() Original publisher: [Read original article]() Published: 2011-07-08T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [Logging](), [Command-line interface](), [Scripting, bash](), [C]() Tags: [bash](), [c](), [command-line](), [howto](), [logging](), [syslog]() ### AI overview A practical introduction to syslog that explains its role as a standard for logging program messages, including storing events in log files and writing messages from the command line, Bash scripts, and C programs. ### Source excerpt I build software products and write on the Internet.