1) To create end user accounts in a VSD--do I just user useradd as expected, or is there some vsd tool to create them? 2) Why aren't end user accounts chrooted for security? If the VSD is similar to a reseller account, then the end users (aka. scary people :) are the subaccounts under those. Why aren't they set up in a chrooted environment? Obviously they don't need the dedicated software that the VSD does, but security is extremely important for them. My guess is this just isn't completed yet? Or is left as an exercise for the reader :) 3) Should admin start with admin rights? After installing and setting up VSD's, the admin user had: ftp, mail, perl, gcc, net, telnet rights. Shouldn't admin user start with admin rights? 2) So many many processes... So I created two VSD's each running apache and MySQL and the other default stufff (atd, crond , syslogd). So a single VSD set up like this uses at least 15 processes. So.... for just 100 VSD's that's... 1500 processes! Umm... doesn't that pose a problem for a typical server? Especially as there may be other services I want to allow the VSD's which would increase that even more. Thanks! -- Joel Shellman
