Discussion:
comstar no persistence option
Joe Veliscos via illumos-zfs
2014-05-24 11:44:45 UTC
Permalink
Hi all,

New member here...

In a blog about building a storage system I read the following :

COMSTAR supports a "no persistence" option in the service configuration, so
that any configuration commands issued don't actually modify the persistent
configuration in the SMF configuration store.

How does one go about actually implementing this option?

Joe



-------------------------------------------
illumos-zfs
Archives: https://www.listbox.com/member/archive/182191/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182191/23047029-187a0c8d
Modify Your Subscription: https://www.listbox.com/member/?member_id=23047029&id_secret=23047029-2e85923f
Powered by Listbox: http://www.listbox.com
Saso Kiselkov via illumos-zfs
2014-05-24 12:50:19 UTC
Permalink
Post by Joe Veliscos via illumos-zfs
Hi all,
New member here...
COMSTAR supports a "no persistence" option in the service configuration,
so that any configuration commands issued don't actually modify the
persistent configuration in the SMF configuration store.
How does one go about actually implementing this option?
Hi Joe,

I'll be replying here, since this mailing list has a wider audience than
my blog. The "no persistence" thing simply means that any changes you do
to COMSTAR via the administration commands (stmfadm, itadm, etc.) won't
be persisted across reboots and COMSTAR will start out with a clean
config each time. To enable this behavior you simply flip a the STMF
service property stmf_data/persist_method to "none". See the
"set_stmf_non_persistent" function in the stmf-ha script:
https://github.com/skiselkov/stmf-ha/blob/master/stmf-ha#L52-L62

Cheers,
--
Saso
Loading...