No one with write rights to rclog.txt
 

Well that would be stupid as it would get so big and clogg the servers... but the fact that people can delete the log and write to it is pointless in its self. So something needs to be done... Any suggestions?

Its just stupid people can write to such an important log and people can just delete it.

When somebody writes to the log, isn't that write event logged?

Logs get so big after a certain time, that they need to be split. Someone needs write to it, so they can split it, for easy management.

yep.

Then how do people some how manage to delete the logs and leave behind nothing at all? It doesn't say the deleted it, it doesnt say they uploaded a file rclog.txt and it doesn't say that they wrote to it at all :\

Server can do that automatically.

I agree with this suggestion.

Perhaps individual rights for move/rename?

How?

People are stupid then...

Time: Tue Nov 4 21:14:18 2003
Jagen renamed file logs/rclog.txt to rclog_09042003.txt
Time: Tue Nov 4 21:14:19 2003
Jagen loaded file(s) from logs/

Time: Tue Nov 4 21:14:29 2003
Jagen deleted file logs/rclog.txt
Time: Tue Nov 4 21:14:30 2003
Jagen loaded file(s) from logs/

and if I try to upload a file called rclog.txt it does this:
Uploaded file logs/rclog.tx
(note the missing t)
EDIT:
this is a recent bug with the server... not sure what it'd do if it was overwritten though... I would assume it's logged though
ENDEDIT

If I open and save
Time: Tue Nov 4 21:16:50 2003
Jagen saved file logs/rclog.txt
Time: Tue Nov 4 21:16:51 2003
Jagen loaded file(s) from logs/

This really wouldn't be a problem if managers were responsible and smart enough not to give rw rclog.txt rights out.

I'm not too keen on the subject, but didn't Stefan add a feature to subtract rights? Or was that just for the NPC server?

Stefan did make that subtract right. I think he made it especially for levels.

Actually False, If you delete the log twice fast. It wont recreate till the next action is taken, So no log of the log being deleted. :)

Is it a good idea to tell everybody about that? x_x

Yes, but it should be told to Stefan. :)

I have a suggestion. Logs are not in file browser, well, they are, but not accessed from there. In the server options there should be a varible like, rclog=account1,account2, etc...

This will give high admins added into there access to a buttion which displays the logs. The logs are dated and changed once a week, so displaying them would not lag ones computer with a ton of text. But the logs would have to be rescripted so that they don't go off the window, and so it easier to read.

Mabey something like that? :)

Nope. Nor was Jagens, if it was all true.

I believe the rclog shouldn't be taken seriously in matters that need to be handled by anybody higher than a server manager if there is even a remote chance it could have been edited.

Perhaps there had ought to be an uneditable version per server uploaded to a global directory or some such?

I do like that account-specific idea though, would make it easier for people to check up on exactly how much their staff are working or maybe who carried out what action.

Final thought -
I think it would be ideal to have a new window like the accounts list that lets you search for an action or account or time/date etc. Listing the results processed from the raw data in the log file, an uneditable log preferably.
To avoid it getting too big maybe a 30 day limit to how long actions are kept in the file?

That is why this thread came into existence, Sir.

How about if rclog.txt is greater than 4 megabytes, rename RClog automatically(name it the date, like 090403.txt or whatever). Then all will be well in the world of Ivalice.

Actually I think it could even be .tgz'ed, too, and only the most recent log entries of, dunno, the last month or the last few hundred kilobytes need to be available in plain text.
Perhaps the log handling could be done more `behind the scenes', using a database thingie and having some kind of scripted interface.

Four megabytes, yeah. That'd take me just under an hour to download.

What I did is every first of the month I renamed the log to that past month so it would start a new one. This kept the log small and easier to deal with when it became nessary to look something up, if you knew the month it occurred in ( and year because I put month and year) it is much easier to find. So I suggest the log starts over each month, and names the last log for the month and year it was logged in. A text log of 4 megs is huge and very hard to find something in and I suggest a much smaller log so you don't spend hours looking for something.

... before it's cut off and a new file made.

Kinda what i was getting at there

Not if you upload it.

I didn't know that servers parsed the logs after they got so big. Our gralatlog.txt got over 3megabytes, before I got around to saving it in the oldlogs.

I meant to say that it is possible to code the server to do so.

I know and I agree with you.. ;) I just didn't see that till after I posted ..*shrugs*

Well, now that we're all in agreement maybe this can actually influence something in the new RC being scripted? *prods Jagen*

Yes, certainly, as the RC is the program in charge of managing logs.

logs/*
 

I say only managers...not admins managers....get rw logs/*.....admins get r logs/*