systemd   2938

« earlier    

systemd Services Are Easy
I end up searching how to write systemd services every time I have to do it. This page looks helpful for next time
systemd  linux 
3 days ago by winks
Dropbox - ArchWiki
Prevent automatic updates
Since at least version 2.4.6 (see comments around 2013-11-06 on AUR), Dropbox has had an auto-update capability which downloads a new binary to the ~/.dropbox-dist/ folder. The service then attempts to hand over control to this binary and dies, causing systemd to re-start the service, generating a conflict and an endless loop of log-filling, CPU-eating misery.

A workaround is to prevent Dropbox from downloading the automatic update by creating the ~/.dropbox-dist/ folder and making it read-only:

$ rm -rf ~/.dropbox-dist
$ install -dm0 ~/.dropbox-dist
This appears to be necessary for modern Dropbox clients to operate successfully from systemd on arch.

Also see the relevant Dropbox forum post.
dropbox  arch  bug  systemd 
3 days ago by epsalt
Rethinking PID 1
For a fast and efficient boot-up two things are crucial:

To start less.
And to start more in parallel.
What does that mean? Starting less means starting fewer services or deferring the starting of services until they are actually needed. There are some services where we know that they will be required sooner or later (syslog, D-Bus system bus, etc.), but for many others this isn't the case. For example, bluetoothd does not need to be running unless a bluetooth dongle is actually plugged in or an application wants to talk to its D-Bus interfaces. Same for a printing system: unless the machine physically is connected to a printer, or an application wants to print something, there is no need to run a printing daemon such as CUPS. Avahi: if the machine is not connected to a network, there is no need to run Avahi, unless some application wants to use its APIs. And even SSH: as long as nobody wants to contact your machine there is no need to run it, as long as it is then started on the first connection. (And admit it, on most machines where sshd might be listening somebody connects to it only every other month or so.)

Starting more in parallel means that if we have to run something, we should not serialize its start-up (as sysvinit does), but run it all at the same time, so that the available CPU and disk IO bandwidth is maxed out, and hence the overall start-up time minimized.
linux  sysadmin  boot  systemd 
17 days ago by euler
Arch Linux installation on btrfs subvolumes
GitHub is where people build software. More than 27 million people use GitHub to discover, fork, and contribute to over 80 million projects.
gist  archlinux  btrfs  container  systemd 
18 days ago by ianweatherhogg

« earlier    

related tags

4*  5*  ads  ansible  arch  archlinux  autossh  bind  block  boot  btrfs  bug  bugs  celery  chkservice  circus  cli  confluent  container  containers  cron  daemon  daphne  dbus  debian  debug  debugging  deployment  dev  devops  devuan  dhcp  distributions  dns  dnsmasq  docker  documentation  dovecot  dropbox  emacs  envfile  environmentfile  excellent  fail  fleet  ftp  gdb  gist  go  golang  good  great  hardware  hibernate  homebridge  hosts  ifconfig  ifttt  init  interfaces  iot  ip  jenova  kontext  lang:en  laptop  lennart  libpam  linux  logging  manage  management  monitoring  mte  named  network  networking  node.js  nodered  openssh  os  pi  pid einslinux  power  processes  programming  protocol  python  raspberypi  raspian  rc.local  reboot  reference  resolve  resolved  resource  rsyslog  saas  screen  script  scripting  security  server  service  services  shutdown  socket  space  splash  ssh  supervisor  sys-admin  sysadmin  systemctl  systemd_analize  terminal  timer  tools  touch  troubleshooting  twitter  ubuntu  unicorn  unit  update  virtualenv  warelogging 

Copy this bookmark: