log files grow steadily and eventually eat disk space or slow down file operations. set up a routine to archive or trim them on a regular schedule. keep enough history to troubleshoot, but not so much that the drive suffers. a little rotation goes a long way
sounds like synchronet has a good system - less to think aboutlog files grow steadily and eventually eat disk space or slow down file operations. set up a routine to archive or trim them on a regular sched keep enough history to troubleshoot, but not so much that the drive suf a little rotation goes a long way
Synchronet logs everything into one place as standard, but it's easy to separate out the different services into their own logfiles on Linux. I have lots of term, mail, ftp. mail, events, web, services, and then the catchall for everything else. ircd creates its own log since I run it standalone rather as part of services.
Logrotation is easy after that.
Synchronet logs everything into one place as standard, but it's easy to separate out the different services into their own logfiles on Linux. I have lots of term, mail, ftp. mail, events, web, services, and then the catchall for everything else. ircd creates its own log since I run it standalone rather as part of services.
Logrotation is easy after that.sounds like synchronet has a good system - less to think about
| Sysop: | Mojo |
|---|---|
| Location: | Jasckson, Michigan |
| Users: | 10 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 498471:00:49 |
| Calls: | 100 |
| Calls today: | 1 |
| Files: | 10,063 |
| D/L today: |
7 files (90K bytes) |
| Messages: | 25,972 |