#sysvinit

[linuxtldr]

Check If You Are Using SystemD or Not on Linux

This article will show you three methods for determining whether your Linux system is using systemd or another init system.

[2daygeek]

We all are heard about this word many times but only few of us know what is this exactly. We will show you how to identify the system manager. I will try my

2DayGeek: 3 easy commands to determine the init system manager on Linux.

[linux-ubuntu-it]

Init Freedom: rilasciata Devuan 1.0.0 RC Abbiamo seguito sin dall'inizio il progetto Devuan, <a ... [Visita il sito per leggere tutto l'articolo

[utappia]

Διαχείριση του συστήματος σας με τη χρήση του systemd

Διαχείριση του συστήματος σας με τη χρήση του systemd

Το systemd είναι ο νέος διαχειριστής του συστήματος και των διαφόρων υπηρεσιών του, που έρχεται ως προ-επιλεγμένος στις δημοφιλέστερες Linux διανομές. Ξεκινά μαζί με το σύστημα μας και το εποπτεύει στο σύνολο του. Στο παρόν άρθρο θα δούμε πως μπορούμε να το χρησιμοποιήσουμε προκειμένου να έχουμε τον πλήρη έλεγχο τι τρέχει, τι δουλεύει και πολλές άλλες χρήσιμες πληροφορίες. (more…)

View On WordPress

[for-the-user]

Upstart vs SysVinit

/etc/init.d contains scripts used by the System V init tools (SysVinit). This is the traditional service management package for Linux, containing the init program (the first process that is run when the kernel has finished initializing, not counting initrd) as well as some infrastructure to start and stop services and configure them. Specifically, files in /etc/init.d are shell scripts that respond to start, stop, restart, and (when supported) reload commands to manage a particular service. These scripts can be invoked directly or (most commonly) via some other trigger (typically the presence of a symbolic link in /etc/rc?.d/).

/etc/init contains configuration files used by Upstart. Upstart is a young service management package championed by Ubuntu. Files in /etc/init are configuration files telling Upstart how and when to start, stop, reload the configuration, or query the status of a service. As of lucid, Ubuntu is transitioning from SysVinit to Upstart, which explains why many services come with SysVinit scripts even though Upstart configuration files are preferred. In fact, the SysVinit scripts are processed by a compatibility layer in Upstart.

.d in directory names typically indicates a directory containing many configuration files or scripts for a particular situation (e.g. /etc/apt/sources.list.d contains files that are concatenated to make a virtual sources.list; /etc/network/if-up.d contains scripts that are executed when a network interface is activated). This structure is usually used when each entry in the directory is provided by a different source, so that each package can deposit its own plug-in without having to parse a single configuration file to reference itself. In this case, it just happens that “init” is a logical name for the directory, SysVinit came first and used init.d, and Upstart used plain init for a directory with a similar purpose (it would have been more “mainstream”, and perhaps less arrogant, if they'd used /etc/upstart.d instead).

Of course now there's systemctl, but I'll get to that soon enough.

P.S. I just learnt that on an ubuntu system without chkconfig, to add things to autostart when there is a start script in /etc/init.d/ you can do this:

$ update-rc.d zabbix-agent defaults Adding system startup for /etc/init.d/zabbix-agent ... /etc/rc0.d/K20zabbix-agent -> ../init.d/zabbix-agent /etc/rc1.d/K20zabbix-agent -> ../init.d/zabbix-agent /etc/rc6.d/K20zabbix-agent -> ../init.d/zabbix-agent /etc/rc2.d/S20zabbix-agent -> ../init.d/zabbix-agent /etc/rc3.d/S20zabbix-agent -> ../init.d/zabbix-agent /etc/rc4.d/S20zabbix-agent -> ../init.d/zabbix-agent /etc/rc5.d/S20zabbix-agent -> ../init.d/zabbix-agent

To stop something from autostarting on boot

$ update-rc.d -f zabbix-agent remove

There's not option to check the status unfortunately, so you can just add or remove and it'll tell you if nothing needs to happen.

$ update-rc.d apache2 defaults System start/stop links for /etc/init.d/apache2 already exist. $ update-rc.d mysqld defaults update-rc.d: /etc/init.d/mysqld: file does not exist

[socrate84]

Antix MX-15, elle va booster vos anciens PC !

Antix MX-15, elle va booster vos anciens PC !

Antix fait-elle partie de ces distributions capables de ressusciter les “ordinosaures” et autres PC condamnés à la déchetterie ?

On connaissait déjà Lubuntu, Emmabuntus où encore la Handylinux  pour sauver les machines prenant de l’âge. Grâce à un environnement de bureau léger requérant peu de ressources systèmes (xfce 4.12) cette Antix se propose également comme secouriste des PC à l’agonie.

 L…

View On WordPress

[phenobarbital]

Cómo montar Debian Jessie sin systemd en 3 simples pasos

Cómo montar Debian Jessie sin systemd en 3 simples pasos

¿Por qué lograr un Debian jessie sin systemd?

Si, lo admito, soy un Troll anti-systemd, ya hace algún tiempo había escrito una herramienta que me permitía llevar una instalación desde netinstall a un estado estable y asegurado de Debian GNU/Linux (dicho script, acá) sin embargo, montar un Debian jessie sin systemd implica un par de cambios que, gracias a la gente de Debian, son bastante sencillos.

View On WordPress

[barisperintah]

stop paksa syncthing dari Linux Mint!

Ceritanya syncthing makan banyak memory sampe 400MBan+ hampir sebanding dengan firefox, dan sayangnya RAM masih 2GB (nunggu kiriman), jd terpaksa biar rada lega saya stop syncthing dari task manager.

Tapi, syncthingnya hidup kembali LOL, ini dikarenakan pengaturan confignya. Setelah baca2 syncthing harus dipaksa berenti dari initctl

Baris Perintahnya yakni

initctl stop syncthing

lalu tinggal masukkan passsword root anda untuk memberikan akses root kepada initctl

Selesai