TIP: Click on subject to list as thread! ANSI
echo: synchronet
to: DIGITAL MAN
from: KK4QBN
date: 2018-02-16 05:13:00
subject: Re: Raspberry PI synchron

  Re: Re: Raspberry PI synchron
  By: Digital Man to KK4QBN on Thu Feb 15 2018 23:40:01

 >> And though i've done this. anyway I look at it, when I try to load
 >> envorinment varaibles, even in a very simple script, EXCEPT for scfg,
 >> the SBBSCTRL environment will not set.

 DM> What do you mean "EXCEPT for scfg"? There's nothing special about scfg.

I guess I stated what I was trying to say wrong, you told me to try on the basc
commandline.

SBBSCTRL=/sbbs/ctrl && export SBBSCTRL && /sbbs/exec/scfg

I did this, SCFG LOADED with no issues, not with the regular error message
stating "cannot find sbbs ctrl dir, or whatever"

ANY WAY I try to set SBBSCTRL, either on the cmdline, through a script, through
the . files, profile, etc. ALWAYS at the beginning of loading the sbbs
executable it gives the error, SBBSCTRL EVIRONMENT NOT SET. It DOES NOT seem to
bother the FUNCTION of sbbs itself.

 DM> On what OS?

debian x64, I thought I stated that earlier. it does'nt matter if I did or
did'nt at this point.

 DM> On Ubunu Linux or Debian Linux:

It did not give this issue on Ubuntu or even MINT, using the DEBIAN repo and
not the ubuntu.

 DM> 1. edit the file /etc/profile
 DM> 2. after the last line, add one line: export SBBSCTRL=/path/to/ctrl

 M> 4. at a terminal command prompt, type: echo $SBBSCTRL

kk4qbn@kk4qbn:~$ echo $SBBSCTRL

kk4qbn@kk4qbn:~$ 

it is not working.

here is the last few lines of /etc/profile

  done
  unset i
fi
export SBBSCTRL=/sbbs/ctrl/

It has been like this.

 DM> You don't need 2 different steps (ENV_VAR = val, then export) you can do
 DM> it with a single operation: export ENV_VAR = val, for example:

Thanks for educating me on that.. I used to be better versed in scripting but
lost it through time. I have now somplfied all that.

 DM> Maybe try "export SBBSCTRL=/path/to/ctrl" instead.

I believe I've tried all different variations.. still trying.. I'm amazed the
BBS is running :)

 >> it is also setup in /etc/prfile btw.

that was a typo BTW.

 DM> Works for me. What flavor of Linux are you using?

Debian

 DM> $ export HELLO=Hi!
 DM> $ echo $HELLO
 DM> $ env <- shows all environment variables, you'll see HELLO there too
kk4qbn@kk4qbn:~$ export HELLO=Hi
kk4qbn@kk4qbn:~$ echo $HELLO
Hi

I got HI but no Hello..

 DM> $ export HELLO=Hi!
 DM> $ echo $HELLO
 DM> $ env <- shows all environment variables, you'll see HELLO there too

 DM> Now put this in a file, called hi.sh:

 DM> export HELLO=Hi!

Done..

 DM> # unset HELLO <- remove the HELLO env var
 DM> # source hi.sh <- interpret the hi.sh script
 DM> # echo $HELLO <- Do you see Hi!? It worked

output from this travesty

kk4qbn@kk4qbn:~$ unset HELLO
kk4qbn@kk4qbn:~$ source hi.sh
bash: export: `HELLO-Hi!': not a valid identifier
kk4qbn@kk4qbn:~$ echo $HELLO

kk4qbn@kk4qbn:~$ 

Something is borked.

not even trying the shebang no reason..

Something is blocking env var from being stored to a point.. does it not appear
this way?

Thanks for your hel Rob.. while others would call me an idiot, you spend the
time to help.. I used to be great with *nix environments and mainly run only
freeBSD and it was not as forgiving as a lot of these distros out now, I'm
getting older now, my memory suffer, and I cannot spend as much time at the
console because my health (lower half of body goes numb, plus get migraines)
but I do as good as I can, and I don't want to do this with windows.. Not that
I don't like windows, I do, it has its uses.. but I always have a special place
in my hard for linux and SBBS, and I apreciate your patience.

--

Tim Smith (KK4QBN)
KK4QBN BBS

---
 * Synchronet * KK4QBN BBS - kk4qbn.com - kk4qbn.synchro.net - Chatsworth GA
USA
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.