Language Selection

English French German Italian Portuguese Spanish

Manage Linux init or startup scripts

Filed under
HowTos

Init scripts are small shell programs that usually control services, also known as daemons. Other applications for init scripts involve simply controlling the state of something such as hdparm (HDD sleep timeouts), iptables (loading firewall rule-sets into the kernel) and setserial (COM port configuration).The /etc/init.d directory contains the scripts executed by init at boot time and when the init state.

Init scripts are also important during startup and shutdown (simply “runlevel” changes on *nix systems). If you take a look at the list of processes running on your machine (try ps auwx), chances are that the process with the lowest PID is called “init”. This is the parent of all processes; it’s the first program the kernel starts when booting. init , which can be found in /sbin/init, is responsible for getting the system up and running after the kernel has finished booting.

There are three simple utilities to manage your startup or init scripts

Full Story.

More in Tux Machines

LibreOffice 5, a foundation for the future

The release of the next major version of LibreOffice, the 5.0, is approaching fast. In several ways this is an unique release and I’d like to explain a bit why. Read more

Samsung Continues to Lessen Android Dependence

Samsung's partnership with members of the Linux Foundation appears to be bearing fruit. The partnership's mobile operating system -- dubbed Tizen -- is Linux-based. Samsung's initial Tizen phone rollout was rocky: The company's highly anticipated Samsung Z launch in Russia was quickly canceled last year, and the company blamed concerns about the ecosystem for the delay. Unfortunately, in many cases, ecosystem development presents a "chicken and egg" problem: Developers won't build apps until you have users, and users won't select your product until you have apps. Read more

Linux 4.2 Offers Performance Improvements For Non-Transparent Bridging

The Non-Transparent Bridge code is undergoing a big rework that has "already produced some significant performance improvements", according to its code maintainer Jon Mason. For those unfamiliar with NTB, it's described by the in-kernel documentation, "NTB (Non-Transparent Bridge) is a type of PCI-Express bridge chip that connects the separate memory systems of two computers to the same PCI-Express fabric. Existing NTB hardware supports a common feature set, including scratchpad registers, doorbell registers, and memory translation windows." Or explained simply by the Intel Xeon documentation that received the NTB support, "Non-Transparent Bridge (NTB) enables high speed connectivity between one Intel Xeon Processor-based platform to another (or other IA or non-IA platform via the PCIe interface)." Read more

Benchmarks Of 54 Different Intel/AMD Linux Systems

This week in celebrating 200,000 benchmark results in our LinuxBenchmarking.com test lab, I ran another large comparison against the latest spectrum of hardware/software in the automated performance test lab. Read more