Project

General

Profile

Actions

Bug #12071

closed

clarify implementation of single_instance in SMF services

Added by John Levon over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
Actions #1

Updated by John Levon over 2 years ago

smf_restarter and svc.startd both make mention of:

single_instance
This is an optional property. When set, only one
instance of the service is allowed to transition to
an online or degraded status at any time.

Except, nothing ever implemented it. And now, due to copy-and-pasting, this is set all over the place in manifests that really do have multiple instances that should run at once. So we can't just implement it (and it was always of highly dubious utility). Let's make clear it's ignored.

Actions #2

Updated by John Levon over 2 years ago

  • Subject changed from Clarify implementation of single_instance in SMF services to clarify implementation of single_instance in SMF services
Actions #3

Updated by Electric Monk over 2 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

git commit 8047359fa9aaaf6af13c81ce125afa018449661d

commit  8047359fa9aaaf6af13c81ce125afa018449661d
Author: John Levon <john.levon@joyent.com>
Date:   2019-12-16T16:35:37.000Z

    12071 clarify implementation of single_instance in SMF services
    Reviewed by: Robert Mustacchi <rm@fingolfin.org>
    Approved by: Dan McDonald <danmcd@joyent.com>

Actions

Also available in: Atom PDF