963 shaares
Notre objectif est de faire découvrir la programmation et l'algorithmique au plus grand nombre de personnes possible. Nous créons et diffusons gratuitement des outils et contenus permettant de progresser rapidement dans ces domaines, et organisons des concours pour accompagner cette progression.
Kill user processes on logout
Arch Linux builds the systemd package with --without-kill-user-processes, setting KillUserProcesses to no by default. This setting causes user processes not to be killed when the user completely logs out. To change this behavior in order to have all user processes killed on the user's logout, set KillUserProcesses=yes in /etc/systemd/logind.conf.
Note that changing this setting breaks terminal multiplexers such as tmux and screen. If you change this setting, you can still use a terminal multiplexer by using systemd-run as follows:
Arch Linux builds the systemd package with --without-kill-user-processes, setting KillUserProcesses to no by default. This setting causes user processes not to be killed when the user completely logs out. To change this behavior in order to have all user processes killed on the user's logout, set KillUserProcesses=yes in /etc/systemd/logind.conf.
Note that changing this setting breaks terminal multiplexers such as tmux and screen. If you change this setting, you can still use a terminal multiplexer by using systemd-run as follows:
8
down vote
favorite
1
I'm doing a hardware refresh on a my Colo, I just need to copy my UFW rules from my old server to my new server. I dont seem to be able to get them copy all the active rules from my old server to my new one.
How do I copy my active UFW rules between servers?
down vote
favorite
1
I'm doing a hardware refresh on a my Colo, I just need to copy my UFW rules from my old server to my new server. I dont seem to be able to get them copy all the active rules from my old server to my new one.
How do I copy my active UFW rules between servers?
There are many scenarios where you might have to move your data and operating requirements from one server to another. You may need to implement your solutions in a new datacenter, upgrade to a larger machine, or transition to new hardware or a new VPS provider.
Whatever your reasons, there are many different considerations you should make when migrating from one system to another. Getting functionally equivalent configurations can be difficult if you are not operating with a configuration management solution such as Chef, Puppet, or Ansible. You need to not only transfer data, but also configure your services to operate in the same way on a new machine.
In this guide, we will discuss how to prepare your source and target systems for a migration. This will include getting your two machines to communicate with SSH keys and a heavy investigation as to what components need to be transferred. We will work on the actual migration in the next article.
Whatever your reasons, there are many different considerations you should make when migrating from one system to another. Getting functionally equivalent configurations can be difficult if you are not operating with a configuration management solution such as Chef, Puppet, or Ansible. You need to not only transfer data, but also configure your services to operate in the same way on a new machine.
In this guide, we will discuss how to prepare your source and target systems for a migration. This will include getting your two machines to communicate with SSH keys and a heavy investigation as to what components need to be transferred. We will work on the actual migration in the next article.
Let’s Encrypt is a free, automated, and open certificate authority (CA), run for the public’s benefit. Let’s Encrypt is a service provided by the Internet Security Research Group (ISRG). The key principles behind Let’s Encrypt are:
Free: Anyone who owns a domain name can use Let’s Encrypt to obtain a trusted certificate at zero cost.
Automatic: Software running on a web server can interact with Let’s Encrypt to painlessly obtain a certificate, securely configure it for use, and automatically take care of renewal.
Secure: Let’s Encrypt will serve as a platform for advancing TLS security best practices, both on the CA side and by helping site operators properly secure their servers.
Transparent: All certificates issued or revoked will be publicly recorded and available for anyone to inspect.
Open: The automatic issuance and renewal protocol will be published as an open standard that others can adopt.
Cooperative: Much like the underlying Internet protocols themselves, Let’s Encrypt is a joint effort to benefit the community, beyond the control of any one organization.
Free: Anyone who owns a domain name can use Let’s Encrypt to obtain a trusted certificate at zero cost.
Automatic: Software running on a web server can interact with Let’s Encrypt to painlessly obtain a certificate, securely configure it for use, and automatically take care of renewal.
Secure: Let’s Encrypt will serve as a platform for advancing TLS security best practices, both on the CA side and by helping site operators properly secure their servers.
Transparent: All certificates issued or revoked will be publicly recorded and available for anyone to inspect.
Open: The automatic issuance and renewal protocol will be published as an open standard that others can adopt.
Cooperative: Much like the underlying Internet protocols themselves, Let’s Encrypt is a joint effort to benefit the community, beyond the control of any one organization.
All the PubSubHubbubb hubs hosted at Superfeedr are compliant with the core specifications for versions 0.3 and 0.4. To enable your publisher hub and get subscribers coming to your real-time feeds, you need to set up discovery and ping.
Getting a notification that Docker containers are down in production is one of the worst ways to spend your night. In today’s article, we’ll discuss how to use Docker’s restart policy to automatically restart containers and avoid those late-night notifications.
We have a mission to save the web by increasing browsing speed and safety for users, while growing ad revenue share for content creators.
The web has become a different place. With the ad-tech ecosystem out of control, users have revolted and blocking ads has become the new weapon of choice. But this results in a race to the bottom where nobody wins. Without the ability for content creators to earn money for their efforts, they may need to shut down or find a new source of revenue. Users could be left with nowhere to browse, relegated to hand-picked content from controlled sources. Brave is saving the web by building a new suite of cutting-edge web browsers that feature class leading speed, security and protection, plus a new ad revenue sharing solution to help keep publishers in business.
The web has become a different place. With the ad-tech ecosystem out of control, users have revolted and blocking ads has become the new weapon of choice. But this results in a race to the bottom where nobody wins. Without the ability for content creators to earn money for their efforts, they may need to shut down or find a new source of revenue. Users could be left with nowhere to browse, relegated to hand-picked content from controlled sources. Brave is saving the web by building a new suite of cutting-edge web browsers that feature class leading speed, security and protection, plus a new ad revenue sharing solution to help keep publishers in business.
juste un petit guide pour bien démarrer avec git. no deep shit ;)
Ce tutoriel traite de ces magnifiques petites choses lumineuses que sont les LED. Nous en avons déjà parlé dans la leçon n°3 quand nous nous sommes amusés à faire clignoter des LED, mais aussi à jouer avec des LED multicolores pour former une orbite lumineuse à variation de couleur dynamique. Si vous n'avez pas encore abordé cette leçon, nous vous invitons à la suivre jusqu'au bout, d'accord ? Ainsi, nous pourrons commencer par quelques expériences.
Blog Domotique : article sur le détecteur d'ouverture Nodon
Stickers muraux
De votre domicile ... au central téléphonique, votre connexion ADSL chemine via votre ligne téléphonique, la ligne de cuivre. Ce chemin se termine dans le Noeud de Raccordement abonnés (NRA) où se situe les équipements de l'opérateur historique (Orange/France Telecom) qui a en charge des lignes sur la Boucle Locale, puis la ligne en cas de dégroupage est acheminée vers la Salle de Dégroupage où se trouve les équipements DSLAM des opérateurs alternatifs, comme ici Free. Regardons de manière succincte ce cheminement, ces équipements... et comment se passe le câblage, l'activation de votre nouvel accès ADSL.
DSLAM Free Ogéviller (Fréménil)