Standard MOO server

This method of logging is controlled by $kahuna.standardlogging which must be set to 1. This method will log everything on the standard MOO server log file. This log file is defined when the server is started; usually with option -l (see the README file of the MOO server package). All lines concerning Aloha will have a CAPITAL ALOHA to identify themselves. A typical log from Aloha would look like:

Jan 1 19:51:38: > ALOHA: POST /97/submittest HTTP/1.0
Jan 1 19:51:38: > ALOHA: Referer: http://127.0.0.1:2222/97/test
Jan 1 19:51:38: > ALOHA: Connection: Keep-Alive
Jan 1 19:51:38: > ALOHA: User-Agent: Mozilla/4.08 [en] (X11; I; Linux 2.4.20-24.9 i686; Nav)
Jan 1 19:51:38: > ALOHA: Host: 127.0.0.1:2222
Jan 1 19:51:38: > ALOHA: Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */*
Jan 1 19:51:38: > ALOHA: Accept-Encoding: gzip
Jan 1 19:51:38: > ALOHA: Accept-Language: en
Jan 1 19:51:38: > ALOHA: Accept-Charset: iso-8859-1,*,utf-8
Jan 1 19:51:38: > ALOHA: Content-type: multipart/form-data; boundary=--------------1133921644773919629873420913
Jan 1 19:51:38: > ALOHA: Content-Length: 183
Jan 1 19:51:38: > ALOHA: ---------------1133921644773919629873420913
Jan 1 19:51:38: > ALOHA: Content-Disposition: form-data; name="username"
Jan 1 19:51:38: > ALOHA:
Jan 1 19:51:38: > ALOHA: this is a test
Jan 1 19:51:38: > ALOHA: ---------------1133921644773919629873420913-

However, the logs from Aloha will be mixed up with standard MOO log, obviously... which might make it hard to read, and/or time consuming to scan manually. A cheap way to extract them, could be:

less moo.log $\arrowvert$ grep " $>$ ALOHA:" $»$ aloha.log

where moo.log is your MOO server log file, and aloha.log will be the file into which all logs form Aloha will be saved into. Now, you can view only the log from the Web server using your favorite text editor, and opening aloha.log.
Again, even though $kahuna.standardlogging might be set to 1, logging will not occur if $kahuna.logging is set to 0.