i found a crash when umonitor try to read spam log
Program received signal SIGSEGV, Segmentation fault.
0x0000000000426989 in view_log (filename=0x7fffffff5940 "/sbbs/data/logs/spam.log", title=0x481346 "SPAM Log") at umonitor.c:414
414
read(buffile,buf,j);
Then, when i research and verify my config scfg->system->advance->logs,
i'm surprised to see that the value are ../data/
.
I update it to ../data/logs/ but now i have a /sbbs/data/logs/logs/ with
the http log and daily logs here
the sbbs.ini HttpLogFile are empty (as default)
Re: weird config logs dir error and umonitor crash
By: Ragnarok to DOVE-Net.Synchronet_Programming_C+ on Mon Dec 03 2018 03:36 am
i found a crash when umonitor try to read spam log
Program received signal SIGSEGV, Segmentation fault.
0x0000000000426989 in view_log (filename=0x7fffffff5940 "/sbbs/data/logs/spam.log", title=0x481346 "SPAM Log") at umonitor.c:414 414
read(buffile,buf,j);
How big is your spam.log file? It might be too big to put on the stack (but I would expect the alloca to fail in that case).
.
I update it to ../data/logs/ but now i have a /sbbs/data/logs/logs/ with the http log and daily logs here
Yeah, don't do that. Read the online help (F1 in SCFG) for that configuration setting.
Re: weird config logs dir error and umonitor crash
By: Digital Man to Ragnarok on Mon Dec 03 2018 12:57:57
Re: weird config logs dir error and umonitor crash
By: Ragnarok to DOVE-Net.Synchronet_Programming_C+ on Mon Dec 03 2018 03:36 am
i found a crash when umonitor try to read spam log
Program received signal SIGSEGV, Segmentation fault. 0x0000000000426989 in view_log (filename=0x7fffffff5940 "/sbbs/data/logs/spam.log", title=0x481346 "SPAM Log") at umonitor.c:414 414
read(buffile,buf,j);
How big is your spam.log file? It might be too big to put on the stack (but I would expect the alloca to fail in that case).
-rw------- 1 root root 8,3M dic 3 22:21 spam.log
can i put it on logrotate to perform a daily cleanup?
Sysop: | r00t |
---|---|
Location: | Newport Beach, CA |
Users: | 12 |
Nodes: | 6 (0 / 6) |
Uptime: | 231:46:29 |
Calls: | 144 |
Files: | 238 |
Messages: | 33,772 |