[bug-notifications] [cswclassutils 0004075]: cswinitsmf should refuse to create an FMRI with a dot in the name

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://www.opencsw.org/mantis/view.php?id=4075 
====================================================================== 
Reported By:                maciej
Assigned To:                bonivart
====================================================================== 
Project:                    cswclassutils
Issue ID:                   4075
Category:                   other
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2009-12-10 09:34 CET
Last Modified:              2010-01-07 17:38 CET
====================================================================== 
Summary:                    cswinitsmf should refuse to create an FMRI with a
dot in the name
Description: 
08:25 <@automaciej> I just discovered that SMF FMRIs don't work if they
have dots in them.
08:25 <@automaciej> like, you can have cswpostgres_8_4, but can't have
cswpostgres_8.4
08:29 < lewellyn> yup
08:29 < lewellyn> it's documented somewhere, in fact.
08:29 <@automaciej> cswclassutils don't catch that
08:29 < lewellyn> that's why sun's services tend to be whatever23 or
whatever_23
08:30 < Dagobert> I guess it is because SMF is designed to be extended to
multi-host at some point in the future and . is a domain-sep. Same thing as
for auto*

====================================================================== 

---------------------------------------------------------------------- 
 (0007192) bonivart (manager) - 2010-01-07 17:38
 http://www.opencsw.org/mantis/view.php?id=4075#c7192 
---------------------------------------------------------------------- 
I agree with adding a warning to cswinitsmf, the problem is already in the
package and it can't be handled much better or should i filter out dots
from the FMRI with sed before using it? Still issue a big warning though.

I think it's most important to not let new and updated packages pass with
known problems. Everything we find we should add a test for so it can't
pass again.