I'm still working on getting up under Linux. Now I find that Binkit
works great, but Fido stuff comes into my "in" folder owned by root.
Once I chown those, SBBSECHO ill not unpack the archives.
On 2018 May 17 12:48:00, you wrote to All:
I'm still working on getting up under Linux. Now I find that Binkit works great, but Fido stuff comes into my "in" folder owned by root. Once I chown those, SBBSECHO ill not unpack the archives.
why are you chowning them??
what user:group is binkit running as?
what user:group is sbbs running as?
what user:group is sbbsecho running as?
The packets were coming in under root which I have since fixed. SBBS is running under sbbs:sbbs. No idea with binkit. SBBSECHO is running under sbbs:sbbs. Now my only issue is with zip as it start to unpack, and then errors with a message that the file is not found though it is still in the "in" folder. erno: 2 (no such file or directory)
RainManHood<---
Rmh wrote to Thumper <=-
Re: Re: Another Issue
By: Thumper to mark lewis on Sun May 20 2018 01:28 pm
The packets were coming in under root which I have since fixed. SBBS is running under sbbs:sbbs. No idea with binkit. SBBSECHO is running under sbbs:sbbs. Now my only issue is with zip as it start to unpack, and then errors with a message that the file is not found though it is still in the "in" folder. erno: 2 (no such file or directory)
Probably you can show us the file/path with the issues and
configurations in sbbsecho.ini
RainManHood<---
Re: Re: Another IssueSBBS is
By: Thumper to mark lewis on Sun May 20 2018 01:28 pm
The packets were coming in under root which I have since fixed.
underrunning under sbbs:sbbs. No idea with binkit. SBBSECHO is running
configurationssbbs:sbbs. Now my only issue is with zip as it start to unpack, and then errors with a message that the file is not found though it is still in the "in" folder. erno: 2 (no such file or directory)
Probably you can show us the file/path with the issues and
Re: Re: Another IssueSBBS is
By: Thumper to mark lewis on Sun May 20 2018 01:28 pm
The packets were coming in under root which I have since fixed.
underrunning under sbbs:sbbs. No idea with binkit. SBBSECHO is running
configurations insbbs:sbbs. Now my only issue is with zip as it start to unpack, and then errors with a message that the file is not found though it is still in the "in" folder. erno: 2 (no such file or directory)
Probably you can show us the file/path with the issues and
sbbsecho.ini
Here is what I have for paths and error:
unpacking bundle: /home/sbbs/sbbs/in/00000063.MO0 (2.5KB)
Executing: = unzip -ojc /home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/ sh: 1: =: not found
Executing: = 'unzip -ojc /home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/' system returned :32517, erno: 2 (No such file or directory)
!unpack failure: /home/sbbs/sbbs/in/00000063.MO0
Re: Re: Another Issue
By: Thumper to Rmh on Mon May 21 2018 11:53 am
Here is what I have for paths and error:
unpacking bundle: /home/sbbs/sbbs/in/00000063.MO0 (2.5KB)
Executing: = unzip -ojc /home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/ sh: 1: =: not found
Executing: = 'unzip -ojc /home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/' system returned :32517, erno: 2 (No such file or directory)
!unpack failure: /home/sbbs/sbbs/in/00000063.MO0
My unzip command is set to unzip -ojC. The lower case "c" in your command line will extract to stdout / screen. I don't think that's what you want..
My unzip command is set to unzip -ojC. The lower case "c" in your
command line will extract to stdout / screen. I don't think that's
what you want..
Typo on my part. It is a C. :)
Executing: = unzip -ojc /home/sbbs/sbbs/in/00000063.MO0 -d
/home/sbbs/sbbs/in/ sh: 1: =: not found
I'm still working on getting up under Linux. Now I find that Binkit works great, but Fido
stuff comes into my "in" folder owned by root. Once I chown those, SBBSECHO ill
not unpack the archives. I'm using the stock zip & unzip. Any ideas?
Re: Re: Another Issue
By: Thumper to Al on Mon May 21 2018 02:03 pm
My unzip command is set to unzip -ojC. The lower case "c" in your
command line will extract to stdout / screen. I don't think that's
what you want..
Typo on my part. It is a C. :)
Oh.. :)
Executing: = unzip -ojc /home/sbbs/sbbs/in/00000063.MO0 -d
/home/sbbs/sbbs/in/ sh: 1: =: not found
Maybe the "sh: 1: =: not found" indicates the problem.. but I'm not sure what that is trying to say.
Do you have zip/unzip in your native program list in external programs?
Re: Re: Another Issue
By: Thumper to mark lewis on Sun May 20 2018 01:28 pm
SBBS isThe packets were coming in under root which I have since fixed.
underrunning under sbbs:sbbs. No idea with binkit. SBBSECHO is running
sbbs:sbbs. Now my only issue is with zip as it start to unpack, and then errors with a message that the file is not found though it is still in the "in" folder. erno: 2 (no such file or directory)
Probably you can show us the file/path with the issues andconfigurations
Here is what I have for paths and error:
unpacking bundle: /home/sbbs/sbbs/in/00000063.MO0 (2.5KB)
Executing: = unzip -ojc /home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/ sh: 1: =: not found
Executing: = 'unzip -ojc /home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/' system returned :32517, erno: 2 (No such file or directory)
Here is what I have for paths and error:
unpacking bundle: /home/sbbs/sbbs/in/00000063.MO0 (2.5KB)
Executing: = unzip -ojc /home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/ sh: 1: =: not found
Executing: = 'unzip -ojc /home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/' system returned :32517, erno: 2 (No such file or directory)
!unpack failure: /home/sbbs/sbbs/in/00000063.MO0
My unpack command are set as:
[archive:ZIP]
RainManHood<---
Re: Another Issueworks
By: Thumper to All on Thu May 17 2018 12:48 pm
I'm still working on getting up under Linux. Now I find that Binkit
filesgreat, but Fido
stuff comes into my "in" folder owned by root. Once I chown those, SBBSECHO ill
not unpack the archives. I'm using the stock zip & unzip. Any ideas?
How are you running Binkit (e.g. from sbbs)? Whatever process is running binkit should be the owner of the files it creates. You "chown those"
to what owner?Binkit is running from SBBS. I've since resolved that problem, but now have the zip errors going on that I listed in a previous message.
Digital Man wrote to Thumper <=-
Re: Another Issue
By: Thumper to All on Thu May 17 2018 12:48 pm
I'm still working on getting up under Linux. Now I find that Binkit works great, but Fido
stuff comes into my "in" folder owned by root. Once I chown those, SBBSECHO ill
not unpack the archives. I'm using the stock zip & unzip. Any ideas?
How are you running Binkit (e.g. from sbbs)? Whatever process is
running binkit should be the owner of the files it creates. You "chown those" files to what owner?
Digital Man wrote to Thumper <=-
Re: Another Issue
By: Thumper to All on Thu May 17 2018 12:48 pm
I'm still working on getting up under Linux. Now I find that Binkit works great, but Fido
stuff comes into my "in" folder owned by root. Once I chown those, SBBSECHO ill
not unpack the archives. I'm using the stock zip & unzip. Any ideas?
How are you running Binkit (e.g. from sbbs)? Whatever process is running binkit should be the owner of the files it creates. You "chown those" files to what owner?
Yes. It is running from SBBS. SBBS is running under user sbbs. I have to "chown" the files
to sbbs. They come in under root. I have changed the user in the Unix section of sbbs.ini
to sbbs. Could it be that I should have setup in /sbbs instead of /home/sbbs/sbbs?
How are you running Binkit (e.g. from sbbs)? Whatever process is
running binkit should be the owner of the files it creates. You
"chown those" files to what owner?
Yes. It is running from SBBS.
SBBS is running under user sbbs. I have
to "chown" the files to sbbs. They come in under root.
I have changed the user in the Unix section of sbbs.ini to sbbs. Could
it be that I should have setup in /sbbs instead of /home/sbbs/sbbs?
No, the directory does not define the owner of created files.
If you ;SHELL from the BBS and run 'whoami', who does it say you are?
digital man
Re: Re: Another Issue
By: Digital Man to Thumper on Fri May 25 2018 04:47 pm
No, the directory does not define the owner of created files.
If you ;SHELL from the BBS and run 'whoami', who does it say you are?
digital man
I did the whoami and it came up root.
On 2018 May 25 08:07:00, you wrote to Digital Man:I've now got Binkit running as a timed event plus as a service. I've also setup SBBS to run under user sbbs and double checked with the whoami command in shell. I fired up umonitor and ran fidoin and fidoout, but still getting the sh: 1 : *: not found.
how are you executing it? as a scheduled event in SBBS, as a scheduled task from cron or similar, or is it running all the time like a traditional mailer so it can accept incoming connections?
no, the directory doesn't really matter... you just have to get everything running with the same owner or at least the same group...
... Ura Montanan if football widows are rare because the men hunt instead.
Damn glasses.... The error is sh: 1 : =: not found
What do you see when you run zip or unzip from the command line?
If you see the help screens there must be something wrong on your command line.
I fired up umonitor and ran fidoin and fidoout, but still getting the
sh: 1 : =: not found
Damn glasses.... The error is sh: 1 : =: not found
RainManHood<---
My unzip command is set to unzip -ojC. The lower case "c" in your
command line will extract to stdout / screen. I don't think that's
what you want..
Typo on my part. It is a C. :)
RainManHood<---
Damn glasses.... The error is sh: 1 : =: not found
Any change of debugging that sh? maybe running some "set -x" to have some extra verbosity?
Damn glasses.... The error is sh: 1 : =: not found
Any change of debugging that sh? maybe running some "set -x" to
have some extra verbosity?
I'm scratching my head on that one. Don't know what to say at this point.
RainManHood<---
Damn glasses.... The error is sh: 1 : =: not found
Any change of debugging that sh? maybe running some "set -x" to
have some extra verbosity?
I'm scratching my head on that one. Don't know what to say at this point.
RainManHood<---
I am thinking the way this works, Synchronet wraps the command between quotes for a sh execution.
Probably incluuding a : set -x;unzip comand etc
I think Thumper was having permission issues as well.. so maybe he is looking at all that. If he solves that I suspect the problem with zip/unzip will go away.
RainManHood<---
Rmh wrote to Thumper <=-
Re: Re: Another Issue
By: Thumper to Al on Mon May 21 2018 02:03 pm
My unzip command is set to unzip -ojC. The lower case "c" in your
command line will extract to stdout / screen. I don't think that's
what you want..
Typo on my part. It is a C. :)
Thinking if adding a bit more verbosity?
Unpack = %@unzip -ojCv %f -d %s
Also, anything at all "extra" in data/sbbsecho.log ?
mark lewis wrote to Thumper <=-
On 2018 May 26 14:54:32, you wrote to me:
I fired up umonitor and ran fidoin and fidoout, but still getting the
sh: 1 : =: not found
i hadn't seen you mention that before...
are you seeing it with both fidoin and fidoout?
is it just on the screen or also in your sbbs log?
are either or both of fidoin and fidoout running a script? if yes, what are the contents of the script(s)?
Rmh wrote to Thumper <=-
Re: Another Issue
By: Al to Rmh on Sun May 27 2018 09:44 pm
Damn glasses.... The error is sh: 1 : =: not found
Any change of debugging that sh? maybe running some "set -x" to
have some extra verbosity?
I'm scratching my head on that one. Don't know what to say at this point.
Thumper,
can you please show us (again) the content of your ctrl/sbbsecho.ini
file?
Specifically:
Inbound =
Outbound =
SecureInbound =
I suspect something is not right there as to me is not picking up the value of the variables.
Thumper wrote to Rmh on 05-29-18 11:52 <=-
Rmh wrote to Thumper <=-
Re: Re: Another Issue
By: Thumper to Al on Mon May 21 2018 02:03 pm
My unzip command is set to unzip -ojC. The lower case "c" in your
command line will extract to stdout / screen. I don't think that's
what you want..
Typo on my part. It is a C. :)
Thinking if adding a bit more verbosity?
Unpack = %@unzip -ojCv %f -d %s
Also, anything at all "extra" in data/sbbsecho.log ?
Here is a cut of my log today:
2018-05-29 02:56:20 SBBSecho 3.04-Linux r3.81 May 9 2018 GCC 5.4.0 invoked with options: -ce
2018-05-29 02:56:20 Configured: 7 archivers, 7 linked-nodes, 0
echolists 2018-05-29 02:56:20 NetMail directory: /sbbs/netmail/
2018-05-29 02:56:20 Secure Inbound directory: /home/sbbs/sbbs/in/ 2018-05-29 02:56:20 Non-secure Inbound directory: /home/sbbs/sbbs/in/ 2018-05-29 02:56:20 Outbound (BSO root) directory: /home/sbbs/sbbs/out 2018-05-29 02:56:20 Read 29 areas from ../data/AREAS.BBS
2018-05-29 02:56:20 Read 2 areas from ../data/badareas.lst
2018-05-29 02:56:20 Read 8 echo statistics from ../data/echostats.ini 2018-05-29 02:56:20 Unpacking bundle: /home/sbbs/sbbs/in/00000063.MO0 (1.2KB) 2018-05-29 02:56:20 Executing: = unzip -ojC
Thumper wrote to Rmh on 05-29-18 12:24 <=-...
Rmh wrote to Thumper <=-
Re: Another Issue
By: Al to Rmh on Sun May 27 2018 09:44 pm
Damn glasses.... The error is sh: 1 : =: not found
Any change of debugging that sh? maybe running some "set -x" to
have some extra verbosity?
I'm scratching my head on that one. Don't know what to say at this point.
Thumper,
can you please show us (again) the content of your ctrl/sbbsecho.ini
file?
Specifically:
Inbound =
Outbound =
SecureInbound =
I suspect something is not right there as to me is not picking up the value of the variables.
Here is a cut of that:
ZoneBlind = false //I'd set this to true
Inbound = ../in (I'd put the complete path here)
SecureInbound = ../in (Complete path and create a secure inbound folder) Outbound = ../out (Complete path)
AreaFile = ../data/areas.bbs
AreaFileBackups = 100
CfgFileBackups = 100
BadAreaFile = ../data/badareas.lst
EchoStats = ../data/echostats.ini
LogFile = ../data/sbbsecho.log
LogTimeFormat = %Y-%m-%d %H:%M:%S
TempDirectory = ../temp/sbbsecho
OutgoingSemaphore=../data/binkout.now
BundleSize = 250K
PacketSize = 250K
SysopAliasList = SBBS
ZoneBlindThreshold = 65535 (If you're linked in Fidonet, change this to 4)
Rmh wrote to Thumper <=-
Re: Re: Another Issue
By: Thumper to Al on Mon May 21 2018 02:03 pm
My unzip command is set to unzip -ojC. The lower case "c" in your
command line will extract to stdout / screen. I don't think that's
what you want..
Typo on my part. It is a C. :)
Thinking if adding a bit more verbosity?
Unpack = %@unzip -ojCv %f -d %s
Also, anything at all "extra" in data/sbbsecho.log ?
Here is a cut of my log today:
2018-05-29 02:56:20 SBBSecho 3.04-Linux r3.81 May 9 2018 GCC 5.4.0 invoked with options: -ce
2018-05-29 02:56:20 Configured: 7 archivers, 7 linked-nodes, 0 echolists 2018-05-29 02:56:20 NetMail directory: /sbbs/netmail/
2018-05-29 02:56:20 Secure Inbound directory: /home/sbbs/sbbs/in/
2018-05-29 02:56:20 Non-secure Inbound directory: /home/sbbs/sbbs/in/ 2018-05-29 02:56:20 Outbound (BSO root) directory: /home/sbbs/sbbs/out 2018-05-29 02:56:20 Read 29 areas from ../data/AREAS.BBS
2018-05-29 02:56:20 Read 2 areas from ../data/badareas.lst
2018-05-29 02:56:20 Read 8 echo statistics from ../data/echostats.ini 2018-05-29 02:56:20 Unpacking bundle: /home/sbbs/sbbs/in/00000063.MO0 (1.2KB) 2018-05-29 02:56:20 Executing: = unzip -ojC /home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/
2018-05-29 02:56:20 ERROR executing '= unzip -ojC /home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/' system returned: 32512, errno: 2 (No such file or directory)
Inbound = ../in
SecureInbound = ../in
Outbound = ../out
are either or both of fidoin and fidoout running a script? if yes,
what are the contents of the script(s)?
Running on the internal timed events:
Fidoin: %!sbbsecho%. -ce
Fidoout: %sbbsecho%. -ni
Just something you may want to try.... not sure it will have a positive effect but, why not split your secure and nonsecure inbound folders and see what happens. Also rename your areas.bbs to lower case.
This is more of a WAG...
Re: Re: Another Issue
By: Thumper to Rmh on Tue May 29 2018 11:52 am
Rmh wrote to Thumper <=-
Re: Re: Another Issue
By: Thumper to Al on Mon May 21 2018 02:03 pm
My unzip command is set to unzip -ojC. The lower case "c" in your
command line will extract to stdout / screen. I don't think that's
what you want..
Typo on my part. It is a C. :)
Thinking if adding a bit more verbosity?
Unpack = %@unzip -ojCv %f -d %s
Also, anything at all "extra" in data/sbbsecho.log ?
Here is a cut of my log today:
2018-05-29 02:56:20 SBBSecho 3.04-Linux r3.81 May 9 2018 GCC 5.4.0
invoked with options: -ce
2018-05-29 02:56:20 Configured: 7 archivers, 7 linked-nodes, 0
echolists 2018-05-29 02:56:20 NetMail directory: /sbbs/netmail/
2018-05-29 02:56:20 Secure Inbound directory: /home/sbbs/sbbs/in/
2018-05-29 02:56:20 Non-secure Inbound directory: /home/sbbs/sbbs/in/
2018-05-29 02:56:20 Outbound (BSO root) directory: /home/sbbs/sbbs/out
2018-05-29 02:56:20 Read 29 areas from ../data/AREAS.BBS
2018-05-29 02:56:20 Read 2 areas from ../data/badareas.lst
2018-05-29 02:56:20 Read 8 echo statistics from ../data/echostats.ini
2018-05-29 02:56:20 Unpacking bundle: /home/sbbs/sbbs/in/00000063.MO0
(1.2KB) 2018-05-29 02:56:20 Executing: = unzip -ojC
/home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/
2018-05-29 02:56:20 ERROR executing '= unzip -ojC
/home/sbbs/sbbs/in/00000063.MO0 -d /home/sbbs/sbbs/in/' system
returned: 32512, errno: 2 (No such file or directory)
See that '=' (equals sign) in the unzip command? that's not supposed to be there. That implies there something wrong with the [archive:zip] section of your sbbsecho.ini file. It should look liek this:
See that '=' (equals sign) in the unzip command? that's not supposed to be there. That implies there something wrong with the [archive:zip] section of your sbbsecho.ini file. It should look liek this:
[archive:ZIP]
Sig = 504B
SigOffset = 0
Pack = %@zip -jD %f %s
Unpack = %@unzip -ojC %f -d %s
'.'...Fidoin: %!sbbsecho%. -ce
Fidoout: %sbbsecho%. -ni
so not a script for either of them, then...
why does one start with a '!' and not the other?
taking a quick look at max's setup, both start with '!' and end with
Thumper wrote to All on 06-01-18 12:10 <=-
Well.... I got everything working but now am getting this message that
I never got before about the packets:
2018-06-01 11:46:41 SBBSecho 3.04-Linux r3.81 May 9 2018 GCC 5.4.0 invoked with options:
2018-06-01 11:46:41 Configured: 7 archivers, 7 linked-nodes, 0
echolists 2018-06-01 11:46:41 NetMail directory: /sbbs/netmail/
2018-06-01 11:46:41 Secure Inbound directory: /home/sbbs/sbbs/insec/ 2018-06-01 11:46:41 Non-secure Inbound directory: /home/sbbs/sbbs/in/ 2018-06-01 11:46:41 Outbound (BSO root) directory: /home/sbbs/sbbs/out 2018-06-01 11:46:41 Read 29 areas from /home/sbbs/sbbs/data/areas.bbs 2018-06-01 11:46:41 Read 2 areas from /home/sbbs/sbbs/data/badareas.lst 2018-06-01 11:46:41 Read 8 echo statistics from /home/sbbs/sbbs/data/echostats.ini
2018-06-01 11:46:41 Importing /home/sbbs/sbbs/in/5b101756.pkt (Type 2+, 0.8KB) from 1:218/700 to 1:218/601
2018-06-01 11:46:41 Unauthenticated SYNCDATA EchoMail from 1:218/700 ignored
2018-06-01 11:46:41 Bad packet detected:
/home/sbbs/sbbs/in/5b101756.pkt 2018-06-01 11:46:41 Importing /home/sbbs/sbbs/in/5b106278.pkt (Type 2+, 3.5KB) from 1:218/700 to 1:218/601 2018-06-01 11:46:41 Unauthenticated FIDO_SYSOP EchoMail from 1:218/700 ignored
2018-06-01 11:46:41 Unauthenticated FIDO_SYSOP EchoMail from 1:218/700 ignored
2018-06-01 11:46:41 Bad packet detected:
/home/sbbs/sbbs/in/5b106278.pkt 2018-06-01 11:46:41 Writing 2 areas to /home/sbbs/sbbs/data/badareas.lst 2018-06-01 11:46:41 Deleting /home/sbbs/sbbs/ctrl/sbbsecho.bsy (from line 2958)
2018-06-01 11:46:41 SBBSecho exiting with error level 0
I'm sure it is something simple, but not sure where it's at....
Well.... I got everything working but now am getting this message that I never got before about the packets:
2018-06-01 11:46:41 SBBSecho 3.04-Linux r3.81 May 9 2018 GCC 5.4.0 invoked with options:
2018-06-01 11:46:41 Configured: 7 archivers, 7 linked-nodes, 0 echolists 2018-06-01 11:46:41 NetMail directory: /sbbs/netmail/
2018-06-01 11:46:41 Secure Inbound directory: /home/sbbs/sbbs/insec/ 2018-06-01 11:46:41 Non-secure Inbound directory: /home/sbbs/sbbs/in/ 2018-06-01 11:46:41 Outbound (BSO root) directory: /home/sbbs/sbbs/out 2018-06-01 11:46:41 Read 29 areas from /home/sbbs/sbbs/data/areas.bbs 2018-06-01 11:46:41 Read 2 areas from /home/sbbs/sbbs/data/badareas.lst 2018-06-01 11:46:41 Read 8 echo statistics from /home/sbbs/sbbs/data/echostats.ini
2018-06-01 11:46:41 Importing /home/sbbs/sbbs/in/5b101756.pkt (Type 2+, 0.8KB) from 1:218/700 to 1:218/601
2018-06-01 11:46:41 Unauthenticated SYNCDATA EchoMail from 1:218/700
ignored
For EchoMail messages (in packets) to be imported, they must be secured. This can be accomplished either via:
1. A secured mailer (e.g. BinkP) session where the bundles/packets are received
into your *secure* inbound directory, and/or:
2. The packets are password-protected and the password is valid (matches your
configuration for the linked node).
If neither of these are true, then the echomail messages are "unauthenticated" and ignored.
digital man
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495930:15:29 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,871 |