Thanks (as always) for the quick response this late at night. I did a
hand-edit of my svc-pkg-depot file to concat the --cfg option, and now
am getting this:
ppriv -s A=basic,-file_link_any,-proc_info,-proc_session,net_privaddr -e
/usr/lib/pkg.depotd
--ssl-dialog=smf:svc:/application/pkg/server/dev:default --cfg
svc:/application/pkg/server/dev:default
pkg.depotd: option: --ssl-dialog -- Invalid value specified. Expected:
builtin, exec:/path/to/program, smf, or an SMF FMRI.
Is the ssl-dialog option being constructed correctly?
-- Alan
On 07/15/10 10:53 PM, Shawn Walker wrote:
On 07/15/10 10:27 PM, Alan Steinberg wrote:
I pulled over the latest source and tried using it on my depot, and am
getting these messages:
//lib/svc/method/svc-pkg-depot[183]: --cfg
svc:/application/pkg/server/dev:default: not found [No such file or
directory]
[ Jul 15 21:18:58 Stopping because all processes in service exited. ]
I'm obviously setting something incorrectly, but in looking at the
pkg-server.xml file that was delivered with this change, I can't see
what I am doing wrong with my "pkg-server-dev.xml" file.
svc-pkg-depot shows:
cmd="$wrapper ${pkg_root}usr/lib/pkg.depotd $bool_ops $option_ops " \
"--cfg $SMF_FMRI"
But if the --cfg option can be a file, how does this get set?
--cfg determines where the *depot* configuration is retrieved from.
cfg_file is for the *repository* configuration.
It isn't picking up my manifest file's define of cfg_file.
You won't see anything in the log about it picking up cfg_file. The
depot now reads all of its configuration directly from SMF.
Once it starts up (properly) it will read the configuration from SMF,
discover that you have set a cfg_file for the repository, and then use
that.
This did work at one point during my test cycle, but it's apparent I
botched something horribly during my final webrev and putback.
Apologies,
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
