Les vidéos d’Henri Guillemin

If the rule you followed brought you to this, of what use was the rule ?

Anton Chigurh – No Country For Old Men

Among the calamities of war may be numbered the diminution of the love of truth, by the falsehoods which interest dictates, and credulity encourages.

Samuel Johnson, The Idler no. 30 (11 Nov. 1758)

Un fou rempli d’erreurs, que le trouble accompagne….

En vain monte à cheval pour tromper son ennui ;

Le chagrin monte en croupe et galope avec lui

(Nicolas BOILEAU-DESPRÉAUX, Épît. v.)

“Ainsi obsédé par ses échecs passés, il s’ingéniait à ruiner son présent.”

SNMP logging a lot to Syslog

SNMPd is a systemd, unit now.

So the file we have to modify is not /etc/default/snmpd but /etc/systemd/system/multi-user.target.wants/snmpd.service

We just need to change -Lsd to -LS4d to only log warning level messages and get rid of the millions of UDP connections.

Description=Simple Network Management Protocol (SNMP) Daemon.

ExecStartPre=/bin/mkdir -p /var/run/agentx
ExecStart=/usr/sbin/snmpd -LS4d -Lf /dev/null -u Debian-snmp -g Debian-snmp -I -smux,mteTrigger,mteTriggerConf -f
ExecReload=/bin/kill -HUP $MAINPID


After that run:

systemctl daemon-reload
systemctl reload snmpd

Samba hell

The share options “read only” and “writeable” have the following defaults:

Default: read only = yes
Default: writeable = no

So, think of explicitly set write permissions if needed (or lose a lot of time searching why you cannot write, that happened to a err.. friend, you know :/).

Obey pam restrictions has weird side effects like using the default UMASK set on the host for creating files, which de facto overwrite the force create mode and force directory mode options. That’s also a good way to lose time searching why the permissions are not set correctly.

On some old configurations I found it set to yes, but the default is now no.

Default: obey pam restrictions = no

Source: https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html