Project

General

Profile

Actions
Copy link

Bug #999

open

Services: svccfg numeric instance name not accepted / svccfg import fails

Added by Lou Picciano about 12 years ago. Updated about 12 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Start date:
2011-05-07
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
External Bug:

Description

svcadm will not enable a manifest with a numeric-only instance name.

EG, instance v123 is acceptable; 123 is not.

note: svccfg will validate a manifest so configured...

Actions
Copy link
 #1

Updated by Julian Wiesener about 12 years ago

  1. svccfg validate tntnet.xml
  2. svccfg import tntnet.xml
    svccfg: Invalid instance name "123".
    svccfg: Import of tntnet.xml failed. Progress:
    svccfg: Service "site/tntnet": properties imported.
    svccfg: Instance "123": not reached.
    svccfg: Import failed.

changing instance name to 123v doesn't work either, however, v123 does. So the report schould be called "does not allow names starting with numbers" rather then does't allow numeric names.

It need to be checked, if it is a bug in validate, or if we want to allow instance names starting with numbers.

Actions
Copy link
 #2

Updated by Albert Lee about 12 years ago

  • Project changed from OpenIndiana Distribution to illumos gate
  • Priority changed from Normal to Low
Actions
Copy link

Also available in: Atom PDF