mldonkey, a multi-networks file-sharing client - Bugs: bug #17094, Log file size's boundaries(size)...
You are not allowed to post comments on this tracker with your current authentication level.
bug #17094: Log file size's boundaries(size) have no effect.
| Submitter: | Fabiano <fabtar> | ||
| Submitted: | Thu 13 Jul 2006 08:06:16 AM UTC | ||
| Category: | Core | Severity: | 3 - Normal |
| Item Group: | Program malfunction | Status: | Wont Fix |
| Assigned to: | None | Open/Closed: | Closed |
| Release: | 2.7.7 | Release: | |
| Operating System: | Linux | Binaries Origin: | CVS / Self compiled |
| CPU type: | Intel x86 | ||
|
Sat 09 Sep 2006 06:14:34 PM UTC, comment #2: |
Rolf Leggewie <leggewie> |
|
Thu 13 Jul 2006 09:56:44 AM UTC, comment #1: log_size is only used if logging goes into RAM -> log_file = ""
|
spiralvoice <spiralvoice> |
|
Thu 13 Jul 2006 08:06:16 AM UTC, original submission:
I have noted that options:
|
Fabiano <fabtar> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
| Date | Changed by | Updated Field | Previous Value | => | Replaced by |
|---|---|---|---|---|---|
| 2006-07-13 | spiralvoice | Status | None | Wont Fix | |
| Open/Closed | Open | Closed |

Well, shouldn't it? My log is alread a quarter Gig after just about two days with another 10 to go before automatic restart.