Forums » Suggestions
archive or append to errors.log files
..lots of times I'm a little slow on bugreporting, and my errors.log file has already been wiped by a subsequent log (often me troubleshooting the problem); is there a chance we could keep logs for more than one session, say five or so??
(I can just make a script to do it, but doesn't anyone else have this problem?)
..oh, and on a related note; can we get chat color-codes stripped out? "less" tries to open it in hexedit-mode
(I can just make a script to do it, but doesn't anyone else have this problem?)
..oh, and on a related note; can we get chat color-codes stripped out? "less" tries to open it in hexedit-mode
Plug it into logrotate? :P
the chat color codes already ARE stripped out, and it drives me insane trying to keep track of what's what.
Miharu's right... It was much easier to parse the logfile when the colors were in it. Of course, once the LUA is open, we can redirect different chat to different logs and that'll solve that problem.
okay, I'll think I'll hijack my own thread:
we want split logs!!!
( :D )
(**edit: I think I might remember something like that, Miharu, but my memory of alpha is pretty hazy at this point)
we want split logs!!!
( :D )
(**edit: I think I might remember something like that, Miharu, but my memory of alpha is pretty hazy at this point)
We used to have a multilog, but it was ingame-only... chat was split into 6 different "logs" while ingame, which meant a player could filter out a particular type of chat to watch just by selecting a particular log:
- System messages (ie, X killed Y, X had issues, etc.)
- Private messages (typing into that log sent messages back to the person who last messaged you without needing to type their name in or hit tab)
- Sector messages
- General (universal) messages
- Team messages (channel 11 now)
- Group messages
- System messages (ie, X killed Y, X had issues, etc.)
- Private messages (typing into that log sent messages back to the person who last messaged you without needing to type their name in or hit tab)
- Sector messages
- General (universal) messages
- Team messages (channel 11 now)
- Group messages
1) Open VO folder
2) Rename errors.log to something(anything) else
3) Play
I do this whenever I want to save a log, or am running a series of tournament matches in a night and need to log off midway.
2) Rename errors.log to something(anything) else
3) Play
I do this whenever I want to save a log, or am running a series of tournament matches in a night and need to log off midway.
Those of you who use OSX 10.4, I have an automator script that I could upload somewhere for you all, if there's demand. Only catch is that you have to remember to run the script when you quit.
Here's an OS X and linux bash script to do this for you (put it somewhere in your PATH):
#!/bin/sh
CURRDIR=`pwd`
# Path to the Vendetta directory (default is for Linux
VENDETTAPATH="${HOME}/.vendetta/"
# Default path to the OS X vendetta directory. Uncomment this for OS X
# VENDETTAPATH="/Applications/Vendetta.app"
cd $VENDETTAPATH
function mverror {
if [ -e errors.log ]
then
mv errors.log errors-`date +%Y-%m-%d_%R`.log
fi
}
mverror
if [ -e vendetta ]
then
exec ./update.rlb
elif [ -d Resources ]
then
cd ..
open "Vendetta.app"
else
then
echo "Erm...?"
fi
mverror
cd $CURRDIR
#!/bin/sh
CURRDIR=`pwd`
# Path to the Vendetta directory (default is for Linux
VENDETTAPATH="${HOME}/.vendetta/"
# Default path to the OS X vendetta directory. Uncomment this for OS X
# VENDETTAPATH="/Applications/Vendetta.app"
cd $VENDETTAPATH
function mverror {
if [ -e errors.log ]
then
mv errors.log errors-`date +%Y-%m-%d_%R`.log
fi
}
mverror
if [ -e vendetta ]
then
exec ./update.rlb
elif [ -d Resources ]
then
cd ..
open "Vendetta.app"
else
then
echo "Erm...?"
fi
mverror
cd $CURRDIR