Bug#960348: Patch for /lib/systemd/system/logrotate.service

2020-05-11 Thread Tilman Heinrich

Shortly: Solution for preventing from errors by systemd
logrotate.service when running before local file systems are ready.

4a5
> After=local-fs.target


Bug#960348: logrotate: Logrotate.service fails at boottime if dedicated /var is not ready

2020-05-11 Thread Tilman Heinrich
Package: logrotate
Version: 3.14.0-4
Severity: important
Tags: patch

Dear Maintainer,

the logrotate.service failed when started by the systemd under the following 
conditions:
 - There is no graphical target but the system runs to multi-user.target,
 - The system was not started for a few days,
 - The logrotate service was started at boot time, maybe triggered by the 
stand still period,
 - The /var directory is separated to a dedicated md device.

There was no error after manually starting the service at the command line 
when the system was up.

If you don't wish that users will be faced by error messages at boot time it 
would be help to complete the unit description in the file 
/lib/systemd/system/logrotate.service by simply add the following statement 
to the unit section: After=local-fs.target.

This statement is also missing in the unstable package 
logrotate_3.16.0-3_amd64.deb.

Best Regards
T. Heinrich

-- Package-specific info:
Contents of /etc/logrotate.d
total 28
-rw-r--r-- 1 root root 120 Apr 19  2019 alternatives
-rw-r--r-- 1 root root 173 May 28  2019 apt
-rw-r--r-- 1 root root 130 Aug 29  2018 btmp
-rw-r--r-- 1 root root 112 Apr 19  2019 dpkg
-rw-r--r-- 1 root root 501 Feb 26  2019 rsyslog
-rw-r--r-- 1 root root 340 Jul 24  2019 squid
-rw-r--r-- 1 root root 145 Feb 19  2018 wtmp


-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages logrotate depends on:
ii  cron [cron-daemon]  3.0pl1-134+deb10u1
ii  libacl1 2.2.53-4
ii  libc6   2.28-10
ii  libpopt01.16-12
ii  libselinux1 2.8-1+b1
ii  systemd-sysv241-7~deb10u4

Versions of packages logrotate recommends:
pn  bsd-mailx | mailx  

logrotate suggests no packages.

-- no debconf information



Bug#956599: firefox: Prevent search engines from masking ctrl+click for forcing open sites in foreground.

2020-04-13 Thread Tilman Heinrich

Package: firefox
Version: 68.7.0esr~linuxmint1+debbie
Severity: wishlist

Dear Maintainer,

recently my firefox confronted me with a feature which feels like a bug:
Instead of open a search result in a background tab ctrl+click on the result
opens the tab in the foreground. After some investigation of settings and in
about:config I realized that this only happened with the Yahoo search engine
(https://de.search.yahoo.com/). Additionally their site settings don't
distinct
between loading in back- or foreground.

I wonder if there could be a setting which can prevent such
misbehavingwebsites
from idiotically masking the browser settings for opening pages. Until
this is
implemented I simply ban this site from my default engines list.

Best regards
Tilman.



-- System Information:
Debian Release: 9.3
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-12-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information



Bug#956581: Fwd: squid: Starting sdquid by systemd fails when local fs /var is not ready.

2020-04-13 Thread Tilman Heinrich

Package: squid
Version: 4.6-1+deb10u1
Severity: important
Tags: patch

Dear Maintainer,

I installed squid early when I set up a special router. The start
repeatedlyfails by inaccessibility of files at the dedicated /var
partition (dev/md1). The result was a stopped squid service due to a
failed restart.

The first solution was to change the triggered path for restart in
/etc/resolvconf/update-libc.d/squid from /usr/sbin to /var/log. Later I
found that the unit decription in the systemd configuration file
/lib/systemd/system/squid.service is incomlete, because of the omitted
depency for the local-fs.target. So I copied the file to
/etc/systemd/system/squid.service and added the missing depency to the
"After=" statement - this should be the default for the unit description
under /lib/systemd/system/ when started up by systemd.

As long as /var is a local fs and not a remote one this should be
sufficient. I have not tested whether this solution (without the path
change in the updater configuration) eventually doesn't work, like
described in bug report #932593.

Regards Tilman

-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages squid depends on:
ii adduser 3.118
ii libc6 2.28-10
ii libcap2 1:2.25-2
ii libcom-err2 1.44.5-1+deb10u3
ii libdb5.3 5.3.28+dfsg1-0.5
ii libdbi-perl 1.642-1+b1
ii libecap3 1.0.1-3.2
ii libexpat1 2.2.6-2+deb10u1
ii libgcc1 1:8.3.0-6
ii libgnutls30 3.6.7-4+deb10u3
ii libgssapi-krb5-2 1.17-3
ii libkrb5-3 1.17-3
ii libldap-2.4-2 2.4.47+dfsg-3+deb10u1
ii libltdl7 2.4.6-9
ii libnetfilter-conntrack3 1.0.7-1
ii libnettle6 3.4.1-1
ii libpam0g 1.3.1-5
ii libsasl2-2 2.1.27+dfsg-1+deb10u1
ii libstdc++6 8.3.0-6
ii libxml2 2.9.4+dfsg1-7+b3
ii logrotate 3.14.0-4
ii lsb-base 10.2019051400
ii netbase 5.6
ii squid-common 4.6-1+deb10u1

Versions of packages squid recommends:
ii ca-certificates 20190110
ii libcap2-bin 1:2.25-2

Versions of packages squid suggests:
ii resolvconf 1.79
pn smbclient 
pn squid-cgi 
pn squid-purge 
pn squidclient 
pn ufw 
pn winbind 

-- Configuration Files:
/etc/resolvconf/update-libc.d/squid changed:
PATH="/usr/sbin:/usr/bin:/sbin:/bin"
if [ -d /var/log ] ; then
invoke-rc.d squid reload || true
fi

/etc/squid/squid.conf changed:
acl manager proto cache_object
acl localnet src 192.168.*.0/24 #rdbl.heinrich.intra - work zone
acl localdmz src 192.168.*.0/24 #rdbl.heinrich.intra - dmz zone
acl localhome src 192.168.*.0/24 #rdbl.heinrich.intra - home zone
acl SSL_ports port 443 563 873
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 488 # gss-http
acl Safe_ports port 1025-65535 # unregistered ports
acl purge method PURGE
acl CONNECT method CONNECT
http_access allow localhost manager
http_access deny manager
http_access allow purge localhost
http_access deny purge
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow localhost
http_access allow localnet
http_access allow localhome
http_access deny all
http_reply_access allow localnet
http_reply_access allow localhome
http_reply_access deny all
icp_access allow localnet
icp_access deny all
htcp_access allow localnet
htcp_access deny all
http_port 3128
cache_mem 200 MB
maximum_object_size_in_memory 40 KB
cache_replacement_policy heap GDSF
cache_dir aufs /var/spool/squid 2048 16 256
maximum_object_size 40 MB
cache_swap_low 94
cache_swap_high 96
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern (Release|Packages(.gz)*)$ 0 20% 2880
refresh_pattern . 0 20% 4320
cache_effective_user proxy
forwarded_for off
coredump_dir /var/spool/squid


-- no debconf information

11c11
< After=network.target network-online.target nss-lookup.target
---
> After=local-fs.target network.target network-online.target nss-lookup.target