When allowing a user shell access, DA will edit /etc/ssh/sshd_config and add that login to the AllowUser list, change the shell, but it won't restart SSH so it can pickup the new config.
I restarted ssh from the console, and it worked fine.
There was another error I ran into several times that involved backing up a user's site from my soon to be former sad excuse for hosting company's oversold DA v1.23.4 and restoring on my new-hotness Debian 3.1 w/ DA v1.24.2.
When backing up and restoring from the same user name, everything works fine except for the dbase portion. My DA reported an error that it couldn't find /usr/bin/mysql and therefore couldn't run the SQL to import the tables and data. In Sarge, it is
located in /usr/local/mysql/bin/mysql w/ a sym ln in /usr/local/bin/mysql.
I was able to import the tables via PhpMyAdmin but since you can call 'mysql' from anywhere because it is in the path, is it necessary to refer to the absolute path?
I've used DA several times before from the reseller standpoint, but now I have my own system, and shell access, not much can be sweeter.
-bdk
I restarted ssh from the console, and it worked fine.
There was another error I ran into several times that involved backing up a user's site from my soon to be former sad excuse for hosting company's oversold DA v1.23.4 and restoring on my new-hotness Debian 3.1 w/ DA v1.24.2.
When backing up and restoring from the same user name, everything works fine except for the dbase portion. My DA reported an error that it couldn't find /usr/bin/mysql and therefore couldn't run the SQL to import the tables and data. In Sarge, it is
located in /usr/local/mysql/bin/mysql w/ a sym ln in /usr/local/bin/mysql.
I was able to import the tables via PhpMyAdmin but since you can call 'mysql' from anywhere because it is in the path, is it necessary to refer to the absolute path?
I've used DA several times before from the reseller standpoint, but now I have my own system, and shell access, not much can be sweeter.
-bdk
