Le Vendredi 17 Octobre 2003 16:38, Henry Baragar a �crit :This is really strange: multilog should have been able to write any file if it is running under root.
Your comments caused me to look more closely at the default configurationSeems a wise decison.
and it looks like the multilog logging process is run by root in the
default configuration. (My preference is to minimize the number of
processes owned by root)
If you have a default configuration, how come multilog is running as "nobody"?
Multilog is owned by root.
What does " ps -aj |grep multilog" say?
/var/opt/log/bincimap was also owned by root, but I then chown'd it to nobody,
as suggested in the Binc README. That's the step I seem to have skipped in
the first place.
Yes, svscan is owned by root. I think it is invoked from init at boot-time,How was svscanboot invoked? Who owns the svcan process on your system? Is it "nobody"? It should be "root".
something like this: init --> svscanboot --> scscan --> supervise
What does "ps -aj |grep svscan" say? What does "ps -aj |grep supervise" say?
bincimap is trying "cd /opt/bincimap/bin", but can't: there should be no problem if the supervise process is running as root (see above).
I still cannot fathom the following log entries, though:
> Warning: unable to enter jail path "/opt/bincimap/bin" > and > Unprivileged stub shutting down
To me they seem to indicate some kind of privilege clash, but I don't know
enough about the Bincimap start-up stub to tell what's up.
Regards Sigmund.
-- Henry Baragar Principal, Technical Architecture 416-453-5626 Instantiated Software Inc. http://www.instantiated.ca
