Heads up: vscan scan engine name prefix
Date: Thu, 10 Apr 2008 17:47:49 -0700 From: Joyce McIntosh <Joyce.McIntosh at sun dot com> To: onnv-gate at onnv dot sfbay dot sun dot com, on-all at eng dot sun dot com Subject: Heads up: vscan scan engine name prefix If you have never enabled / configure the vscan service this should not affect you. The putback of 6660667 Engine name is used directly as property group name without any prefix introduces a prefix (vs_engine_) to the property groups created per configured scan engine. If you configured scan engines in a previous build their property group names will not have this prefix and thus they will not be recognized by vscand or vscanadm. You can manually edit these property group names using svccfg, or you can remove the service configuration, re-import it and re-configure your scan engines. The vscanadm CLI is unchanged. The prefix is not part of the engine_id passed to vscanadm. For example: an engine_id of av1 will now have associated property group vs_engine_av1. svccfg -s vscan:icap svc:/system/filesystem/vscan:icap > editprop OR svccfg svc:> delete system/filesystem/vscan svc:> import /var/svc/manifest/system/filesystem/vscan.xml svc:> quit vscanadm add-engine [-p property=value]... engine_id
on 2009/11/20 23:48