From owner-freebsd-bugs Mon Apr 6 22:10:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19356 for freebsd-bugs-outgoing; Mon, 6 Apr 1998 22:10:03 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: (from gnats@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19346; Mon, 6 Apr 1998 22:10:01 -0700 (PDT) (envelope-from gnats) Date: Mon, 6 Apr 1998 22:10:01 -0700 (PDT) Message-Id: <199804070510.WAA19346@hub.freebsd.org> To: freebsd-bugs Cc: From: Peter Wemm Subject: Re: bin/6233: Velocis/RDS Fails to start after OS Upgrade 2.1.6 -> 2.2.6 Reply-To: Peter Wemm Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/6233; it has been noted by GNATS. From: Peter Wemm To: tkiller@netbox.com Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/6233: Velocis/RDS Fails to start after OS Upgrade 2.1.6 -> 2.2.6 Date: Tue, 07 Apr 1998 13:01:22 +0800 tkiller@netbox.com wrote: [..] > >>Core was generated by `rds'. > >>Program terminated with signal 12, Bad system call. > >>Cannot access memory at address 0x20019080. > >>#0 0x200e9ad5 in ?? () > > I have notified the vendor of the problem, but they do not have a serve r running 2.2. The server ran fine under 2.1.6. This is a very important component of a major project we are working one. Just a hunch.. Have you got the SYSV IPC options enabled in your kernel? If not, you may need to build a custom kernel with the following options: options SYSVSHM options SYSVSEM options SYSVMSG Under 2.2.x, the generic kernel has only got SYSVSHM, you might need the others. I think they were all enabled by default in 2.1.x, but I have not checked. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message