View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001408 | unreal | ircd | public | 2003-12-04 23:10 | 2003-12-13 22:13 |
| Reporter | capitaine | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Summary | 0001408: Keep logs | ||||
| Description | I tried to set Log::maxsize <max-file-size> but since our traffic is not predictable, I find it not very useful. If would be very nice to have a Log::keeplogs <time> Example : logs { keeplogs 60D; ...... } Anyway thanks you ! | ||||
| 3rd party modules | |||||
|
|
Err... this may be irrelevant... But what would happen if you got absolutly FLOODED with connects, etc... your logs would grow to an astronomical size, possibly utilising all the HD space..? That is not good. Would'nt it just make more sense to set a higher logsize than you think you will ever need, but smaller than your HD? My two cents as ever... ;) |
|
|
Well, I haven't said I would like the Log::maxsize beeing suppressed. Sure, it's useful for big networks anyway. |
|
|
My point is that having a logtime expire would be useless and hard to code... Make that four cents ;) |
|
|
I agree that keeping logs for legal reasons, like 2 months or more, is useless. But, I don't know very much about C, and if it's hard to code, let's close the case. Thanks you anyway. |
|
|
Ok perhaps I should comment on this. From my personal experience I know it's better (safer!) to have fixed sizes than to use days (if you've done nt/w2k eventlog sysadmin stuff you'll know why), for example if you got limited hd space, or more likely limited quota.. then you'll run into huge problems if you eat all your space... But... for some people this _can_ be useful, so it's worth looking at... I haven't worked much (eh not at all) with the logging code, but it doesn't seem too hard to code either... just a stat() call to get the creation time of the logfile and do some calculations. |
|
|
I dunno, seems kinda like this is more a job for a cron script type thing to me. |
|
|
You're right. Size has to be checked. For the crontab, yes I think so too. It's not revelant to include that in the core server. It may be a module in the future. |
|
|
ok well.. then I'll just close it. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-12-04 23:10 | capitaine | New Issue | |
| 2003-12-04 23:53 | w00t | Note Added: 0004206 | |
| 2003-12-05 10:37 | capitaine | Note Added: 0004212 | |
| 2003-12-08 01:42 | w00t | Note Added: 0004243 | |
| 2003-12-10 19:43 | capitaine | Note Added: 0004281 | |
| 2003-12-11 18:39 | syzop | Note Added: 0004309 | |
| 2003-12-11 18:57 |
|
Note Added: 0004310 | |
| 2003-12-13 18:38 | capitaine | Note Added: 0004327 | |
| 2003-12-13 22:13 | syzop | Status | new => closed |
| 2003-12-13 22:13 | syzop | Note Added: 0004332 |
