Joey Hess <[EMAIL PROTECTED]> writes:
> You really don't want to know, but in brief it runs many different
> processes that need to be very isolated from each other and have very
> different permissions given to them. I allocate the uids from the pool
> on the fly and use it for a kind of process
Wichert Akkerman wrote:
> Scary, why would it need so many uids?
You really don't want to know, but in brief it runs many different
processes that need to be very isolated from each other and have very
different permissions given to them. I allocate the uids from the pool
on the fly and use it for
Previously Joey Hess wrote:
> Well, I have a package that really needs a minumum of 100 but ideally
> 1000 semi-static uids of its own (the block should be contiguous; must
> have _no_ user in the password file for at least a large percentage of
> them; don't ask), but I have not dared to bring it
Wichert Akkerman wrote:
> We have reserved the 3-5 uid/gid range for ages, but never used
> it and observing the current rate of growth I don't think it makes sense
> to keep them reserved: Debian will not use that range in the next
> century, while large systems definitely can use the extr
Package: debian-policy
Severity: wishlist
We have reserved the 3-5 uid/gid range for ages, but never used
it and observing the current rate of growth I don't think it makes sense
to keep them reserved: Debian will not use that range in the next
century, while large systems definitely can u
5 matches
Mail list logo
