how to catch a wildrunning pointer
Hi My Problem: Within a kernel timeout routine I allocate memory and fill it with data. After a while I lock at this data again and realize that it it was modifyted (but not by me). How can I set a kernel mode watch point to that data to see which function change the data. Any Ideas Regards Thomas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how to catch a wildrunning pointer
* Thomas Klein <[EMAIL PROTECTED]> [000128 02:42] wrote: > > > Hi > > My Problem: > Within a kernel timeout routine I allocate memory and fill it with data. > After a while I lock at this data again and realize that it it was modifyted > (but not by me). > How can I set a kernel mode watch point to that data to see which function > change the data. > > Any Ideas Look at the vm code, you can probably write protect the pages while you aren't accessing them, this will cause offending code to panic the machine so you can figure out who is twiddling your bits. Of course you'll have to unprotect the memory when you want to access it for legitimate reasons. You owe the oracle a how-to on acually doing this, a paragraph or two would suffice. thanks, -Or^H^HAlfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how to allocate an alined address for a device?
On Fri, 28 Jan 2000, YAMAMOTO Shigeru wrote: > > > "Warner" == Warner Losh writes: > Warner> In a cardbus system, one would force the alignment in the card bus > Warner> bridge. It would reject those things that aren't aligned in a sane > Warner> manner for cardbus. It would try again to get a different range, if > Warner> possible, or would reject the attempt. > > I think it is no good to try again to get a different range. > Because, a different system has a different free address range and a device > dirver can not know where is a free address range. > > So I change rman_reserve_resource() in @src/sys/kern/subr_rman.c for we can > allocate an aligned address. > > My idea is using high bits of flags. > RF_ALIGN_XXX in aflags specifies an alignment request and an alignment > size. > Bad point of my idea is that we need to use a different bit for each an > alignment size. > > This is a patch for @src/sys/kern/subr_rman.c (rev. 1.10) and > @src/sys/sys/rman.h (rev. 1.5) > > Is my idea good or not? I'm uneasy about using the flags for this since I'm vaguely reserving the upper 16 bits of flags for bus-specific purposes (although I haven't formalised this). For allocating aligned regions with pnp, I simply looped in the caller trying each specific range until one was free (see isa_find_port() in isa_common.c). This is ugly but it does work. In the long run, I think we need either an extra parameter to rman_reserve_resource() or a new api rman_reserve_resource_aligned(). This also implies changing the method BUS_ALLOC_RESOURCE() or adding BUS_ALLOC_RESOURCE_ALIGNED(). -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
downed IP addresses/redundancy
This is an idea I had to help people provide for reduntant servers. Many programs will bind to all interfaces to serve requests, however sometimes it's important that a service only appear on a single IP or interface. However you'd really like the server to be able to bind to 2 IP addresses, one that you're serving for and another in case your sister server goes down. My idea is that you'd be able to ifconfig an IP to an interface but leave the IP 'deactivated', when another server goes down you can activate the IP address so that it will now take incomming requests. A 'hack' way of doing this would be to use IPFW and only add the extra IP after firewalling it off, when it'd needed then remove the block on the IP address. Does anyone particularly like/hate this idea? Just wanted to share, and possibly get better suggestions. The main problem I see is that now you have to hack around with routing otherwise you can't talk to the machine who's IP you're holding for replacement. thanks, -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: downed IP addresses/redundancy
Alfred Perlstein wrote: > > Does anyone particularly like/hate this idea? Just wanted to > share, and possibly get better suggestions. I usually do that like this: HostA -> Address1, Alias1 HostB -> Address2 ...where Host A and Host B talk to each other through the pair of "real" addresses, while the service network uses the address referred to above as "alias 1". When Host A goes away, Host B does an ifconfig alias to bring up the service net address on Host B. We just completed a full n-way local and wide area application level failover product that runs under FreeBSD 3.x. It does a lot of this for you, including maintaining heartbeat links, starting and stopping services, and the rest of the stuff you would expect from such a beast. Oh, and it runs cross platform; you can fail an Apache (or whatever) instance between Solaris, Linux and FreeBSD. Go check out the press release at the URL below. Yours, -- Jack Rusher, Chief Engineer | mailto:[EMAIL PROTECTED] Integratus, Inc.| http://www.integratus.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
java -> ld-elf.so.1: assert failed: ... lockdflt.c:55
Since the ~Jan 25 I have been getting an error while running any java programs on 3.4-stable. I cvsup'd,and ran a make world this afternoon and it still fails. It doesn't always hit... about 50% of the time. The errors is: ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 over and over and over... I can only kill the java process with -9. The process memory usage just climbs until it reaches about three times its normal size, and then it just freezes (no more assert failed messages) with 99% CPU util. The machine is: FreeBSD stronghold.guild.ab.ca 3.4-STABLE FreeBSD 3.4-STABLE #0: Thu Jan 27 17:04:43 MST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/STRONGHOLD i386 Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-STABLE #0: Thu Jan 27 17:04:43 MST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/STRONGHOLD Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x387f9ff,MMX,FXSR,> real memory = 134217728 (131072K bytes) avail memory = 127115264 (124136K bytes) Preloaded elf kernel "kernel" at 0xc034b000. Pentium Pro MTRR support enabled I haven't submitted this to -java as I am not subscribed, and the error doesn't seem to be directly java related; that is, should any process cause an assertion to fail in ld? I am about to move to -current, and the problem does not exist on any of our current boxes (this is my only stable box left), so I don't really have a reason to spend much time on it, but I thought I would throw it out and see if anybody bit. If any other information would be helpful let me know; otherwise, I know what I will be doing tomorrow afternoon. Thanks Chad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
SMP + Dual port Intel PRO/100+
-BEGIN PGP SIGNED MESSAGE- I was wondering if anybody has had problems with the dual port Intel PRO/100+ cards with a multi-processor kernel. We are getting device timeouts when booted into a SMP kernel. Things we have tried The card works fine with a single processor kernel... Reboot to a kernel with only the SMP added and it doesn't work. Two single Intel PRO/100+ cards work fine with SMP and also without. If anyone can give me any ideas on how else to debug this it would be appreciated. Thanks Corey - -- Corey Leopold E-Mail: Corey Leopold <[EMAIL PROTECTED]> Phone (210)-925-3459 - -- -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQCVAwUBOJHSRT3+cS8MmLXZAQGL4gP/WLjinqUCxlWlDM+Wc17Va+WSseXQkPU3 zmUgsvoAIq4dlHc3/g/gr7jfAxshuh1Cqx7olrMp33nFodMyVK8VSfxbgLsdbdlL 56iUcIc1jAmGJLkjFv+SR2OLN0tOtkvPO4PXPl/fGSuethDcIUTje69zxvu57HOn oWXNdZKBWgU= =16wF -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: java -> ld-elf.so.1: assert failed: ... lockdflt.c:55
In article <[EMAIL PROTECTED]>, Chad David <[EMAIL PROTECTED]> wrote: > > Since the ~Jan 25 I have been getting an error while > running any java programs on 3.4-stable. I cvsup'd,and > ran a make world this afternoon and it still fails. It doesn't > always hit... about 50% of the time. > > The errors is: > > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 [...] > FreeBSD stronghold.guild.ab.ca 3.4-STABLE FreeBSD 3.4-STABLE #0: Thu Jan > 27 17:04:43 MST 2000 I believe I fixed this one in -current 3 days ago, but I haven't merged it into -stable yet. I would appreciate it if you would try the patch below and let me know whether it clears up the problem for you. John Index: lockdflt.c === RCS file: /home/ncvs/src/libexec/rtld-elf/lockdflt.c,v retrieving revision 1.3.2.1 diff -u -r1.3.2.1 lockdflt.c --- lockdflt.c 2000/01/21 02:31:50 1.3.2.1 +++ lockdflt.c 2000/01/28 18:25:01 @@ -28,10 +28,9 @@ /* * Default thread locking implementation for the dynamic linker. It * is used until the client registers a different implementation with - * dllockinit(). The default implementation does mutual exclusion - * by blocking the SIGVTALRM, SIGPROF, and SIGALRM signals. This is - * based on the observation that most userland thread packages use one - * of these signals to support preemption. + * dllockinit(). The default implementation does mutual exclusion by + * blocking almost all signals. This is based on the observation that + * most userland thread packages use signals to support preemption. */ #include @@ -63,10 +62,13 @@ l = NEW(LockDflt); l->depth = 0; -sigemptyset(&l->lock_mask); -sigaddset(&l->lock_mask, SIGVTALRM); -sigaddset(&l->lock_mask, SIGPROF); -sigaddset(&l->lock_mask, SIGALRM); +sigfillset(&l->lock_mask); +sigdelset(&l->lock_mask, SIGTRAP); +sigdelset(&l->lock_mask, SIGABRT); +sigdelset(&l->lock_mask, SIGBUS); +sigdelset(&l->lock_mask, SIGSEGV); +sigdelset(&l->lock_mask, SIGKILL); +sigdelset(&l->lock_mask, SIGSTOP); return l; } To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SMP + Dual port Intel PRO/100+
On Fri, 28 Jan 2000, Corey Leopold wrote: > I was wondering if anybody has had problems with the dual port Intel > PRO/100+ cards with a multi-processor kernel. We are getting device > timeouts when booted into a SMP kernel. Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 ... fxp0: rev 0x05 int a irq 19 on pci2.4.0 fxp0: Ethernet address 00:08:c7:45:f4:e3 fxp1: rev 0x05 int a irq 16 on pci2.5.0 fxp1: Ethernet address 00:08:c7:45:f4:e4 ... FreeBSD sasami.jurai.net 3.4-STABLE FreeBSD 3.4-STABLE #3: Tue Jan 4 16:43:36 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/SASAMI i386 Sounds like your system isn't setting up the PCI-PCI bridge correctly when its in MP mode. Is there an MP version setting in the BIOS you can change? Are you running the latest BIOS? What board are you using? Processors? What is the exact error message? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: java -> ld-elf.so.1: assert failed: ... lockdflt.c:55
Yes this fixed it. Thanks. Chad On Fri, 28 Jan 2000, John Polstra wrote: > In article <[EMAIL PROTECTED]>, > Chad David <[EMAIL PROTECTED]> wrote: > > > > Since the ~Jan 25 I have been getting an error while > > running any java programs on 3.4-stable. I cvsup'd,and > > ran a make world this afternoon and it still fails. It doesn't > > always hit... about 50% of the time. > > > > The errors is: > > > > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 > [...] > > FreeBSD stronghold.guild.ab.ca 3.4-STABLE FreeBSD 3.4-STABLE #0: Thu Jan > > 27 17:04:43 MST 2000 > > I believe I fixed this one in -current 3 days ago, but I haven't > merged it into -stable yet. I would appreciate it if you would try > the patch below and let me know whether it clears up the problem for > you. > > John > > Index: lockdflt.c > === > RCS file: /home/ncvs/src/libexec/rtld-elf/lockdflt.c,v > retrieving revision 1.3.2.1 > diff -u -r1.3.2.1 lockdflt.c > --- lockdflt.c2000/01/21 02:31:50 1.3.2.1 > +++ lockdflt.c2000/01/28 18:25:01 > @@ -28,10 +28,9 @@ > /* > * Default thread locking implementation for the dynamic linker. It > * is used until the client registers a different implementation with > - * dllockinit(). The default implementation does mutual exclusion > - * by blocking the SIGVTALRM, SIGPROF, and SIGALRM signals. This is > - * based on the observation that most userland thread packages use one > - * of these signals to support preemption. > + * dllockinit(). The default implementation does mutual exclusion by > + * blocking almost all signals. This is based on the observation that > + * most userland thread packages use signals to support preemption. > */ > > #include > @@ -63,10 +62,13 @@ > > l = NEW(LockDflt); > l->depth = 0; > -sigemptyset(&l->lock_mask); > -sigaddset(&l->lock_mask, SIGVTALRM); > -sigaddset(&l->lock_mask, SIGPROF); > -sigaddset(&l->lock_mask, SIGALRM); > +sigfillset(&l->lock_mask); > +sigdelset(&l->lock_mask, SIGTRAP); > +sigdelset(&l->lock_mask, SIGABRT); > +sigdelset(&l->lock_mask, SIGBUS); > +sigdelset(&l->lock_mask, SIGSEGV); > +sigdelset(&l->lock_mask, SIGKILL); > +sigdelset(&l->lock_mask, SIGSTOP); > return l; > } > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: java -> ld-elf.so.1: assert failed: ... lockdflt.c:55
In article <[EMAIL PROTECTED]>, Chad David <[EMAIL PROTECTED]> wrote: > > Yes this fixed it. Thanks. Thanks for testing it. I have merged the fix into -stable now. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: downed IP addresses/redundancy
* Jack Rusher <[EMAIL PROTECTED]> [000128 07:42] wrote: > Alfred Perlstein wrote: > > > > Does anyone particularly like/hate this idea? Just wanted to > > share, and possibly get better suggestions. > > I usually do that like this: > > HostA -> Address1, Alias1 > HostB -> Address2 > > ...where Host A and Host B talk to each other through the pair of > "real" addresses, while the service network uses the address referred > to above as "alias 1". When Host A goes away, Host B does an > ifconfig alias to bring up the service net address on > Host B. > > We just completed a full n-way local and wide area application > level failover product that runs under FreeBSD 3.x. It does a lot of > this for you, including maintaining heartbeat links, starting and > stopping services, and the rest of the stuff you would expect from > such a beast. Oh, and it runs cross platform; you can fail an Apache > (or whatever) instance between Solaris, Linux and FreeBSD. Go check > out the press release at the URL below. Definetly a cool product, still the problem is that if you tell a daemon to bind to a particular IP address, let's take this scenario: You have multiple customers on two boxes, each customer gets 2 IP address and you lolad balance between the two. Some customers may wish to run thier own sql servers, they should only bind to the IP address on each machine that they own. Once you tell an application to bind to a particular IP address I'm pretty sure most don't have an option to bind another listen socket. The customer can't fail over properly because even when the alias for the box that dies comes up, thier daemon won't get requests on the added IP. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SMP + Dual port Intel PRO/100+
-BEGIN PGP SIGNED MESSAGE- On 28-Jan-00 Matthew N. Dodd wrote: > ... > > FreeBSD sasami.jurai.net 3.4-STABLE FreeBSD 3.4-STABLE #3: Tue Jan 4 > 16:43:36 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/SASAMI > i386 > > Sounds like your system isn't setting up the PCI-PCI bridge correctly when > its in MP mode. Is there an MP version setting in the BIOS you can > change? Are you running the latest BIOS? Couldn't find any such setting, Just upgraded to the latest bios no change... System stats Dell Precision Workstation 610 Processors 2 X 550Mhz ZEON Ram 256Meg Bios ver A09 (just changed from A08) Service Tag 5CLDU I'm not sure who dell had make the motherboard. Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Probing for devices on PCI bus 2: fxp0: rev 0x05 int a irq 11 on pci2.4.0 fxp0: Ethernet address 00:90:27:f0:9d:96 fxp1: rev 0x05 int a irq 15 on pci2.5.0 fxp1: Ethernet address 00:90:27:f0:9d:97 FreeBSD abs 3.4-RELEASE FreeBSD 3.4-RELEASE #2: Thu Jan 27 15:22:25 CST 2000 root@abs:/usr/src/sys/compile/ABS i386 And finally the error fxp0: device timeout With no response from the network. Thanks again Corey - -- Corey Leopold E-Mail: Corey Leopold <[EMAIL PROTECTED]> Phone (210)-925-3459 - -- -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQCVAwUBOJHquj3+cS8MmLXZAQGwmAP+IuAwNUZTUQ4KCAxhbk5aC/Mqn8l2dhkL V0cjQ4Rs6AAzR+p1B9x/JZ5sfVum60T/26sFGYQFk+OL4NAb2Go0raSf7pQMVRu2 YgGMvZbRUr7Rrf1E6AJItdMgC9toMcjjjS6ge5LLmbc6+Fjx7nfLMXl0h6sJVjFQ Rarcf3Vfmfc= =W4lR -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SMP + Dual port Intel PRO/100+
On Fri, 28 Jan 2000, Corey Leopold wrote: ... > FreeBSD abs 3.4-RELEASE FreeBSD 3.4-RELEASE #2: Thu Jan 27 15:22:25 CST 2000 > root@abs:/usr/src/sys/compile/ABS i386 > > And finally the error > > fxp0: device timeout > > With no response from the network. What is the board connected to? Hub? Switch? Can you specify media settings manually? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SMP + Dual port Intel PRO/100+
-BEGIN PGP SIGNED MESSAGE- On 28-Jan-00 Matthew N. Dodd wrote: > On Fri, 28 Jan 2000, Corey Leopold wrote: > ... > > What is the board connected to? Hub? Switch? Can you specify media > settings manually? > I've had it on a cross-over cable with a 100MB sparc on the other end, and also a 100MB Cisco Hub. Specifing the media settings doesn't change things. Also autoselect selects right (eg. 100baseTX full-duplex with the cross-over, and 100baseTX half-duplex with the hub.) I also tried 10baseT/UTP settings these don't work either. If I run tcpdump I can see arp traffic going out from the machine but I never see any other traffic. If I couldn't just boot into a single processor kernel and it worked, I would suspect that it is a bad cable. Thanks Corey - -- Corey Leopold E-Mail: Corey Leopold <[EMAIL PROTECTED]> Phone (210)-925-3459 - -- -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQCVAwUBOJH23T3+cS8MmLXZAQEqDAP/cZAGVvXX5Jh5l6mPcXceGRmLu0P9vQvH 623nNV3LDwAZwCwxNqfQyI6AGg6D7yeNZqY5SAa67jc35PONViiRbf55aVo0LFj/ /7ltw14uxAwcemnY+d+OzgaXf+fsOzw97AddhAzM8D1u+WZJA4va2lJgzcLhc42b qSqkYNtrt8U= =B2JB -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SMP + Dual port Intel PRO/100+
On Fri, 28 Jan 2000, Corey Leopold wrote: > If I couldn't just boot into a single processor kernel and it worked, I would > suspect that it is a bad cable. You might want to take the output of 'mptable' to -smp and ask there. Something isn't being setup correctly with regard to the PCI-PCI bridge on that card. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Compiling under the linux emulator
I was looking for this same info a while back, didn't find it in my search of the archives, please let me know if you have any success. thanks, -Charlie (compiled but not linked) On Thu, Jan 27, 2000 at 05:24:46PM -0600, Gene Harris wrote: > I need to compile a program under the freebsd linux > emulator. How do I set up an environment where make, > cc, etcetera point to the emulator binaries? > > I am attempting to recompile the xfstt port under the linux > emulator to test some stability issues. -- Charles Anderson[EMAIL PROTECTED] No quote, no nothin' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: downed IP addresses/redundancy
Alfred Perlstein wrote: > > You have multiple customers on two boxes, each customer gets 2 > IP address and you lolad balance between the two. Ah! I see your difficulty. I was thinking about availability; you were thinking about load balancing. > Some customers may wish to run thier own sql servers, they should > only bind to the IP address on each machine that they own. > > The customer can't fail over properly because even when the alias > for the box that dies comes up, thier daemon won't get requests on > the added IP. You have worse trouble than that. If you are running an order/entry database, you don't want the service to fail over to the second machine without remote synchronization of the data. Otherwise, you end up with two databases that have entries that compete for the same serial numbers. No one likes hand merging orders. :-) This also makes it important that the database only ever run on one machine at a time. You would want to start the database on the machine that holds the service net address, right after you do the ifconfig to bring up that address on the secondary's interface. Can you give me some more complete scenarios? I am interested in your problem. Yours, -- Jack Rusher, Chief Engineer | mailto:[EMAIL PROTECTED] Integratus, Inc.| http://www.integratus.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
3.4 cdroms and xdm
A few questions: Am I insane or is my FreeBSD 3.4 install disk from Walnut Creek bad? I can not get it to boot and boot disks created with it do not work. Will boot disks created from the web source work? I seem to vaguely remember something about this but can not remember where or what was said. Also, I managed to get xdm to go active at boot time on my 3.3 machine but it would not let anyone in. I used the line in the ttys file and just changed the off to on. Is this problem covered somewhere? I have not found anything and would really like to avoid command line startx for my users. Any help will be greatly appreciated. james To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 3.4 cdroms and xdm
Re: XDM problem. Make sure that each users' .xsession file is set as executable for the owner. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: downed IP addresses/redundancy
* Jack Rusher <[EMAIL PROTECTED]> [000128 15:04] wrote: > Alfred Perlstein wrote: > > > > You have multiple customers on two boxes, each customer gets 2 > > IP address and you lolad balance between the two. > > Ah! I see your difficulty. I was thinking about availability; you > were thinking about load balancing. > > > Some customers may wish to run thier own sql servers, they should > > only bind to the IP address on each machine that they own. > > > > The customer can't fail over properly because even when the alias > > for the box that dies comes up, thier daemon won't get requests on > > the added IP. > > You have worse trouble than that. If you are running an order/entry > database, you don't want the service to fail over to the second > machine without remote synchronization of the data. Otherwise, you > end up with two databases that have entries that compete for the same > serial numbers. No one likes hand merging orders. :-) This also > makes it important that the database only ever run on one machine at > a time. You would want to start the database on the machine that > holds the service net address, right after you do the ifconfig to > bring up that address on the secondary's interface. > > Can you give me some more complete scenarios? I am interested in > your problem. Consider phk's Jail code, giving each user a true virtual server of some sort, there's no way for it suddenly bind to another specific IP address without a restart. I think this issue should be addressed by the application designers as well, you _should_ be able to tell... let's say bind to grab another interface at runtime. maybe ndc allows this i'll have to look. -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how to allocate an alined address for a device?
In message <[EMAIL PROTECTED]> Doug Rabson writes: : I'm uneasy about using the flags for this since I'm vaguely reserving the : upper 16 bits of flags for bus-specific purposes (although I haven't : formalised this). : : For allocating aligned regions with pnp, I simply looped in the caller : trying each specific range until one was free (see isa_find_port() in : isa_common.c). This is ugly but it does work. : : In the long run, I think we need either an extra parameter to : rman_reserve_resource() or a new api rman_reserve_resource_aligned(). : This also implies changing the method BUS_ALLOC_RESOURCE() or adding : BUS_ALLOC_RESOURCE_ALIGNED(). Well, with just 6 bits one could handle any alignment requirement up to 2^(2^6). We have 6 bits left. If this were the alignment requirement, a value of 0 would mean 2^0 or 1, which is the current behavior. More restrictive alignment requirements could be encoded easily. No ABI or API change needed. #define RF_ALIGNMENT_MASK 0xfc00 #define RF_ALIGNMENT_SHIFT 10 #define RF_ALIGNMENT_LOG2(x)(x << RF_ALIGNMENT_SHIFT) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Compiling under the linux emulator
All you need to do is modify your path to include whatever linux subdirs you need referenced first, such as PATH=/usr/compat/linux/bin:$PATH;export PATH. You may need to add other subdirs as well, according to any errors you might receive. That is all it takes. And, it works! *==* *Gene Harris http://www.tetronsoftware.com* *FreeBSD Novice* *All ORBS.org SMTP connections are denied! * *==* On Fri, 28 Jan 2000, Charles Anderson wrote: > I was looking for this same info a while back, didn't find it in my > search of the archives, please let me know if you have any success. > > thanks, > -Charlie (compiled but not linked) > > On Thu, Jan 27, 2000 at 05:24:46PM -0600, Gene Harris wrote: > > I need to compile a program under the freebsd linux > > emulator. How do I set up an environment where make, > > cc, etcetera point to the emulator binaries? > > > > I am attempting to recompile the xfstt port under the linux > > emulator to test some stability issues. > -- > Charles Anderson [EMAIL PROTECTED] > > No quote, no nothin' > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: downed IP addresses/redundancy
Alfred Perlstein <[EMAIL PROTECTED]> wrote: > >Once you tell an application to bind to a particular IP address >I'm pretty sure most don't have an option to bind another listen >socket. > >The customer can't fail over properly because even when the alias >for the box that dies comes up, thier daemon won't get requests on >the added IP. What would be cool is if FreeBSD could do VRRP. This is usually used for providing a default route handled by two physical boxen, but if you turn it around and provide a route to a service IP address that may be handled by two boxen that deal with fail-over using VRRP then this solves the problem discussed in this thread. I'd be interested to know of a free implementation of VRRP for the BSD network stack. Tony. -- dot it thus To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 3.4 cdroms and xdm
Kurt Olsen wrote: > > Re: XDM problem. > > Make sure that each users' .xsession file is set as executable for the > owner. And, for any user who cannot login via XDM, login over the network and read the .xsession-errors file created in their home directory. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 3.4 cdroms and xdm
>And, for any user who cannot login via XDM, login over the network and >read the .xsession-errors file created in their home directory. Additionally, if you don't have a network you can hit Ctrl-F1 to get back to a text terminal. Or just enter the username, hit Enter, enter the passwordd and hit F1 which will log you in in failsafe mode. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
using pipes
I'm working on a project where one process will be working with a stream of data from a series of separate processes. We currently have an architecture where process A (the controller) starts up process B (the source). The output from B is directed into a named pipe (created earlier with mkfifo). Meanwhile, process C (the sink) is reading from the named pipe. After B exits, A will start up a new one, and so one. [Side note: We have little control of process B. It is a program from another source that simply outputs to stdout. We redirect its stdout to the named pipe.] This system works, but has occasional glitches where the output stream from C is momentarily interrupted. They appear to be due to the 4K capacity of the pipe, combined with the fact that new data from B is not appearing in the pipe until after the pipe is completely empty. As C reads, the size of the pipe decreases until it reaches 0, at which point it suddenly jumps back to 4096. Occasionally, C will read the pipe again after it has been emptied, but before B has finished filled it again. When that happens, there is a momentary break in C's output, which is undesirable. One thought I've had to try to resolve the problem is to use a regular pipe instead of a named pipe. Process A would create a pipe, then fork off C which would keep its end of the pipe open for the duration of its run (days, weeks, months... this ain't NT! :) Then A would fork off the series of B processes, one at a time, with their stdout mapped to the input of the pipe. What I'm wondering is if there might be any problem with having a whole series of processes outputting to the same pipe, which is held open by a long-lived process at the other end of the pipe. Or would this arrangement be likely to have the same problem as the current one? For that matter, does anyone have better suggestions how to proceed? Thanks for your insight, and please CC: me on replies. Dave -- Dave Walton[EMAIL PROTECTED] -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Acceptable MBUF levels?
On Wed, 26 Jan 2000, Bosko Milekic wrote: > > On Wed, 26 Jan 2000, Doug White wrote: > > >When people refer to mbufs, they refer to mbuf clusters, of which there's > >a fixed number. The kernel will allocate more mbufs as necessary. > > Uhm, actually, mbufs are also allocated from mb_map. Thus, they are > also capped. (Unless I'm missing something big again... :-) ) That would be correct, at least looking at the appropriate code in /sys/kern/uipc_mbuf.c. The read-only sysctls kern.ipc.nmbclusters and kern.ipc.nmbufs hold the max mbuf clusters and the max mbufs, respecively. kern.ipc.nmbufs is bound to an nmbufs value in there, but I can't figure out to what value it's initialized to. > >The usual rule of thumb is that the peak should never exceed 75% of the > >max mbufs in the system to allow for sufficient overhead in extreme > >situations. In this case you're at 80%, so you should probably recompile > >your kernel and bump maxusers. > > Actually, for mbufs and mbuf clusters, you should increase > NMBCLUSTERS, which will serve as an indication of allocate-able clusters > as well as, ultimately, mbufs. Increasing maxusers has the side effect of increasing NMBCLUSTERS according to this formula (from /sys/conf/param.c): #ifndef NMBCLUSTERS #define NMBCLUSTERS (512 + MAXUSERS * 16) #endif You only have to override NMBCLUSTERS by hand if you want a truly gigantic (i.e. > 10,000) number of nmbclusters. Just be VERY CAREFUL doing so since you can *reduce* the number, and that's not good! >From personal experience, 512 maxusers and 16384 nmbclusters is more than enough for just about anything -- just make sure you can handle a 17MB kernel. :-) Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
