I am getting the following error. There are 16 different errors all similar to this. I am running Synchronet. As a former Wildcat SysOp back in the day I am trying to get Syncronet figured out. Any ideas on what I should do about this error?
!ERROR reading (000220) #2/2 /sbbs/data/subs/dove-unix
Re: Errors with DOVE-net
By: Digital Man to Trever on Mon Jan 06 2020 01
Re: Errors with DOVE-net
By: Trever to Digital Man on Mon Jan 06 2020 05:23 pm
Re: Errors with DOVE-net
By: Digital Man to Trever on Mon Jan 06 2020 01
Here is a large portion of the error.log All files are owned by sbbs:sbbs. I am also having issues with ssh not able to bind to port 22. I moved the regular ssh to run on a different port thinking that may be interfering but it still is happening.
on Jan 6 17:16:01 2020 sandboxbbs.com
term Node 1 <Trever> !ERROR 2 (No such file or directory) in getmsg.cpp line 86 (loadmsg) reading "(000220) #2/2 /sbbs/data/subs/dove-unix" access=-103 info=smb_getmsghdr corrupt message header ID (6F 6D 3A 20) at offset 544
Re: Errors with DOVE-net
By: Digital Man to Trever on Mon Jan 06 2020 05:59 pm
I delete that one and one other that was giving me greif.
Re: Errors with DOVE-net^^^^^^^^^^^^^^^^
By: Digital Man to Trever on Mon Jan 06 2020 01:38 pm
---
þ Synchronet þ My Brand-New BBS
---^^^^^^^^^^^^^^^^
þ Synchronet þ My Brand-New BBS
:-P
þ Synchronet þ My Brand-New BBS^^^^^^^^^^^^^^^^
How about an old fashioned rusty one?? :P
þ Synchronet þ My Brand-New BBS^^^^^^^^^^^^^^^^
How about an old fashioned rusty one?? :P
Or an old worn-out BBS?
Or an old worn-out BBS?
Running on a TRS-80 Model 100 32K laptop.
Wait a minute!! That's what I started Sysoping on!! <G>
:) Sometimes I had thought about trying to run Synchronet on an Android devi N>or a jailbroken iPhone/iPad just for fun. Android and iOS both have some for N>of *nix as their base OS, and you can get a bash shell on a jailbroken iOS N>device and connect to it via SSH; I'm sure the same could be done on an Andro N>device. I've wondered what it would take to get Synchronet to build on such N>device. Some sysops have installed Synchronet on a Raspberry Pi, so why not N>Android or iOS device? ;) The only thing would be that it might be more N>difficult to run DOS doors on a device like that.
---^^^^^^^^^^^^^^^^
þ Synchronet þ My Brand-New BBS
:-P
How about an old fashioned rusty one?? :P
Daryl
I've wondered about a telnet client for an Android. The bad thing is
the screen is too small to work with.
On 01-10-20 12:14, Nightfox wrote to Daryl Stout <=-
Re: Re: Errors with DOVE-net
By: Daryl Stout to NIGHTFOX on Thu Jan 09 2020 04:04 pm
Or an old worn-out BBS?
Running on a TRS-80 Model 100 32K laptop.
Wait a minute!! That's what I started Sysoping on!! <G>
:) Sometimes I had thought about trying to run Synchronet on an
Android device or a jailbroken iPhone/iPad just for fun. Android and
There's an fTelnet for Android, which I think renders BBS ANSI fairly
well. In the past, there used to be an iOS app called iSSH that
worked with ANSI BBSes fairly well. But you're right, I think
phones tend to be too small.
I used to have a smartphone with a dedicated hardware keyboard.
The screen would slide to the side a bit to reveal the keyboard. I
wish there were more smartphones like that.
There's an fTelnet for Android, which I think renders BBS ANSI fairly
well. In the past, there used to be an iOS app called iSSH that
worked with ANSI BBSes fairly well. But you're right, I think
phones tend to be too small.
I can't remember the name of it, but there are a few apps.
I used to have a smartphone with a dedicated hardware keyboard.
The screen would slide to the side a bit to reveal the keyboard. I
wish there were more smartphones like that.
I used to have a phone like that years ago. But, it's easier to type
on a regular desktop keyboard.
There's an fTelnet for Android, which I think renders BBS ANSI fairly
well. In the past, there used to be an iOS app called iSSH that
worked with ANSI BBSes fairly well. But you're right, I think
phones tend to be too small.
I used to have a smartphone with a dedicated hardware keyboard.
The screen would slide to the side a bit to reveal the keyboard. I
wish there were more smartphones like that.
On 01-14-20 17:07, nolageek wrote to Nightfox <=-
I agree with both of you. Using the BBS on a phone is an exercise in frustration. Vertically the keyboard is too small and it takes multiple tries for people to log in and horizontally either the main window
floats all over the place when you're tying to type, or you have to
move it back and forth to see what you're doing (if the native keyboard doesn't hijack you and take over the entire screen.
The only way I can see a phone working is with a Blutooth keyboard, but kinda defeats the purpose of portability.
On 01-15-20 08:26, Rampage wrote to Tony Langdon <=-
The only way I can see a phone working is with a Blutooth keyboard, but
kinda defeats the purpose of portability.
these search results might be interesting ;)
https://www.google.com/search?q=roll-up+keyboard+computer
I've heard of ConnectBot for Android, though I don't think it renders BBS ANS N>properly. From what I remember, there are very few mobile telnet apps that N>render BBS ANSI properly.. fTelnet (for Android) and iSSH (for iOS but is no N>longer available) are the only mobile telnet apps I've seen that render BBS N>ANSI properly.
I agree. I took a typing class in 8th grade and learned to touch-type, so I N>still find it easier to type on a regular desktop keyboard (a good laptop N>keyboard is fine with me too). For mobile, I find hardware keyboards easier N>and more accurate than the on-screen keyboards. There's no tactile feedback N>with the on-screen keyboards, and they tend to rely on things like N>auto-complete in order to type messages fast. Auto-complete can be inaccurat N>and sometimes people don't seem to proofread their message and will send/save N>things with mistakes in them. People also often use voice input on their N>mobile devices, which can often be inaccurate.
Sysop: | Chris Crash |
---|---|
Location: | Huntington Beach, CA. |
Users: | 557 |
Nodes: | 8 (0 / 8) |
Uptime: | 09:08:43 |
Calls: | 10,406 |
Files: | 5 |
Messages: | 364,995 |