If you want to expand the tests, we can discuss the necessary details. If other systemd files also take this quite simplistic approach we should stay with this and leave it to pglcmd to log errors to pglcmd.log if something else is missing. True, although you could check much more precisely for this (and much other stuff). There are some fixes regarding this in the git repository. The condition "ConditionPathExists=|/etc/pgl/blocklists.list" is not strictly necessary, you can also run pgl with only local blocklists instead (files or links in /etc/pgl/blocklists.local/). Now I had a pedantic look at the systemd file: If you pass "-with-systemdsystemunitdir=/usr/lib/systemd/system/" (or another path) to configure the real systemd file is created and later on installed. Please note that it is a file called systemd.in. The release of 2.2.3 is planned hopefully for next monday, it would be awesome if you could test it before. I just committed your systemd file with complete integration in the build-system to the git repository. I'll make the changes you suggested to the PKGBUILDs. It feels wrong to have this behavior by default. What I need to clarify is whether the network (and possibly timeout) checks are more appropriate in the timer or service file.Īs for my reluctance to implement a hard dependency on network.target, it's born by the fact that it would force a network connection regardless of whether the admin or user wants one. So again and AFAIK, failure of the service is only temporary until another call is placed by the timer. So the retry should happen the next day at the earliest or as soon as the computer is on when the downtime is superior to 24h, just as (ana)cron used to do it (including failures when a connection wasn't established prior to launching the script). It also emulates the anacron functionality to call the service if the system has been down for more than 24 hours. Just like the "old" cron.daily script, the timer is programmed to be called every 24 hours if the system is on. You're absolutely right but remember that there are 2 parts to pgl integration to systemd timer: a service and a timer. > The documentation ("Requisite") says the service will fail and there is no mention of 'retry'. So in case anybody needs this blocklist too there is a link below for downloading.īlocklists included in "full-ascii-blocklist.p2p"
PEERGUARDIAN TABLET HOW TO
So now I suppose the only way is to wait until lists on will be fixed and all non-ASCII symbols will be removed.Īlso if anybody know how to compile PeerGuardian with the support of Unicode please comment the method here.Īs for me I've created manually a common blocklist that includes IP-ranges from the following blocklists presented below and manually deleted all non-ASCII symbolds from it.
PEERGUARDIAN TABLET UPDATE
As it has happened just recently I can suppose that blocklists have been updated on with many non-ASCII symbols and were downloaded as an update after this by PeerGuardian program. WARN: No valid ASCII blocklist format line:Īs I have discovered this happens because of the many non-ASCII symbols like "¬ ® µ ¼ Ñ" and others that appears in blocklist files and that PeerGuardian cannot parse while constructing master blocklist. I have experienced this problem with "no valid ASCII format" recently too ( unzip-natspec) (optional) – for zipped blocklists (optional) – to diagnose connection problems ( femtomail-git, ssmtp-plain, exim-mysql, dma, exim-gnutls, esmtp, sendmail, ssmtp, exim-heavy, courier-mta, exim, msmtp-mta, nullmailer, opensmtpd, postfix) (optional) – to send reports ( p7zip-jinfeihan57-git, p7zip-natspec, 7-zip-full) (optional) – for 7z blocklists ( networkmanager-consolekit, networkmanager-iwd, networkmanager-git) (optional) – to whitelist newly started network interfaces ( net-tools-debian-ifconfig, net-tools-git) (optional) – to whitelist local IP addresses ( zlib-static, zlib-git, zlib-ng, zlib-ng-compat-git) (make) ( systemd-homed-containers, systemd-pr23511, systemd-selinux, systemd-git) ( procps-ng-static, procps-ng-nosystemd-minimal-git, procps-ng-nosystemd, procps-ng-git) ( iptables-nosystemd-minimal-git, iptables-minimal-git, iptables-git, iptables-fullconenat, iptables-fullconenat-nft, iptables-nft) ( dbus-elogind, dbus-git, dbus-nosystemd-minimal-git, dbus-nosystemd, dbus-selinux, dbus-x11, dbus-xdg-docs)
( coreutils-git, coreutils-selinux, coreutils-hybrid, coreutils-hybrid-git)
( bash-devel-git, bash-devel-static-git, bash-git, bash-xdg)
0 kommentar(er)
