OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

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