Project

General

Profile

Bug #999

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

Added by Lou Picciano over 8 years ago. Updated over 8 years ago.

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

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

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...

History

#1

Updated by Julian Wiesener over 8 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.

#2

Updated by Albert Lee over 8 years ago

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

Also available in: Atom PDF