nmbd and smbd will not be started again on transition from runlevel 1 to 2

Bug #820679 reported by Clint Byrum on 2011-08-03
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Medium
Unassigned
Trusty
Undecided
Unassigned

Bug Description

The stop on conditions for these jobs is

stop on runlevel [!2345]

which will cause them to stop when the administrator switches runlevel to 1. But the on switch to 2, there is no corresponding start on condition to cause them to start again.

Ursula Junque (ursinha) on 2011-08-05
Changed in samba (Ubuntu):
importance: Undecided → Medium
Ben Howard (utlemming) wrote :

Merge proposal committed.

Changed in samba (Ubuntu):
assignee: nobody → Ben Howard (utlemming)
status: New → Triaged
Ben Howard (utlemming) on 2016-04-21
Changed in samba (Ubuntu):
assignee: Ben Howard (utlemming) → nobody
Andreas Hasenack (ahasenack) wrote :

Thanks for filing this bug in Ubuntu.

I tried this "runlevel" switch in our systemd releases, even though systemd doesn't have this same exact concept, and it worked as expected. "runlevel 1" stopped samba, and going back to "2" started it again.

While trusty is still supported and is an upstart-based release, I don't believe this issue qualifies for an SRU as per https://wiki.ubuntu.com/StableReleaseUpdates#When.

Changed in samba (Ubuntu):
status: Triaged → Invalid
Changed in samba (Ubuntu Trusty):
status: New → Won't Fix

Always nice to see a 6 year old bug fixed!

Excerpts from Andreas Hasenack's message of 2017-06-08 23:19:08 UTC:
> ** Changed in: samba (Ubuntu)
> Status: Triaged => Invalid
>
> ** Changed in: samba (Ubuntu Trusty)
> Status: New => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/820679
>
> Title:
> nmbd and smbd will not be started again on transition from runlevel 1
> to 2
>
> Status in samba package in Ubuntu:
> Invalid
> Status in samba source package in Trusty:
> Won't Fix
>
> Bug description:
> The stop on conditions for these jobs is
>
> stop on runlevel [!2345]
>
> which will cause them to stop when the administrator switches runlevel
> to 1. But the on switch to 2, there is no corresponding start on
> condition to cause them to start again.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/820679/+subscriptions

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers