Hi all
I have disabled on-page error display per default. This is best practice for all tools "in production", so as not to make it easier for attackers.
To see errors reported from your scripts, you can do two things:
1) look for them in /var/log/user.log, like this:
tail -F /var/log/user.log | grep <yourusername>
Note: this is on the webserver, hemlock, not on the login server.
2) temporarily enable on-page error display for your script(s) by putting the following in your php code:
ini_set('display_errors', 1); error_reporting(E_ALL & ~E_NOTICE);
Regards, Daniel
2008/8/26 Daniel Kinzler daniel@brightbyte.de:
Note: this is on the webserver, hemlock, not on the login server.
Could someone think of a way to make hemlock's files accessible at nightshade and vice versa? It is not convenient to hold a separate shell window just to see the errors.
— Kalan
On Tue, Aug 26, 2008 at 01:52:25PM +0800, Kalan wrote:
Could someone think of a way to make hemlock's files accessible at nightshade and vice versa? It is not convenient to hold a separate shell window just to see the errors.
One classic solution is to set up a no-password ssh key, configured so it is only accepted for connections between toolserver.org hosts. To do this, set up the new ssh key as normal and then add
from="*.toolserver.org"
before 'ssh-rsa' at the beginning of the relevant line in .ssh/authorized_keys.
Then you can cat or tail the log files on hemlock from processes running on nightshade.
- Carl
toolserver-l@lists.wikimedia.org