touch-packages team mailing list archive

["Dr. Jens Rosenboom" <j.rosenboom@xxxxxxxx>]

While I agree that this may never have been guaranteed, it has been
working with all previous init systems. For me, the implied policy of
using rc.local is: Run after all other init stuff has finished.

For example, https://github.com/puppetlabs/razor-server uses modifying
rc.local in order to trigger some post installation actions to happen
once the node has rebooted after being installed. This works pretty well
with Precise and Trusty and also seems to be fine with most other
distros.

Also, having a server with no network connectivity ever will also not be
very useful. This is certainly different for desktop systems, but then,
why would you have the

After=network.target

at all?

** Changed in: systemd (Ubuntu)
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1451797

Title:
  rc.local should require network-online.target

Status in systemd package in Ubuntu:
  New

Bug description:
  The current definition in `/lib/systemd/system/rc-local.service` uses
  `After=network.target`, which is pretty useless, as `network.target`
  according to
  http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ only
  has relevance during shutdown, which never happens for rc.local.

  The result is that tasks in rc.local may get started before the
  network is properly setup, which may cause them to fail, as this is a
  significant change from the old SysV init behaviour.

  The solution would be to change the dependency to

  Wants=network-online.target
  After=network-online.target

  see also the notes in
  http://www.freedesktop.org/software/systemd/man/systemd.special.html
  for that.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu4 [modified: lib/systemd/system/rc-local.service]
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Tue May  5 11:40:42 2015
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9DRT
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRT
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.21
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd05/04/2012:svnSupermicro:pnX9DRT:pvr0123456789:rvnSupermicro:rnX9DRT:rvr1.21:cvnSupermicro:ct3:cvr0123456789:
  dmi.product.name: X9DRT
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1451797/+subscriptions