upstart commands should point out "service" if upstart is not running

Bug #1592251 reported by Hans Ginzel
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)

Bug Description

The 'restart <service>' command does not work on default 16.04 installation.

If there is no upstart, the restart command should say the equivalent systemd command and/or should it execute.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Tue Jun 14 06:48:56 2016
MachineType: LENOVO 7666WJ5
 Socket 0:
   no product info available
 Socket 0:
   no card
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=e8264d19-08ae-46d2-b99a-d386d051d8b3 ro quiet splash
SourcePackage: systemd
 [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf

 3 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install) 04/18/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7NETB2WW (2.12 ) 7666WJ5
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7NETB2WW(2.12):bd04/18/2008:svnLENOVO:pn7666WJ5:pvrThinkPadX61s:rvnLENOVO:rn7666WJ5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: 7666WJ5
dmi.product.version: ThinkPad X61s
dmi.sys.vendor: LENOVO

Revision history for this message
Hans Ginzel (hans-matfyz) wrote :
tags: added: init systemd upstart
Revision history for this message
Martin Pitt (pitti) wrote :

"reset" has nothing to do with services, upstart, or systemd. It resets the terminal settings and contents and clears it, see manpage.

If you mean "restart", then yes, this is an upstart specific command. Please use "service" as an init neutral way to control services.

affects: systemd (Ubuntu) → upstart (Ubuntu)
Changed in upstart (Ubuntu):
status: New → Won't Fix
Revision history for this message
Hans Ginzel (hans-matfyz) wrote :

The bug should fixed.

Should the upstart specific commands be installed in the default 16.04 installation?

description: updated
description: updated
Revision history for this message
Martin Pitt (pitti) wrote :

Because upstart is still being used for the session startup. We are working on the transition there.

Changed in upstart (Ubuntu):
importance: Undecided → Wishlist
status: Won't Fix → Triaged
summary: - restart: Unable to connect to Upstart: Failed to connect to socket
- /com/ubuntu/upstart: Connection refused
+ upstart commands should point out "service" if upstart is not running
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.