David Powell wrote:
Darren Reed wrote:
...
It might be the case that fixed project IDs were an anachronism best
replaced by a dynamic, system-local ID mechanism, but unfortunately
it's probably too late to change that.
You might be right about that.
I can't discernany actual use for the project id,
except (it seems) for the extended accounting log files.
2) As part of the work for PSARC/2009/332, I'm putting
together a "i.project" file to add the "svc.inetd"
project to existing /etc/project files when people
do an upgrade. The obvious thing to do is to add it
to the file in a way that makes it identical to the
/etc/project that gets committed. But there is no
operational need that I can see for that to happen.
Have you determined how this will work under IPS?
What does IPS do if a project introduces a new daemon that
wants to run as non-root? Whatever is done for that and files
similar to /etc/passwd would be the basis of a recipe to fix
/etc/project.
When I was looking at the various i.* files, it occurred
to me that it was a pity there wasn't better infrastrucutre
to support those scripts. A lot of them are doing the same
thing and have the same n lines of sed/if repeated time
and time again. I hope IPS makes that better...
Darren
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
