On Tue, 1 Mar 2005, Matt wrote:
When providing a shell environment for a larger number of users, what is the
best way to retrict access to commands/resources? I've already setup quotas.
I don't want users playing with system commands. I've read something about a
retricted shell, but can't find
Max Laier wrote:
On Tuesday 01 March 2005 21:22, Matt wrote:
When providing a shell environment for a larger number of users, what is
the best way to retrict access to commands/resources? I've already
setup quotas. I don't want users playing with system commands. I've
read something about a r
On Tuesday 01 March 2005 21:22, Matt wrote:
> When providing a shell environment for a larger number of users, what is
> the best way to retrict access to commands/resources? I've already
> setup quotas. I don't want users playing with system commands. I've
> read something about a retricted she
When providing a shell environment for a larger number of users, what is
the best way to retrict access to commands/resources? I've already
setup quotas. I don't want users playing with system commands. I've
read something about a retricted shell, but can't find any details.
_
4 matches
Mail list logo
