Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Synchronet Multinode BBS Softwar...  <--  <--- Return to Home Page
   Networked Database  Synchronet Multinode BBS Softwar...   [782 / 900] RSS
 From   To   Subject   Date/Time 
Message   Digital Man    Jeff Smith   Echocfg Error?   June 18, 2019
 2:27 PM *  

  Re: Echocfg Error?
  By: Jeff Smith to Digital Man on Sun Jun 16 2019 07:58 pm

 > Hello Digital Man,
 >
 > > A backtrace from that core dump might be very helpful:
 > > http://wiki.synchro.net/howto:gdb
 > > You might also try running echocfg in one of the other '-i' modes (e.g.
 > > -is) and see if that avoid the issues.
 >
 > Ok... Here's a wierd one. I stopped the sbbs daemon. As suggested I edited
 > the sbbs file in /etc/init.d and uncommented the "ulimit -c unlimited" line.
 > I then added the following lines to the /etc/sysctl.conf file.
 >
 > # Controls whether core dumps will append the PID to the core filename.
 > # Useful for debugging multi-threaded applications.
 > kernel.core_uses_pid = 1
 > kernel.core_pattern = /tmp/core.%e.%p
 >
 > I then restarted the sbbs daemon. I then loaded ./echocfg which loaded ok.
 > Then exited echocfg and got no errors or faults. I then stopped the sbbs
 > daemon and commented out the "ulimit -c unlimited" line and restarted the
 > sbbs daemon. I reloaded and exited ./echocfg with no errors or faults. I
 > then stopped the daemon again and commented out the "kernel.core_uses_pid =
 > 1"  and "kernel.core_pattern = /tmp/core.%e.%p" line. Then restarted the
 > sbbs daemon again and loaded ./echocfg once again. Upon exiting I got the
 > following response
 >
 >
 > sbbs@bbs5:~/exec$ ./echocfg
 > ---------------------------------------------------------------------------
 > Synchronet FidoNet Configuration  Version 3.06  Copyright 2019 Rob Swindell
 >
 > XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
 >       after 173 requests (173 known processed) with 0 events remaining.
 > ---------------------------------------------------------------------------
 >
 > I did try the various display modes and none seemed to generate and errors.

So changing max core size (ulimit -c) for the sbbs daemon won't have any effect
 on the max core size for programs that you run from bash (echocfg).

Anyway, if you run echocfg from gdb and get a backtrace from the crash, please
share.

                                            digital man

This Is Spinal Tap quote #9:
David St. Hubbins: I mean, it's not your job to be as confused as Nigel.
Norco, CA WX: 72.8°F, 65.0% humidity, 5 mph ENE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.07-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Synchronet Multinode BBS Softwar...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0941 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_eo0s0958u92h3hb26tg7nt29p2, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_eo0s0958u92h3hb26tg7nt29p2, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_eo0s0958u92h3hb26tg7nt29p2, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0