|
|
|
This item is for system problems. If something on Grex isn't working right (line noise on a modem, weird behavior from a program, etc.), this is the place to announce it. Except for security holes. If you find a hole in system security, mail information about it to "staff".
260 responses total.
A lot of things have been fixed, tuned or otherwise corrected in the weeks since the upgrade. Now might be a good time to look around and see what other systems issues are still outstanding -- broken or not working the same as before the upgrade -- and mention it here to make certain nothing gets overlooked.
I still can't compile my C++ programs since the upgrade. I compile the source files like this: g++ -c -fno-exceptions box.cpp g++ -c -fno-exceptions line.cpp g++ -c -fno-exceptions parse.cpp g++ -c -fno-exceptions token.cpp and then link them like this: ld -L/usr/lib/gcc-lib/i386-unknown-openbsd3.8/3.3.5 -lc -lm -lstdc++ -o box box.o line.o parse.o token.o The compiles go fine, but the linker has lots of errors of the form: /usr/lib/libstdc++.so.40.0: undefined reference to `_Unwind_Resume' /usr/lib/libstdc++.so.40.0: undefined reference to `_Unwind_DeleteException' and lots more like that. I'm not calling the "Unwind" routines from my code, so I presume the compiler is putting references in automatically. I thought maybe if I turned off exceptions that would take care of it, but as you can see the "-fno-exceptions" flag didn't fix the problem. So I need to either a) tell the compiler not to insert those references, or b) find the libraries that include those Unwind routines and link them in. Anybody have any ideas?
Try adding -lgcc and see if that fixes it.
THanks Mike - that's better. Now I only get two linker errors: /usr/lib/libc.so.38.2: undefined reference to `environ' /usr/lib/libc.so.38.2: undefined reference to `__progname' I'm not referring to those two variables in my program; it looks like libc is. Is that the right libc to use? Anybody know what library has those symbols?
This response has been erased.
Why was Grex down for the last day or two?
This response has been erased.
This response has been erased.
Happily, we're not getting the variety of crashes we used to see before the system upgrade and swapping out that memory. We appear to be down to just this one particular panic in softdep_write_inodeblock: panic: softdep_write_inodeblock: indirect pointer #0 mismatch 0 != 0 Starting stack trace... panic(d6a33880,d6a33880,e88e9d5c,e88e9db4,d6703b00) at panic+0x71 panic(d050a940,d0509dd7,0,0,0) at panic+0x71 initiate_write_inodeblock(e9be68dc,d6a68d58,d0f93000,0,e88e9e0c) at initiate_write_inodeblock+0x3c1 softdep_disk_io_initiation(d6a68d58,7fffffff,e88e9e5c,d021ae58) at softdep_disk_io_initiation+0x66 spec_strategy(e88e9e64,d6a13bb0,e88e9e6c,d067a2f4,0) at spec_strategy+0x42 spec_vnoperate(e88e9e64,40,e88e9e7c,80,d0580b80) at spec_vnoperate+0x16 VOP_STRATEGY(d6a68d58,d6a13e34,e88e9ebc,d02eed92,d6a13e34) at VOP_STRATEGY+0x25 bwrite(d6a68d58,d6a4f4a0,1,0,d6a13dc4) at bwrite+0xac spec_vnoperate(e88e9ed4,1,0,d6a68d58,d0580bc0) at spec_vnoperate+0x16 VOP_BWRITE(d6a68d58,0,1,0) at VOP_BWRITE+0x25 ffs_fsync(e88e9f24,d6a13dc4,10052,d6a27004,d05806c0) at ffs_fsync+0x1df VOP_FSYNC(d6a13dc4,d6a36000,3,d6a27004,0,12,d6a27004) at VOP_FSYNC+0x34 sched_sync(d6a27004) at sched_sync+0x100 Bad frame pointer: 0xd06f1ed8 End of stack trace. syncing disks...
Is this a bug?
This response has been erased.
Thanks Dan -
/--------------------------------\
| Now I can put things in boxes! |
\--------------------------------/
___ _ I can also use drop capitals, in any figlet font. Of
/ _ \ | | course, that necessitates writing a long paragraph,
/ /_\ \_ __ __| | which gets tiredome for the reader. I am curious what
| _ | '_ \ / _` | the correct libraries are to use with ld - Dan told me
| | | | | | | (_| | to use "c++" for both compiling and linking, and I
\_| |_/_| |_|\__,_| presume c++ is just g++ with certain options. (But
since it's a binary, I can't tell what options.) Still,
ln ought to work with the right libraries, oughtn't it?
___ _ how do I tell the linker not to give warnings whehever
/ _ \| | I use strcpy or sprintf? It seems very maternalistic
/ /_\ \ |___ ___ about that. There must be some option that turns off
| _ | / __|/ _ \ those warnings, I would think.
| | | | \__ \ (_) |
\_| |_/_|___/\___( )
|/
_ _
_ _ _ __ | |_ _ ___| | ___ _
| | | | '_ \| | | | |/ __| |/ / | | |
| |_| | | | | | |_| | (__| <| |_| |
\__,_|_| |_|_|\__,_|\___|_|\_\\__, |
|___/
This response has been erased.
This response has been erased.
This response has been erased.
This response has been erased.
fronttalk is hell.
This response has been erased.
Thanks Dan. I know everyone has a string class they think is the answer to all problems; I've written a few of them myself. But a lot of times I don't want or need the overhead.
This response has been erased.
I just dialed into grex (with DOS kermit) and instead of letting me hit Enter to select the default VT100: Terminal type: [vt100] (I hit Enter key) tset: unknown terminal type I had to type out VT100. What was changed and please fix it. I don't know how long ago this happened because I was not able to dial in for a couple of weeks, maybe the BSD upgrade caused the problem.
You dialed in for 30 minutes on December 22: keesan tty01 Thu Dec 22 13:28 - 13:58 (00:29) I don't think anything has changed since then.
(Joe's comment slipped in ahead of mine) Nothing has been changed since I fixed the dialup line tty speed a week or so ago. Is it possible that your .login or .profile has some dependency on the default tty value used on the dialin lines? The default TERM for tty00 and tty01 is now "dialup" instead of "unknown".
I am setting my terminal in .cshrc with /usr/bin/tset, which exists. I probably dialed in with linux on previous occasions and when I was asked about whether my terminal is [VT100] I typed linux. If I type linux or vt100 things work, the problem was when I hit the enter key for the default vt100 and it was interpreted as 'tset' being my terminal. I can try ssh'ing with DOS and hitting the Enter key some time. Maybe nobody else who dials in with DOS also accesses grex with linux and set it up this way.
This response has been erased.
Re #21: I care more about clarity than speed most of the time, too. But if you pick one library of classes and call it "standard", you can't get away form the fact that other people have different libraries that are more standard to them than yours. So what's clear to you won't be to them. If you have to drag a lot of libraries along with you whenever you port something to someplace new, that's a drawback in my book. Sometimes it's worth it, sometimes it's not.
Re 26, sometimes I telnet to grex after dialing with DOS. Why 'dialup?vt100' ? Sometimes I dial with linux, or ssh with linux.
I changed the tset line in .login to tset -m '?vt100' and was able, while still online with ssh, to type login and login name and password and Enter key and get logged in. Probably as vt100 (which is sure to mess up lynx or pine since I am in linux).
This response has been erased.
Grex seems to be on the RBL blacklist again - a mail just bounced back with that explanation.
Looks like it's listed in SORBS and in Spamcop.
I tried to email myself from grex to my freeshell account, which would not
accept mail from grex, which I find funny because recently freeshell was
also on the spamcop blacklist and I could not mail people from freeshell.
A good reason to have two shell accounts.
From Mailer-Daemon@cyberspace.org Tue Dec 27 16:55:35 2005
Date: Tue, 27 Dec 2005 16:55:35 -0500
From: Mail Delivery System <Mailer-Daemon@cyberspace.org>
To: keesan@cyberspace.org
Subject: Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
keesan@freeshell.org
SMTP error from remote mail server after MAIL FROM:<keesan@cyberspace.org>:
host smtp.freeshell.org [192.94.73.21]: 550 5.7.1 216.86.77.194 blocked
according spamcop.net:see http://spamcop.net/bl
------ This is a copy of the message, including all the headers. ------
Return-path: <keesan@cyberspace.org>
Received: from keesan (helo=localhost)
by grex.cyberspace.org with local-esmtp (Exim 4.54)
id 1ErL4x-0004wq-PN
for keesan@freeshell.org; Tue, 27 Dec 2005 15:05:51 -0500
Date: Tue, 27 Dec 2005 15:05:51 -0500 (EST)
From: Sindi Keesan <keesan@grex.cyberspace.org>
To: keesan@freeshell.org
Subject: Mail delivery failed: returning message to sender (fwd)
Message-ID: <Pine.BSO.4.63.0512271505300.12571@grex.cyberspace.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: Sindi Keesan <keesan@cyberspace.org>
Sindi Keesan
---------- Forwarded message ----------
Date: Tue, 27 Dec 2005 00:44:58 -0500
From: Mail Delivery System <Mailer-Daemon@cyberspace.org>
To: keesan@cyberspace.org
Subject: Mail delivery failed: returning message to sender
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
SMTP error from remote mail server after initial connection:
host mx08.gis.net [208.218.130.52]: 551 Connection refused. Your ip number
216.86.77.194 was found on the spamcopbl.gis.net RBL database
------ This is a copy of the message, including all the headers. ------
Return-path: <keesan@cyberspace.org>
Received: from keesan (helo=localhost)
by grex.cyberspace.org with local-esmtp (Exim 4.54)
id 1Er7dq-00010n-5o
for XXXXX; Tue, 27 Dec 2005 00:44:58 -0500
Date: Tue, 27 Dec 2005 00:44:58 -0500 (EST)
From: Sindi Keesan <keesan@grex.cyberspace.org>
To: XXXXX
Subject: Re: hi to all
In-Reply-To: <6.1.2.0.1.20051222223045.01a79540@pop.gis.net>
Message-ID: <Pine.BSO.4.63.0512270043031.11667@grex.cyberspace.org>
References: <Pine.BSO.4.63.0512222052160.29871@grex.cyberspace.org>
<6.1.2.0.1.20051222223045.01a79540@pop.gis.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: Sindi Keesan <keesan@cyberspace.org>
According to http://www.spamcop.net/w3m?action=checkblock&ip=216.86.77.194,
"in the past 302.3 days, it has been listed 17 times for a total
of 15.8 days"
So how long until grex can send outgoing mail to anyone using spamassassin, one or two days? How do we get it unblocked? Can't they put grex and freeshell on a whitelist somehow? I tried to forward returned mail from grex to freeshell so I could send it from there, and freeshell is also blocking grex mail. Do they block on the From line or on the ISP if they don't match? I could try sending directly via an ISP when grex or freeshell are blacklisted but I use freeshell as From and Replyto.
This response has been erased.
warning: libc.so.38.2: minor version >= 3 expected, using it anyway PicoSpan T3.3a; designed by Marcus Watts copyright 1984 NETI; licensed by Unicon Inc.
Re resp:35: Being listed on Spamcop is not, in itself, enough to get Spamassassin to reject mail in its default configuration. Spamassassin works on a "point" system. Various signs of spam are worth certain numbers of points. If the score exceeds a user-configurable threshold, the mail is tagged as spam or rejected, depending on the configuration. Being listed in bl.spamcop.net is only worth 1.8 points towards a default spam threshold of 5. Most likely, some clueless mail admin is blocking all mail from hosts in Spamcop's blacklist. There are blacklists that I feel are accurate enough to use that way, but bl.spamcop.net definitely isn't one of them.
!help
Welcome to Grex's help archives!
Please mail staff with additions, corrections, or if you need help!
Valerie Mates, valerie@cyberspace.org. Last update 6/5/97
Available documents are:
0. The new, excellent, Grex FAQ. Highly recommended!
1. An Introduction to Grex ("Take Me To Your Modem")
2. Frequently Asked Questions (more useful to non-Grexers)
3. An Introduction To The Picospan Conferencing ("BBS") System.
4. The Grex Declaration Of Principles
5. Who pays for Grex? Can I help? Does this cost money?
6. Phone list
7. Article about Grex that was in the People's Food Co-op Newsletter
8. Choose this option to get >>>help from a real live person<<<
9. Run the menu system.
A. Run Lynx.
B. Go to the conferences ("BBS").
C. Change settings on your account (password, name, shell, .plan file, etc)
D. Frequently Asked Questions about Grex's Party program
E. Frequently Asked Questions about Web Pages on Grex
Choose a number (or letter), or q to quit: 6
Last update: 4/25/2001 by scott@cyberspace.org
The phone numbers for Grex are:
phone number device modem type max. speed
------------------------------------------------
+1 734 761 3000 Groovy GVC 14.4 14400 bps
+1 734 761 5041 Groovy GVC 14.4 14400 bps
+1 734 761 3411 Groovy GVC 14.4 14400 bps
+1 734 761 3451 Groovy GVC 14.4 14400 bps
+1 734 761 3554 Groovy GVC 14.4 14400 bps
+1 734 761 3596 Groovy GVC 14.4 14400 bps
+1 734 761 2517 Groovy GVC 14.4 14400 bps
In normal operation, these numbers trunk hunt, so dialing (734) 761-3000
will give you the first available line out of these seven. All of the
modems connect to a terminal server which makes an 8-bit telnet connection
to Grex.
Press Enter to continue...
| Last 40 Responses and Response Form. |
|
|
|
- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss