1. Forum
  2. DOVE-Net
  3. Synchronet JavaScript

  • Javascript TW2

    From Dumas Walker@VERT/CAPCITY2 to ALL on Sat Dec 30 11:05:00 2017
    Good morning,I am attempting to get the JS version of TW2 up and running withSynchronet. Using the directions in the SYSOP.TXT file, I run thefollowing command:/sbbs/exec/jsexec /sbbs/xtrn/tw2/twint500.jsThat pops open a window with a blue-and-yellow screen, similar to SCFG,that says TradeWars 2 Initialization at the top left, and the date & timeat the top right. The only thing in the middle of the screen is a very smallblue-and-yellow box. There are no options listed in the box. The onlything I can do on that screen is press ESC twice to exit.Shouldn't there be some options in there? :)From the output in the lxterminal window, I am running JSexec v3.17a-Linux(rev 1.184) Compiled Nov 4 2017 13:52:09 with GCC 6.3.0; JavaScript-C 1.8.52011-03-31. JSON client is v1.29.Thanks!--- SLMR 2.1a "Get out & take your Sacagawea dollars with you!" - Moe Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Digital Man@VERT to Dumas Walker on Sat Dec 30 11:34:33 2017
    Re: Javascript TW2 By: Dumas Walker to ALL on Sat Dec 30 2017 11:05 am > Good morning, > I am attempting to get the JS version of TW2 up and running with > Synchronet. Using the directions in the SYSOP.TXT file, I run the > following command: > > /sbbs/exec/jsexec /sbbs/xtrn/tw2/twint500.js > > That pops open a window with a blue-and-yellow screen, similar to SCFG, > that says TradeWars 2 Initialization at the top left, and the date & time > at the top right. The only thing in the middle of the screen is a very small > blue-and-yellow box. There are no options listed in the box. The only > thing I can do on that screen is press ESC twice to exit. > > Shouldn't there be some options in there? :) > > From the output in the lxterminal window, I am running JSexec v3.17a-Linux > (rev 1.184) Compiled Nov 4 2017 13:52:09 with GCC 6.3.0; JavaScript-C 1.8.5 > 2011-03-31. JSON client is v1.29.The problem you're describing was fixed on Nov-17:http://cvs.synchro.net/cgi-bin/viewcvs.cgi/src/sbbs3/js_uifc.cSo you just need to cvs-update and recompile. :-) digital manSynchronet "Real Fact" #93:Synchronet v3.16c was released in August of 2015 (5 years after v3.15b).Norco, CA WX: 72.3F, 25.0% humidity, 0 mph WNW wind, 0.00 inches rain/24hrs--- Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From echicken@VERT/ECBBS to Dumas Walker on Sat Dec 30 14:13:09 2017
    Re: Javascript TW2 By: Dumas Walker to ALL on Sat Dec 30 2017 11:05:00 DW> That pops open a window with a blue-and-yellow screen, similar to SCFG, DW> that says TradeWars 2 Initialization at the top left, and the date & time DW> at the top right. The only thing in the middle of the screen is a very DW> small blue-and-yellow box. There are no options listed in the box. The DW> only thing I can do on that screen is press ESC twice to exit.If I recall correctly, some breaking changes were made to the UIFC API forjavascript a few years ago. Sounds like this script is a victim of that, andit will need to be fixed. Probably not much a user (sysop) can do to workaround it, unless the game offers some kind of non-interactive setup process.---echickenelectronic chicken bbs - bbs.electronicchicken.com - 416-273-7230 Synchronet electronic chicken bbs - bbs.electronicchicken.com
  • From Al@VERT/TRMB to Dumas Walker on Sat Dec 30 13:49:38 2017
    Re: Javascript TW2 By: Dumas Walker to ALL on Sat Dec 30 2017 11:05 am DW> I am attempting to get the JS version of TW2 up and running with DW> Synchronet. Using the directions in the SYSOP.TXT file, I run the DW> following command: DW> /sbbs/exec/jsexec /sbbs/xtrn/tw2/twint500.jsI added a section to ctrl/json-service.ini with..[tw2]dir=../xtrn/tw2/and that seems to have gotten me past this.. Ttyl :-), Al... My opinions are my own; mistakes are the computer's fault.--- Synchronet The Rusty MailBox - Penticton, BC Canada - trmb.synchro.net
  • From Dumas Walker@VERT/CAPCITY2 to DIGITAL MAN on Sun Dec 31 18:57:00 2017
    The problem you're describing was fixed on Nov-17:> http://cvs.synchro.net/cgi-bin/viewcvs.cgi/src/sbbs3/js_uifc.c> So you just need to cvs-update and recompile. :-)I still have the same issue, but it takes approx 1 minute to open theunpopulated TradeWars 2 Initialization window, where it was prettyinstantaneous before.That could be because if I follow the cvs update directions on the wiki, Ieventually get to this step:cd /sbbs/src/sbbs3; make RELEASE=1 symlinksAnd get the following error:make: *** No rule to make target 'symlinks'. Stop.If I replace symlinks with install, it says there is nothing for it to do.The next step gives the same "no rule" error. The other steps all appearedto do what they were supposed to, although it was not much.The comments in my copy of js_uifc.c are now dated 2017/11/17 10:03:07, soit does look like I have an updated copy, FWIW.--- SLMR 2.1a In his hand a moving picture of the crumbling land Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Dumas Walker@VERT/CAPCITY2 to AL on Sun Dec 31 18:58:00 2017
    I added a section to ctrl/json-service.ini with..> [tw2]> dir=../xtrn/tw2/> and that seems to have gotten me past this..I tried that, too. No improvements on this end. :)--- SLMR 2.1a How can I escape this irresistable grasp? Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Dumas Walker@VERT/CAPCITY2 to ECHICKEN on Sun Dec 31 18:59:00 2017
    If I recall correctly, some breaking changes were made to the UIFC API for>javascript a few years ago. Sounds like this script is a victim of that, and>it will need to be fixed. Probably not much a user (sysop) can do to work>around it, unless the game offers some kind of non-interactive setup process.That would be nice. I much rather prefer editing an INI or CFG file overhaving a script or program build it for me. If it came with an example ofeither, I don't see them.--- SLMR 2.1a Tongue-tied & twisted, just an Earth-bound misfit, I! Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Digital Man@VERT to Dumas Walker on Sun Dec 31 16:55:21 2017
    Re: Javascript TW2 By: Dumas Walker to DIGITAL MAN on Sun Dec 31 2017 06:57 pm > > The problem you're describing was fixed on Nov-17: > > http://cvs.synchro.net/cgi-bin/viewcvs.cgi/src/sbbs3/js_uifc.c > > > So you just need to cvs-update and recompile. :-) > > I still have the same issue, but it takes approx 1 minute to open the > unpopulated TradeWars 2 Initialization window, where it was pretty > instantaneous before. > > That could be because if I follow the cvs update directions on the wiki, I > eventually get to this step: > > cd /sbbs/src/sbbs3; make RELEASE=1 symlinks > > And get the following error: > > make: *** No rule to make target 'symlinks'. Stop.Did you run "cvs update" before that? That sounds like you don't have thelatest src/sbbs3/GNUmakefile. > If I replace symlinks with install, it says there is nothing for it to do. > The next step gives the same "no rule" error. The other steps all appeared > to do what they were supposed to, although it was not much. > > The comments in my copy of js_uifc.c are now dated 2017/11/17 10:03:07, so > it does look like I have an updated copy, FWIW.And when you run jsexec, what does it say the build date is? digital manThis Is Spinal Tap quote #36:Bobbi Flekman: Money talks, and bullshit walks.Norco, CA WX: 63.3F, 49.0% humidity, 0 mph ESE wind, 0.00 inches rain/24hrs--- Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From echicken@VERT/ECBBS to Dumas Walker on Sun Dec 31 21:49:11 2017
    Re: Javascript TW2 By: Dumas Walker to ECHICKEN on Sun Dec 31 2017 18:59:00 DW> That would be nice. I much rather prefer editing an INI or CFG file over DW> having a script or program build it for me. If it came with an example of DW> either, I don't see them.Seems I was wrong about the UIFC problems - DM indicated that they've beenfixed. The initialization script seems to work fine on my system. You'll needto resolve your problems with building the latest source before you can run it.I don't know if the initialization script just generates config files or if itoperates directly on the game's JSON database. In any case there appear to beless than twenty settings to configure, so it shouldn't be tedious to use onceyou get it going.---echickenelectronic chicken bbs - bbs.electronicchicken.com - 416-273-7230 Synchronet electronic chicken bbs - bbs.electronicchicken.com
  • From echicken@VERT/ECBBS to Dumas Walker on Sun Dec 31 21:51:22 2017
    Re: Javascript TW2 By: Dumas Walker to AL on Sun Dec 31 2017 18:58:00 >> I added a section to ctrl/json-service.ini with.. >> [tw2] >> dir=../xtrn/tw2/ >> and that seems to have gotten me past this.. DW> I tried that, too. No improvements on this end. :)That's an important step nevertheless, so keep those lines in place in yourjson-service.ini file. This tells your local JSON-DB server to host a 'tw2'module, and the game's configuration script will want to access that modulewhen it does its thing.---echickenelectronic chicken bbs - bbs.electronicchicken.com - 416-273-7230 Synchronet electronic chicken bbs - bbs.electronicchicken.com
  • From Accession@VERT/PHARCYDE to Dumas Walker on Mon Jan 1 00:23:58 2018
    Hello Dumas,On Sun Dec 31 2017 18:57:00, Dumas Walker wrote to DIGITAL MAN: DW> That could be because if I follow the cvs update directions on the DW> wiki, I eventually get to this step: DW> cd /sbbs/src/sbbs3; make RELEASE=1 symlinks DW> And get the following error: DW> make: *** No rule to make target 'symlinks'. Stop.As far as I know, you don't need to run symlinks or SYMLINK=1 or whatever it is unless you're installing for the first time. After that, the symlinks are already there, unless you go from a RELEASE build to a DEBUG build. DW> If I replace symlinks with install, it says there is nothing for it to DW> do. The next step gives the same "no rule" error. The other steps all DW> appeared to do what they were supposed to, although it was not much.Depending on what you want to accomplish, if you just want a release build, "make" should do just fine. If you want DOSEMU support, "make USE_DOSEMU=1" is good.. Check the wiki, there is only a mention of SYMLINK when you're installing for the first time. Scroll down a bit and you'll see the "Upgrading" section.Regards,Nick... "Не знаю. Я здесь только работаю."--- GoldED+/LNX 1.1.5-b20170303 * Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1) Synchronet thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
  • From Dumas Walker@VERT/CAPCITY2 to DIGITAL MAN on Mon Jan 1 17:58:00 2018
    That could be because if I follow the cvs update directions on the wiki, I> > eventually get to this step:> >> > cd /sbbs/src/sbbs3; make RELEASE=1 symlinks> >> > And get the following error:> >> > make: *** No rule to make target 'symlinks'. Stop.> Did you run "cvs update" before that? That sounds like you don't have the> latest src/sbbs3/GNUmakefile.I ran the following, from the wiki:export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbscvs update -d execcvs update -d src 3rdpThen I ran the step quoted above.> And when you run jsexec, what does it say the build date is?JSexec v3.17a-Linux (rev 1.184)Compiled Nov 4 2017 13:52:09 with GCC 6.3.0GNUmakefile in /src/sbbs3 is dated November 26, 2015, which sounds wrong forsure.Thanks!--- SLMR 2.1a My grubby halo, a vapour trail in the empty air... Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Dumas Walker@VERT/CAPCITY2 to ECHICKEN on Mon Jan 1 17:41:00 2018
    That's an important step nevertheless, so keep those lines in place in your> json-service.ini file. This tells your local JSON-DB server to host a 'tw2'> module, and the game's configuration script will want to access that module> when it does its thing.Thanks to you and Al. I will keep them in there as they were not therebefore.--- SLMR 2.1a A restless eye across a weary room... Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Dumas Walker@VERT/CAPCITY2 to ACCESSION on Mon Jan 1 17:44:00 2018
    Depending on what you want to accomplish, if you just want a release build,>"make" should do just fine. If you want DOSEMU support, "make USE_DOSEMU=1" is>good.. Check the wiki, there is only a mention of SYMLINK when you're>installing for the first time. Scroll down a bit and you'll see the "Upgrading">section.When I am looking at:http://wiki.synchro.net/install:nixThe Updating section shows symlinks on the make lines, on Step 4 parts 1and 2.Maybe we are looking at different pages? :D--- SLMR 2.1a A momentary lapse of reason that binds a life to a life.. Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Digital Man@VERT to Dumas Walker on Mon Jan 1 15:06:09 2018
    Re: Javascript TW2 By: Dumas Walker to DIGITAL MAN on Mon Jan 01 2018 05:58 pm > > > That could be because if I follow the cvs update directions on the > > > wiki, I eventually get to this step: > > > > cd /sbbs/src/sbbs3; make RELEASE=1 symlinks > > > > And get the following error: > > > > make: *** No rule to make target 'symlinks'. Stop. > > Did you run "cvs update" before that? That sounds like you don't have the > > latest src/sbbs3/GNUmakefile. > > I ran the following, from the wiki: > > export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs > cvs update -d exec > cvs update -d src 3rdp > > Then I ran the step quoted above. > > > And when you run jsexec, what does it say the build date is? > > JSexec v3.17a-Linux (rev 1.184) > Compiled Nov 4 2017 13:52:09 with GCC 6.3.0Okay, that means it hasn't been built since Nov-4-2017, so it won't include thefix for JS uifc. > GNUmakefile in /src/sbbs3 is dated November 26, 2015, which sounds wrong for > sure.No, actually that's correct:http://cvs.synchro.net/cgi-bin/viewcvs.cgi/src/sbbs3/GNUmakefile?view=logWhat's likely happening is that the jsexec you're running is not the latest oneyou built. If you run "locate jsexec" on your system, it should report to allof the files named "jsexec" on your file system. My guess is, you have morethan one.When you run jsexec, are you typing the absolute path (e.g. /sbbs/exec/jsexec)or just letting your PATH pick the one to run? If you type "which jsexec",it'll tell you which one is running (if any) if you just type "jsexec" withoutthe path.My guess is that either the jsexec that's in your path is an old one or you'respecifying the path to /sbbs/exec/jsexec which is an old one. Or maybe it's asymlink to src/sbbs3/gcc.linux.exe.debug/jsexec but you built a release binarywhen you ran make (or vice versa).I know this seems like a lot of hassle just to run a door game, but you shouldget a handle on how you can can update sbbs (including jsexec) and actuallybenefit from those updates. :-) digital manSynchronet "Real Fact" #61:How to get Synchronet technical support: http://wiki.synchro.net/howto:supportNorco, CA WX: 73.7F, 27.0% humidity, 0 mph NNE wind, 0.00 inches rain/24hrs--- Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Accession@VERT/PHARCYDE to Dumas Walker on Mon Jan 1 19:26:38 2018
    Hello Dumas,On Mon Jan 01 2018 17:44:00, Dumas Walker wrote to ACCESSION: DW> When I am looking at: DW> http://wiki.synchro.net/install:nix DW> The Updating section shows symlinks on the make lines, on Step 4 parts DW> 1 and 2. DW> Maybe we are looking at different pages? :DNope. Same page. That must have been something added recently, as I've never seen or used "symlinks" on those lines before.The only time I use SYMLINK=1 is when compiling for the first time, or changing between a RELEASE build and a DEBUG build, which I also haven't done for quite some time, so I haven't needed to redo symlinks in a long time. Once they're created for the first time, they don't go away unless you delete them. ;)Regards,Nick... "Не знаю. Я здесь только работаю."--- GoldED+/LNX 1.1.5-b20170303 * Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1) Synchronet thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
  • From Al@VERT/TRMB to Accession on Mon Jan 1 21:39:21 2018
    Re: Javascript TW2 By: Accession to Dumas Walker on Mon Jan 01 2018 07:26 pm Ac> Nope. Same page. That must have been something added recently, as I've Ac> never seen or used "symlinks" on those lines before.I think it has been. I recently updated the BBS and I used symlinks on thecommand line as the wiki said and everything went smoothly here..Happy New Year, BTW.. :) Ttyl :-), Al... Reality is for those who can't handle computers.--- Synchronet The Rusty MailBox - Penticton, BC Canada - trmb.synchro.net
  • From Digital Man@VERT to Accession on Mon Jan 1 23:42:11 2018
    Re: Javascript TW2 By: Accession to Dumas Walker on Mon Jan 01 2018 07:26 pm > Hello Dumas, > > On Mon Jan 01 2018 17:44:00, Dumas Walker wrote to ACCESSION: > > DW> When I am looking at: > > DW> http://wiki.synchro.net/install:nix > > DW> The Updating section shows symlinks on the make lines, on Step 4 parts > DW> 1 and 2. > > DW> Maybe we are looking at different pages? :D > > Nope. Same page. That must have been something added recently, as I've never > seen or used "symlinks" on those lines before.Yes, pretty new:http://cvs.synchro.net/cgi-bin/viewcvs.cgi/src/sbbs3/targets.mk > The only time I use SYMLINK=1 is when compiling for the first time, or > changing > between a RELEASE build and a DEBUG build, which I also haven't done for > quite some time, so I haven't needed to redo symlinks in a long time. Once > they're created for the first time, they don't go away unless you delete > them. ;)Right, but when people switch between release and debug builds or copies andsymlinks, those new targets can come in handy. digital manSynchronet/BBS Terminology Definition #18:DSZ = DOS Send ZMODEM (by Chuck Forsberg)Norco, CA WX: 55.9F, 72.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs--- Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Accession@VERT/PHARCYDE to Al on Tue Jan 2 08:24:36 2018
    Hello Al,On Mon Jan 01 2018 21:39:20, Al wrote to Accession: Ac>> Nope. Same page. That must have been something added recently, as Ac>> I've never seen or used "symlinks" on those lines before. Al> I think it has been. I recently updated the BBS and I used symlinks on Al> the command line as the wiki said and everything went smoothly here..I recently (within the past week) went about installing/compiling new on new hardware using SYMLINK=1 in my make line and migrating over all my configuration and customizations. This also worked. However, after doing that I've upgraded a couple times now since (for new sbbslist.js updates) and didn't need any reference to symlinks on those lines. Al> Happy New Year, BTW.. :)And same to you! Starting off the year below 0F with windchills that make you feel like your fingers and face are going to burn off. It's lovely! ;(Regards,Nick... "Не знаю. Я здесь только работаю."--- GoldED+/LNX 1.1.5-b20170303 * Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1) Synchronet thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
  • From Accession@VERT/PHARCYDE to Digital Man on Tue Jan 2 08:28:02 2018
    Hello Digital,On Mon Jan 01 2018 23:42:10, Digital Man wrote to Accession: >> The only time I use SYMLINK=1 is when compiling for the first time, >> or changing between a RELEASE build and a DEBUG build, which I also >> haven't done for quite some time, so I haven't needed to redo >> symlinks in a long time. Once they're created for the first time, >> they don't go away unless you delete them. ;) DM> Right, but when people switch between release and debug builds or DM> copies and symlinks, those new targets can come in handy.So does "SYMLINK=1" and "symlinks" effectively do the same thing then? If so, we're accomplishing the same goal just in different (yet similar) ways. ;)Regards,Nick... "Не знаю. Я здесь только работаю."--- GoldED+/LNX 1.1.5-b20170303 * Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1) Synchronet thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
  • From Digital Man@VERT to Accession on Tue Jan 2 16:34:27 2018
    Re: Javascript TW2 By: Accession to Digital Man on Tue Jan 02 2018 08:28 am > Hello Digital, > > On Mon Jan 01 2018 23:42:10, Digital Man wrote to Accession: > > >> The only time I use SYMLINK=1 is when compiling for the first time, > >> or changing between a RELEASE build and a DEBUG build, which I also > >> haven't done for quite some time, so I haven't needed to redo > >> symlinks in a long time. Once they're created for the first time, > >> they don't go away unless you delete them. ;) > > DM> Right, but when people switch between release and debug builds or > DM> copies and symlinks, those new targets can come in handy. > > So does "SYMLINK=1" and "symlinks" effectively do the same thing then? If > so, we're accomplishing the same goal just in different (yet similar) ways. > ;)They're 2 different makefiles. The install/GNUmakefile (where SYMLINK=1 optionmay be used) is normally only used for the initial install. Thesrc/sbbs3/GNUmakefile is used for building sbbs (and lot of the libraries andutilities) and now has "install" and "symlinks" targets. You don't need torecreate symlinks if they already exist and point where you want them to (butyou already knew that). :-) digital manThis Is Spinal Tap quote #40:Morty the Mime: Come on, don't talk back, mime is money, come on, move it.Norco, CA WX: 76.2F, 20.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs--- Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Accession@VERT/PHARCYDE to Digital Man on Tue Jan 2 20:32:24 2018
    Hello Digital,On Tue Jan 02 2018 16:34:26, Digital Man wrote to Accession: >> So does "SYMLINK=1" and "symlinks" effectively do the same thing >> then? If so, we're accomplishing the same goal just in different >> (yet similar) ways. ;) DM> They're 2 different makefiles. The install/GNUmakefile (where DM> SYMLINK=1 option may be used) is normally only used for the initial DM> install. The src/sbbs3/GNUmakefile is used for building sbbs (and lot DM> of the libraries and utilities) and now has "install" and "symlinks" DM> targets. You don't need to recreate symlinks if they already exist and DM> point where you want them to (but you already knew that). :-)Ah ok. I was just making sure I wasn't going crazy, then. ;)Regards,Nick... "Не знаю. Я здесь только работаю."--- GoldED+/LNX 1.1.5-b20170303 * Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1) Synchronet thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
  • From Dumas Walker@VERT/CAPCITY2 to DIGITAL MAN on Wed Jan 3 18:51:00 2018
    JSexec v3.17a-Linux (rev 1.184)>> Compiled Nov 4 2017 13:52:09 with GCC 6.3.0>Okay, that means it hasn't been built since Nov-4-2017, so it won't include the>fix for JS uifc.>What's likely happening is that the jsexec you're running is not the latest one>you built. If you run "locate jsexec" on your system, it should report to all>of the files named "jsexec" on your file system. My guess is, you have more>than one.You are right, but:/opt/sbbs/exec/jsexec/opt/sbbs/src/sbbs3/gcc.linux.exe.release/jsexec/sbbs/exec/jsexec/sbbs/src/sbbs3/gcc.linux.exe.release/jsexecThose first two are old, from 2009, and are from a backup of a previousinstallation. The last two are a symlink and an actual build, fromNovember 4, 2017. I do not appear to have one more recent. I have triedrunning both "jsexec" and "/sbbs/exec/jsexec" during my attempts.>When you run jsexec, are you typing the absolute path (e.g. /sbbs/exec/jsexec)>or just letting your PATH pick the one to run? If you type "which jsexec",>it'll tell you which one is running (if any) if you just type "jsexec" without>the path.I get no output from "which jsexec".>My guess is that either the jsexec that's in your path is an old one or you're>specifying the path to /sbbs/exec/jsexec which is an old one. Or maybe it's a>symlink to src/sbbs3/gcc.linux.exe.debug/jsexec but you built a release binary>when you ran make (or vice versa).Apparently I did not build one when I ran make. :)>I know this seems like a lot of hassle just to run a door game, but you should>get a handle on how you can can update sbbs (including jsexec) and actually>benefit from those updates. :-)Yes, I would like to get a handle on that, especially since I seem to havedifficulty with it. Since you did not mention it, I am assuming that Ishould be following the directions, as stated, on the UNIX install wiki pageunder the "Updating" heading? That is what I have been trying.Thanks for you assistance!on edit: decided to try something on my own. I split the line:cd /sbbs/src/sbbs3; make RELEASE=1 symlinksinto:cd /sbbs/src/sbbs3make RELEASE=1 symlinksStill got the "symlinks" error. So I ran "make RELEASE=1" in the/sbbs/src/sbbs3 directory without "symlinks". Well, that caused *something*to happen! It ran 10-15 minutes, compiling this and that, befure ending withthis new error:make: *** No rule to make target 'base64.h', needed by'gcc.linux.obj.release-mt/ js_file.o'. Stop.If you get this message, I didn't plumb break it. :D I also still have aNovember 4 version of jsexec, unfortunately.--- SLMR 2.1a He knows changes aren't permanent - but change is! Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Dumas Walker@VERT/CAPCITY2 to ACCESSION on Wed Jan 3 18:17:00 2018
    Maybe we are looking at different pages? :D>The only time I use SYMLINK=1 is when compiling for the first time, or changing>between a RELEASE build and a DEBUG build, which I also haven't done for quite>some time, so I haven't needed to redo symlinks in a long time. Once they're>created for the first time, they don't go away unless you delete them. ;)Thanks. The symlinks still appear to be there. I'd be in a heap of hurtif they were not. :D--- SLMR 2.1a Wind in my hair - shifting and drifting... Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Digital Man@VERT to Dumas Walker on Wed Jan 3 17:30:32 2018
    Re: Javascript TW2 By: Dumas Walker to DIGITAL MAN on Wed Jan 03 2018 06:51 pm > >you built. If you run "locate jsexec" on your system, it should report to > all >of the files named "jsexec" on your file system. My guess is, you have > more >than one. > > You are right, but: > > /opt/sbbs/exec/jsexec > /opt/sbbs/src/sbbs3/gcc.linux.exe.release/jsexec > /sbbs/exec/jsexec > /sbbs/src/sbbs3/gcc.linux.exe.release/jsexec > > Those first two are old, from 2009, and are from a backup of a previous > installation. The last two are a symlink and an actual build, from > November 4, 2017. I do not appear to have one more recent. I have tried > running both "jsexec" and "/sbbs/exec/jsexec" during my attempts.Well if you don't have a recent build, then it doesn't really matter which oneyou run. > >When you run jsexec, are you typing the absolute path (e.g. > /sbbs/exec/jsexec) >or just letting your PATH pick the one to run? If you > type "which jsexec", >it'll tell you which one is running (if any) if you > just type "jsexec" without >the path. > > I get no output from "which jsexec".Then jsexec is not in your search path (which is fine). > >My guess is that either the jsexec that's in your path is an old one or > you're >specifying the path to /sbbs/exec/jsexec which is an old one. Or > maybe it's a >symlink to src/sbbs3/gcc.linux.exe.debug/jsexec but you built > a release binary >when you ran make (or vice versa). > > Apparently I did not build one when I ran make. :) > > >I know this seems like a lot of hassle just to run a door game, but you > should >get a handle on how you can can update sbbs (including jsexec) and > actually >benefit from those updates. :-) > > Yes, I would like to get a handle on that, especially since I seem to have > difficulty with it. Since you did not mention it, I am assuming that I > should be following the directions, as stated, on the UNIX install wiki page > under the "Updating" heading? That is what I have been trying.Okay, yes, that's correct. > Thanks for you assistance!No problem. > on edit: decided to try something on my own. I split the line: > > cd /sbbs/src/sbbs3; make RELEASE=1 symlinks > > into: > > cd /sbbs/src/sbbs3 > make RELEASE=1 symlinks > > Still got the "symlinks" error.Then you're missing an update. What was the "cvs update" command you ran whenyou updated?It sounds like you're missing rev 1.42 of src/sbbs3/targets.mk > So I ran "make RELEASE=1" in the > /sbbs/src/sbbs3 directory without "symlinks". Well, that caused *something* > to happen! It ran 10-15 minutes, compiling this and that, befure ending > with this new error: > > make: *** No rule to make target 'base64.h', needed by > 'gcc.linux.obj.release-mt/ js_file.o'. Stop.You need to perform a "make clean" first as that file has been moved. See"Clean Rebuild" at http://wiki.synchro.net/install:nix#updating digital manSynchronet "Real Fact" #68:Robert D. Bouman, the author of SyncEdit, died in the mid to late 1990's.Norco, CA WX: 68.3F, 34.0% humidity, 7 mph E wind, 0.00 inches rain/24hrs--- Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Dumas Walker@VERT/CAPCITY2 to DIGITAL MAN on Thu Jan 4 18:31:00 2018
    Then you're missing an update. What was the "cvs update" command you ran when> you updated?See below.> It sounds like you're missing rev 1.42 of src/sbbs3/targets.mkMine is dated December 31. Loading it up in mcview gives this info: $Id: targets.mk,v 1.42 2017/12/13 21:25:21 rswindle Exp $> You need to perform a "make clean" first as that file has been moved. See> "Clean Rebuild" at http://wiki.synchro.net/install:nix#updatingOK, here is a cut-and-paste from my lxterminal window: $ export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs $ cvs update -d exec $ cvs update -d src 3rdp $ cd /sbbs/src/sbbs3 $ make RELEASE=1 USE_DOSEMU=1 cleanDeleting gcc.linux.obj.release/Deleting gcc.linux.obj.release-mt/Deleting gcc.linux.lib.release/Deleting gcc.linux.exe.release/ $ cd scfg $ make RELEASE=1 USE_DOSEMU=1 cleanDeleting gcc.linux.obj.release/Deleting gcc.linux.obj.release-mt/Deleting gcc.linux.lib.release/Deleting gcc.linux.exe.release/ $ cd /sbbs/src/sbbs3 $ make RELEASE=1 USE_DOSEMU=1 symlinksmake: *** No rule to make target 'symlinks'. Stop. $ make RELEASE=1 symlinksmake: *** No rule to make target 'symlinks'. Stop.--- SLMR 2.1a "Gasoline clears my sinuses!" - Fred G. Sanford Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Digital Man@VERT to Dumas Walker on Thu Jan 4 17:48:33 2018
    Re: Javascript TW2 By: Dumas Walker to DIGITAL MAN on Thu Jan 04 2018 06:31 pm > > Then you're missing an update. What was the "cvs update" command you ran > > when you updated? > > See below. > > > It sounds like you're missing rev 1.42 of src/sbbs3/targets.mk > > Mine is dated December 31. Loading it up in mcview gives this info: > > $Id: targets.mk,v 1.42 2017/12/13 21:25:21 rswindle Exp $Are you sure? That should read:# $Id: targets.mk,v 1.42 2017/12/13 21:25:21 rswindell Exp $I'll just assume that's a typo. What does "cvs status" report about that file?Should look like this (with a couple extra lines):~/sbbs/src/sbbs3$ cvs status targets.mk===================================================================File: targets.mk Status: Up-to-date Working revision: 1.42 Repository revision: 1.42 /cvsroot/sbbs/src/sbbs3/targets.mk,v Commit Identifier: YArZCgUZpz38bMiA > > You need to perform a "make clean" first as that file has been moved. See > > "Clean Rebuild" at http://wiki.synchro.net/install:nix#updating > > OK, here is a cut-and-paste from my lxterminal window: > > $ export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs > $ cvs update -d exec > $ cvs update -d src 3rdp > $ cd /sbbs/src/sbbs3 > $ make RELEASE=1 USE_DOSEMU=1 clean > Deleting gcc.linux.obj.release/ > Deleting gcc.linux.obj.release-mt/ > Deleting gcc.linux.lib.release/ > Deleting gcc.linux.exe.release/ > $ cd scfg > $ make RELEASE=1 USE_DOSEMU=1 clean > Deleting gcc.linux.obj.release/ > Deleting gcc.linux.obj.release-mt/ > Deleting gcc.linux.lib.release/ > Deleting gcc.linux.exe.release/ > $ cd /sbbs/src/sbbs3 > $ make RELEASE=1 USE_DOSEMU=1 symlinks > make: *** No rule to make target 'symlinks'. Stop. > $ make RELEASE=1 symlinks > make: *** No rule to make target 'symlinks'. Stop.Okay, good. So the base64.h error went away. The symlinks build error ismysterious. What if you remove that from the make command-line? digital manThis Is Spinal Tap quote #10:Dozens of people spontaneously combust each year... just not widely reported.Norco, CA WX: 68.3F, 46.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs--- Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Dumas Walker@VERT/CAPCITY2 to DIGITAL MAN on Fri Jan 5 18:32:00 2018
    ~/sbbs/src/sbbs3$ cvs status targets.mk> ===================================================================> File: targets.mk Status: Up-to-date> Working revision: 1.42> Repository revision: 1.42 /cvsroot/sbbs/src/sbbs3/targets.mk,v> Commit Identifier: YArZCgUZpz38bMiA $ cvs status targets.mkcvs status: No CVSROOT specified! Please use the `-d' optioncvs [status aborted]: or set the CVSROOT environment variable. $ export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs $ cvs status targets.mkcvs status: cannot open CVS/Entries for reading: No such file or directorycvs [status aborted]: no repositoryDoes that provide any clues? :)> > > You need to perform a "make clean" first as that file has been moved. See> > > "Clean Rebuild" at http://wiki.synchro.net/install:nix#updating> >> > OK, here is a cut-and-paste from my lxterminal window:> >> > $ export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs> > $ cvs update -d exec> > $ cvs update -d src 3rdp> > $ cd /sbbs/src/sbbs3> > $ make RELEASE=1 USE_DOSEMU=1 clean> > Deleting gcc.linux.obj.release/> > Deleting gcc.linux.obj.release-mt/> > Deleting gcc.linux.lib.release/> > Deleting gcc.linux.exe.release/> > $ cd scfg> > $ make RELEASE=1 USE_DOSEMU=1 clean> > Deleting gcc.linux.obj.release/> > Deleting gcc.linux.obj.release-mt/> > Deleting gcc.linux.lib.release/> > Deleting gcc.linux.exe.release/> > $ cd /sbbs/src/sbbs3> > $ make RELEASE=1 USE_DOSEMU=1 symlinks> > make: *** No rule to make target 'symlinks'. Stop.> > $ make RELEASE=1 symlinks> > make: *** No rule to make target 'symlinks'. Stop.> Okay, good. So the base64.h error went away. The symlinks build error is> mysterious. What if you remove that from the make command-line?The last time I tried it, it ran for 5-10 minutes beforegiving the base64.h error. I later realized it had erased most of myexecutables from the sbbs3 directory tree. So I am a little leary to tryit again. :)FYI, that was the first and only time I saw the base64.h error was when Iran "make RELEASE=1" without the "symlinks" included.--- SLMR 2.1a "Kills millions of germs on contract" Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Digital Man@VERT to Dumas Walker on Fri Jan 5 18:05:32 2018
    Re: Javascript TW2 By: Dumas Walker to DIGITAL MAN on Fri Jan 05 2018 06:32 pm > > ~/sbbs/src/sbbs3$ cvs status targets.mk > > =================================================================== > > File: targets.mk Status: Up-to-date > > > Working revision: 1.42 > > Repository revision: 1.42 /cvsroot/sbbs/src/sbbs3/targets.mk,v > > Commit Identifier: YArZCgUZpz38bMiA > > $ cvs status targets.mk > cvs status: No CVSROOT specified! Please use the `-d' option > cvs [status aborted]: or set the CVSROOT environment variable. > $ export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs > $ cvs status targets.mk > cvs status: cannot open CVS/Entries for reading: No such file or directory > cvs [status aborted]: no repository > > Does that provide any clues? :)You didn't get the source using cvs in the first place?Do you not have a src/sbbs3/CVS directory? > > > > You need to perform a "make clean" first as that file has been moved. > > > > See > > > > "Clean Rebuild" at http://wiki.synchro.net/install:nix#updating > > > > OK, here is a cut-and-paste from my lxterminal window: > > > > $ export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs > > > $ cvs update -d exec > > > $ cvs update -d src 3rdp > > > $ cd /sbbs/src/sbbs3 > > > $ make RELEASE=1 USE_DOSEMU=1 clean > > > Deleting gcc.linux.obj.release/ > > > Deleting gcc.linux.obj.release-mt/ > > > Deleting gcc.linux.lib.release/ > > > Deleting gcc.linux.exe.release/ > > > $ cd scfg > > > $ make RELEASE=1 USE_DOSEMU=1 clean > > > Deleting gcc.linux.obj.release/ > > > Deleting gcc.linux.obj.release-mt/ > > > Deleting gcc.linux.lib.release/ > > > Deleting gcc.linux.exe.release/ > > > $ cd /sbbs/src/sbbs3 > > > $ make RELEASE=1 USE_DOSEMU=1 symlinks > > > make: *** No rule to make target 'symlinks'. Stop. > > > $ make RELEASE=1 symlinks > > > make: *** No rule to make target 'symlinks'. Stop. > > > Okay, good. So the base64.h error went away. The symlinks build error is > > mysterious. What if you remove that from the make command-line? > > The last time I tried it, it ran for 5-10 minutes before > giving the base64.h error. I later realized it had erased most of my > executables from the sbbs3 directory tree. So I am a little leary to try > it again. :) > > FYI, that was the first and only time I saw the base64.h error was when I > ran "make RELEASE=1" without the "symlinks" included.A "clean" fixed the base64.h error. It had nothing to do with including orexcluding the "symlinks" argument. digital manSynchronet/BBS Terminology Definition #41:REP = QWK ReplyNorco, CA WX: 63.6F, 78.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs--- Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Dumas Walker@VERT/CAPCITY2 to DIGITAL MAN on Sat Jan 6 13:32:00 2018
    $ cvs status targets.mk> > cvs status: No CVSROOT specified! Please use the `-d' option> > cvs [status aborted]: or set the CVSROOT environment variable.> > $ export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs> > $ cvs status targets.mk> > cvs status: cannot open CVS/Entries for reading: No such file or directory> > cvs [status aborted]: no repository> >> > Does that provide any clues? :)> You didn't get the source using cvs in the first place?I did do so.> Do you not have a src/sbbs3/CVS directory?Yes.~/src/sbbs3/CVS$ lsEntries Repository Root TagShould I have been in the /src/sbbs3 directory when I ran the cvs statuscommand?--- SLMR 2.1a L&N -- The Old Reliable Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Dumas Walker@VERT/CAPCITY2 to DIGITAL MAN on Sat Jan 6 14:52:00 2018
    The last time I tried it, it ran for 5-10 minutes before> > giving the base64.h error. I later realized it had erased most of my> > executables from the sbbs3 directory tree. So I am a little leary to try> > it again. :)> >> > FYI, that was the first and only time I saw the base64.h error was when I> > ran "make RELEASE=1" without the "symlinks" included.>> A "clean" fixed the base64.h error. It had nothing to do with including or> excluding the "symlinks" argument.Ok, so running without symlinks does cause all of the make steps listed inthe wiki to complete with success, as does the update.js step. However,restarting synchronet after the compile does not work so good. It ends ina segmentation fault. I had the output captured but apparently it gotdeleted when I had to restore from backup.Just for fun, I did go back through the wiki and attempt to install all ofthe dependencies. apt-get reported that all were installed at at theirnewest versions - none missing.Also, one thing I did see synchronet complain about before abending was theSBBSCTRL not being set. I find this confusing as the script that startssynchronet contains these three lines, before sbbs is called:export HOME=/sbbsexport SBBSCTRL=/sbbs/ctrlexport SBBSNODE=/sbbs/node1 ???--- SLMR 2.1a Safe sex used to mean to put the car in "Park" Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Digital Man@VERT to Dumas Walker on Sat Jan 6 12:20:17 2018
    Re: Javascript TW2 By: Dumas Walker to DIGITAL MAN on Sat Jan 06 2018 01:32 pm > > > $ cvs status targets.mk > > > cvs status: No CVSROOT specified! Please use the `-d' option > > > cvs [status aborted]: or set the CVSROOT environment variable. > > > $ export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs > > > $ cvs status targets.mk > > > cvs status: cannot open CVS/Entries for reading: No such file or > > > directory cvs [status aborted]: no repository > > > > Does that provide any clues? :) > > You didn't get the source using cvs in the first place? > > I did do so. > > > Do you not have a src/sbbs3/CVS directory? > > Yes. > > ~/src/sbbs3/CVS$ ls > Entries Repository Root Tag > > Should I have been in the /src/sbbs3 directory when I ran the cvs status > command?Yes. digital manThis Is Spinal Tap quote #13:Nigel Tufnel: You can't really dust for vomit.Norco, CA WX: 69.2F, 61.0% humidity, 2 mph ESE wind, 0.00 inches rain/24hrs--- Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Dumas Walker on Sat Jan 6 12:24:10 2018
    Re: Javascript TW2 By: Dumas Walker to DIGITAL MAN on Sat Jan 06 2018 02:52 pm > > > The last time I tried it, it ran for 5-10 minutes before > > > giving the base64.h error. I later realized it had erased most of my > > > executables from the sbbs3 directory tree. So I am a little leary to > > > try it again. :) > > > > FYI, that was the first and only time I saw the base64.h error was when > > > I ran "make RELEASE=1" without the "symlinks" included. > > > A "clean" fixed the base64.h error. It had nothing to do with including or > > excluding the "symlinks" argument. > > Ok, so running without symlinks does cause all of the make steps listed in > the wiki to complete with success, as does the update.js step. However, > restarting synchronet after the compile does not work so good. It ends in > a segmentation fault. I had the output captured but apparently it got > deleted when I had to restore from backup.The instructions for debugging crashes (e.g. segfaults) on *nix are here:http://wiki.synchro.net/howto:gdbIt'd be helpful if you had a core file from the crash. > Just for fun, I did go back through the wiki and attempt to install all of > the dependencies. apt-get reported that all were installed at at their > newest versions - none missing. > > Also, one thing I did see synchronet complain about before abending was the > SBBSCTRL not being set. I find this confusing as the script that starts > synchronet contains these three lines, before sbbs is called: > > export HOME=/sbbs > export SBBSCTRL=/sbbs/ctrl > export SBBSNODE=/sbbs/node1 > > ???What's the rest of the script look like? Are you running sbbs daemonized or inthe foreground? digital manSynchronet/BBS Terminology Definition #37:NNTP = Network News Transfer ProtocolNorco, CA WX: 69.2F, 61.0% humidity, 2 mph ESE wind, 0.00 inches rain/24hrs--- Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Dumas Walker@VERT/CAPCITY2 to DIGITAL MAN on Sun Jan 7 11:00:00 2018
    The instructions for debugging crashes (e.g. segfaults) on *nix are here:> http://wiki.synchro.net/howto:gdb>> It'd be helpful if you had a core file from the crash.I think the problem is that I probably have to keep up with acvs/make/etc. routine pretty regular in order not to get out of sync atsome point. I am not a PC platform developer, or a bleeding edge user, soI would not be one to do so.That is part of the reason I chose debian stable over slackware... I knewI'd wind up screwing up a "compile the packages yourself" distro because Iwould not keep up with every single release of my favorite packages. Ifigured out that a release with prebuild binaries and package/dependencymanagement built in was going to be my friend. :)Just so long as the ftp server and qwk mail doesn't stop working (what folksreally use here), I should probably be happy with what I have.Thanks!--- SLMR 2.1a ??? Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Al@VERT/TRMB to Dumas Walker on Sun Jan 7 17:38:11 2018
    Re: Javascript TW2 By: Dumas Walker to DIGITAL MAN on Sun Jan 07 2018 11:00 am DW> I think the problem is that I probably have to keep up with a DW> cvs/make/etc. routine pretty regular in order not to get out of sync at DW> some point. I am not a PC platform developer, or a bleeding edge user, so DW> I would not be one to do so.You are on the bleeding edge here.. I find Synchronet to be very stable so noworries.. :) DW> That is part of the reason I chose debian stable over slackware... I knew DW> I'd wind up screwing up a "compile the packages yourself" distro because I DW> would not keep up with every single release of my favorite packages. I DW> figured out that a release with prebuild binaries and package/dependency DW> management built in was going to be my friend. :)I still consider myself a debianite. The stable release can get old, I think weran woody for 5 or 6 years before sarge was released but it certainly isstable.I took Slackware for a walkabout many years ago and I am still here. I might bea slacker now. I have a hundred or two packages I build myself and update themwhen they need it. One nice thing about slackware is that the build environmentis complete one you install it. No further button pushing is needed. It's agood idea to keep things upto date though.One thing I have found, at least with slackware is that there are a fewpackages that need a real root shell to build successfully. If I build thosefrom a desktop terminal I need to source /etc/profile with a command like "./etc/profile". I build and run Synchronet as a regular user so I don't needthat for Synchronet and it may or may not be an issue for you. Ttyl :-), Al...Everybody should believe in something - I believe I'll have a beer--- Synchronet The Rusty MailBox - Penticton, BC Canada - trmb.synchro.net
  • From Dumas Walker@VERT/CAPCITY2 to Digital Man on Fri Jan 12 16:02:04 2018
    > The instructions for debugging crashes (e.g. segfaults) on *nix are here: > http://wiki.synchro.net/howto:gdb > It'd be helpful if you had a core file from the crash. OK, so after Al's encouragement, I decided to try a different approach. I setup a second sbbs directory, /opt/sbbs, and did a brand new install there.Afterwards, I ran my script that exports paths under /opt/sbbs and starts sbbs. It came up without any apparent issue.Then I created a symlink under the /opt/bbs "test" environment back to the/sbbs/data directory in "production." I did the same thing with the ctrldirectory. When I refired /opt/sbbs/exec/sbbs, I get a segfault again...26991.From what I can tell, I have to compile a debug version in order to get corefiles to generate? Or will changing the limits.conf settings cause the corefile to be created without using a debug version?--- Synchronet CAPCITY2 * capcity2.synchro.net * 1-502-875-8938
  • From Digital Man@VERT to Dumas Walker on Fri Jan 12 18:41:40 2018
    Re: Re: Javascript TW2 By: Dumas Walker to Digital Man on Fri Jan 12 2018 04:02 pm > > > The instructions for debugging crashes (e.g. segfaults) on *nix are here: > > http://wiki.synchro.net/howto:gdb > > > It'd be helpful if you had a core file from the crash. > > OK, so after Al's encouragement, I decided to try a different approach. I > set up a second sbbs directory, /opt/sbbs, and did a brand new install > there. Afterwards, I ran my script that exports paths under /opt/sbbs and > starts sbbs. > It came up without any apparent issue. > > Then I created a symlink under the /opt/bbs "test" environment back to the > /sbbs/data directory in "production." I did the same thing with the ctrl > directory. When I refired /opt/sbbs/exec/sbbs, I get a segfault again... > 26991. > > From what I can tell, I have to compile a debug version in order to get core > files to generate?No, release (non-debug) builds will generate core files too if your system willallow it. > Or will changing the limits.conf settings cause the core > file to be created without using a debug version?A non-debug core file can still be very useful and yes, there a various ways toinstruct your system to allow core files to be created. Detailed here:http://wiki.synchro.net/howto:gdb#core_file digital manSynchronet "Real Fact" #35:The irc.synchro.net network has more servers than users.Norco, CA WX: 68.4F, 39.0% humidity, 3 mph WNW wind, 0.00 inches rain/24hrs--- Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net