[Fwd: about vbox and freebsd]
I got an answer to my question, posted here, from ... but I've been instructed not to post to individuals but to the list so I copy the Mak's response here : snip Your CPU is 64-bit from what I can see. From a bit of Googling, others have encountered this problem, and it seems to have to do with VM-X. I have no idea what that is, but a thread in which someone has a very similar issue is here: http://forums.virtualbox.org/viewtopic.php?f=1t=19420 One notable quote is: ...[the CPU] does not have Intel VT (hardware virtualization), so you will not be able to run 64 bit guests in Virtualbox even though you run a 64 bit host. HTH /snip So, OK. I cannot have 64 bit guests using virtual box. I have installed the 32 bit version of FreeBSD... but it has no X and apparently no networking because the ftp from pkg_add failed. Did I do something wrong in the install, or do I really have to configure all that stuff by hand? Thanks for your help. -- John Francis Lee 1025/37 Thanon Jet Yod Mueang Chiangrai 57000 Thailand ---BeginMessage--- 08/20/2009 11:59 PM Hello Duncan Hutty, I write to you directly because I have posted several times to the list and have not seen an answer to my problem, and you seem knowledgeable about freebsd. I have a dual-core amd64 machine running ubuntu 9.04 with vbox 3.04 and have tried to create a freebsd guest on it. I've had a freebsd webserver at iserver/viaverio for about 15 years but still have not set up a freebsd box of my own where I can really learn the ins and outs of the system, and I'd like to. My problem is that I'm told right at the onset of the install that CPU doesn't support long mode Someone suggested that I was trying to install a 64 bit os on 32 bit system, but I don't think that's the case : j...@ws3:~$ hwinfo --cpu 01: None 00.0: 10103 CPU [Created at cpu.304] Unique ID: rdCR.j8NaKXDZtZ6 Hardware Class: cpu Arch: X86-64 Vendor: AuthenticAMD Model: 15.107.2 AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ Features: fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,nx,mmxext,fxsr_opt,rdtscp,lm,3dnowext,3dnow,rep_good,pni,cx16,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,3dnowprefetch Clock: 1000 MHz BogoMips: 2009.02 Cache: 512 kb Units/Processor: 2 Config Status: cfg=new, avail=yes, need=no, active=unknown 02: None 01.0: 10103 CPU [Created at cpu.304] Unique ID: wkFv.j8NaKXDZtZ6 Hardware Class: cpu Arch: X86-64 Vendor: AuthenticAMD Model: 15.107.2 AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ Features: fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,nx,mmxext,fxsr_opt,rdtscp,lm,3dnowext,3dnow,rep_good,pni,cx16,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,3dnowprefetch Clock: 1000 MHz BogoMips: 2009.02 Cache: 512 kb Units/Processor: 2 Config Status: cfg=new, avail=yes, need=no, active=unknown I'm then dumped into an OK prompt and unable to do much more. Have you seen or heard of this before? Sorry to bother you if you have no clue yourself. Thanks for any help you might be able to give. -- John Francis Lee 1025/37 Thanon Jet Yod Mueang Chiangrai 57000 Thailand 08/15/2009 10:38 PM My problem seems to be that CPU doesn't support long mode Is that it? Can't get there from here? -- John Francis Lee 1025/37 Thanon Jet Yod Mueang Chiangrai 57000 Thailand 08/15/2009 10:20 PM Hi, I got a new machine, a linux ubuntu-running AMD64 based one, and thought I'd try out FreeBSD here at home. But when I begin the VirtualBox installation I get dumped into a shell-looking terminal with an OK prompt. I can't read all the instructions and frankly cannot do anything with it. I tried hitting the 2 before the timeout to boot with ACPI disabled but that seems not to make any difference. Have you heard of this problem before? Any help you might give appreciated. Thanks. I'll go see if the VirtualBox people can shed any light on the matter as well. -- John Francis Lee 1025/37 Thanon Jet Yod Mueang Chiangrai 57000 -- John Francis Lee 1025/37 Thanon Jet Yod Mueang Chiangrai 57000 Thailand ---End Message--- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Suspend/Resume on Thinkpad x40
On Fri, Aug 21, 2009 at 11:53 PM, Ian Smithsmi...@nimnet.asn.au wrote: On Fri, 21 Aug 2009, Joe Snikeris wrote: On Thu, Aug 20, 2009 at 10:58 PM, Ian Smithsmi...@nimnet.asn.au wrote: On Thu, 20 Aug 2009 14:03:29 -0500 Joe Snikeris j...@snikeris.com wrote: First off, I apologize if this is not the right forum for this question. I was torn between posting this in mobile, ACPI, X11 and here. If I might get a better response in one of those forums, please let me know and I'll post there instead. I suspect -mobile might be the best list for this one, perhaps -acpi but that's usually more about development than usage. You might try searching the archives of either for mention of the X40. I'm having some trouble getting the kinks worked out of the suspend/resume functionality on my laptop, an IBM Thinkpad X40. It is mostly working now, but I am still experiencing some strange behavior. I can suspend and resume from a console just fine (except for the fact that the console comes up blank and only displays new characters); however, suspending and resuming in X is problematic. The first suspend and resume in X works perfectly, but the next time I hit suspend, the machine locks up while still displaying whatever I was doing in X. Note that if I switch to a virtual terminal before hitting suspend, this problem does not occur. Does anyone have any suggestions on what I might do to get this resolved? The details of my machine follows; please let me know if any additional information would be helpful. My T23 requires hw.syscons.sc_no_suspend_vtswitch=1 to suspend/resume cleanly (7.0), so does my old Compaq Armada (but that's APM, not ACPI) Thanks Ian. This fixed the problem where suspend would hang the second time it was executed in X. Good to know another model that this works on, for the archives. At any rate, I gave up on ACPI. I've got suspend-to-ram and suspend-to-disk (hibernation) working perfectly using APM. Does anyone know if there are any disadvantages related to power-saving features when using APM over ACPI? Is powerd able to do its job just as well? The answer to that (at 5.5-STABLE) used to be 'no', but there is some APM code in powerd.c, related to how it determines the AC line state, though it's not clear to me if it would require compiling APM in kernel. Certainly /etc/rc.d/power_profile can't set CPU CX states without ACPI. Ok. Just did a search to find out what CPU CX states were. For a good explanation of the CX states: http://lists.freebsd.org/pipermail/freebsd-current/2009-May/006436.html Switching speeds relies on the dev.cpu.0.freq and dev.cpu.0.freq_levels sysctls - are these available when you're running on APM? If so, try running powerd(8) in verbose foreground mode (-v) and see what happens. Yes they are. And powerd in verbose foreground mode shows that it is lowering the frequency all the way down to 75 MHz depending on the load. Cool. Thanks again, Ian. Take care, Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RAID10 setup
This question was asked a few weeks ago, but the original poster must have had their questions amswered. As follow-ups offered further assistance given more detail, I wonder if I could be so bold as to provide that detail for my own circumstances. I have six disks: ad4 - 500MB ad5 - 500MB ad6 - 500MB ad7 - 400MB ad8 - 500MB ad10 - 500MB These are SATA drives, with ad8 and ad10 on a PCIe SATA controller. ad7 was my first disk and currently contains FreeBSD7.2-RELEASE. I've been using that to gain some familiarity with FreeBSD, but it need not be preserved (in fact, I'd rather not preserve it!). When I built the machine, I just plugged the 400GB drive in any old slot, so it can move if that makes sense. When I got the new drives I tried to get identical to the 400GB drive, but couldn't. The 400GB drive currently has a single slice using the full drive. What I'd like to end up with is a three-way stripe across three two-way mirrors, containing as much of the system as possible. I understand that you can't boot from a stripe, so some part of some disk will have to be outside the stripe. However, as the stripe will also be limited to the smallest disk, I'm going to have 5 x 100 GB bits left over anyway, so I guess /boot can go on one of these..? If possible, I'd like set this up pre-install. If it has to be done post-install, or is easier to describe how to do post-install, then that's fine. From here on in, this email becomes speculative. All of the examples I've seen for setting up GEOM stripes and mirrors have used the raw disk as the base-level provider. On the other hand, I've seen nothing that says that the bottom level cannot be a slice, rather than a raw disk, and given the way GEOM works, I suspect this is true. My current plan, based on this assumption, is as follows: With my current FreeBSD installation, create 2 slices on each 500GB disk, 1 x ~400GB, 1 x ~100GB (the same size as the slice of my 400GB disk, and the rest of the disk). Boot from the FreeBSD 7.2-RELEASE dvd, and enter fixit mode. I'm not sure which would be best, or even if both are feasible for what I want to do. (I was at this point in my researchwhen I found this post!). From here, kldload geom_stripe and kldload geom_mirror. Then, create the three mirrors: gmirror label -v main0 /dev/ad4s1 /dev/ad5s1 gmirror label -v main1 /dev/ad6s1 /dev/ad571 gmirror label -v main2 /dev/ad8s1 /dev/ad10s1 This should give me /mirror/main0|main1|main2, right? Next create the stripe: gstripe label -v -s 131072 raid10 /dev/mirror/main0 /dev/mirror/main1 /dev/mirror/main2 (that's all one line) If I'm right so far, then hopefully I should be able to boot to the install dvd again (or just rerun sysnstall?), and from there I should be able to choose a slice from outside 'raid10' to mount /boot, and use 'raid10' for everything else. Do I need anything else on a non-striped slice? Maybe I could even create another mirror: gmirror label -v boot /dev/ad4s2 /dev/ad5s2 and use that to mount /boot, leaving me with s2 on ad6,8 and 10 as 3 spare 100GB slices? Or am I just way off track? PS. I can't believe I'm talking about 300 'spare' GB! My first disk was 20MB! And I never filed that! All guidance much appreciated. Phil On 30 July, 15:03, John Nielsen li...@jnielsen.net wrote: On Wednesday 29 July 2009 15:54:42 Richard Fairbanks wrote: OK, so this is what I want to do. I have 4 big fast drives that I want to run inRAID10 (1+0). So, I'll need to mirror two sets of two disks, then ... Of course, if there is a way to create the stripedsetoff mirrors before installation then installing onto that stripe, that'd be perfect. I don't know if that can be done. I'm sure someone has configured aRAID10 standalone system before. (Oh, I'm using 7.2). I'm just stuck at this point! You need to consider where/how you are going to boot the system. It's straightforward to boot from a gmirror'ed UFS filesystem (the BIOS just uses one disk and thinks everything is normal), but you can't do the same from a stripe. You will either need a separate disk/device for your / or /boot partition or you will need to use slices/partitions on your disks. I frequently have the root filesystem on a small gmirror (partitions on 2 disks) then use the equivalent extra space on the remaining disk(s) for swap. Youi should be able to do this pre-installfrom the Fixit shell. Boot to the live CD, enter the shell, kldload geom_mirror and geom_stripe, create the mirrors, create the stripe, exit the shell, start theinstall, and tell sysinstall to use the device node under /dev/stripe for your filesystem. Alternatively you could just do a regularinstallto one of the disks and do everything post-install. In this case you'd still create two mirrors but one of them would only contain a single disk at first. Then create your stripe, dump/restore your files, update fstab (in
Re: /etc/rc.d/named dilemma
On Fri, Aug 21, 2009 at 09:37:09PM -0700, Nerius Landys wrote: I am trying to figure out why DNS lookups are not possible right after the named process has been launched (during bootup). At start, named sends a couple of queries to e.g. root servers. All this requires the network connection to be already up and running; and if you're using a firewall, it also needs to be up and ready. And, more importantly, it requires some time until named is ready to answer lookups... and in the mean time, you've already launched other processes who do queries. I have a similar problem with a little FreeBSD-based home router running net/mpd5 to connect via PPPoE to a DSL line. Because packages (and so mpd) start after all system processes, named has problems to connect to the root servers, pf has problems initializing itself without ng0 interface, ntpd has problems initializing itself,... and when mpd finally established the network connection, it is already too late. I'd love to change the rc-order of the scripts, so that mpd starts first, waits until the link is up, and only then starts the other processes. But until I've found out how to do that the right way, I wrote a little batch script that gets invoked at link-up, and that simply restarts all other processes in the order: pf, named, ntpd, postfix, etc... That's not ideal, but as a kludge, it works for me. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [Fwd: about vbox and freebsd]
John Francis Lee wrote: I got an answer to my question, posted here, from ... but I've been instructed not to post to individuals but to the list so I copy the Mak's response here : snip Your CPU is 64-bit from what I can see. From a bit of Googling, others have encountered this problem, and it seems to have to do with VM-X. I have no idea what that is, but a thread in which someone has a very similar issue is here: http://forums.virtualbox.org/viewtopic.php?f=1t=19420 One notable quote is: ...[the CPU] does not have Intel VT (hardware virtualization), so you will not be able to run 64 bit guests in Virtualbox even though you run a 64 bit host. HTH /snip Something sounds strange here. The name for Intel's hardware virtualization feature is VT-I, or sometimes VT-x, while AMD's name for the same thing is AMD-V. Your processor supports AMD-V and VirtualBox supports both, at least in the version 3.0.4 that I am running. Alas, my processor is Intel and if there actually is a problem of VirtualBox not being 64 bit capable with AMD-V I cannot test. Since your host system is Ubuntu I am also wondering if the problem could involve their packaging of the product, e.g., an older version of VirtualBox such as 2.x or some such. Also wonder if it needs to be manually turned on in BIOS. Also I believe the 64 bit support is relatively new so you might want to check which version of VirtualBox it became included as a new feature and compare that against the version you have. Since this is a FreeBSD list I'm just going to say it could be an Ubuntu problem, and leave it at that. So, OK. I cannot have 64 bit guests using virtual box. I have installed the 32 bit version of FreeBSD... but it has no X and apparently no networking because the ftp from pkg_add failed. Did I do something wrong in the install, or do I really have to configure all that stuff by hand? Don't know. But the default VirtualBox networking is NAT, with it supplying DHCP services to the client. You may need to enter a line in your (FreeBSD) /etc/rc.conf similar to: ifconfig_rl0=DHCP where rl0 would be whatever is your network interface. When it boots (the FreeBSD guest) it should be assigned an IP something like 10.0.2.15 and a default gateway something like 10.0.2.2. These can vary. Also be aware that while you can connect outbound and receive return traffic you will be unable to initiate inbound connections. If you require this ability you will need to manually set up VirtualBox in bridge mode, which also requires some non-trivial config changes to your host OS. Like I said, something just sounds fishy to me because on the VirtualBox 3.0.4 that I run it clearly supports both Intel and AMD hardware virtualization. Since I don't have the AMD processor to try it myself I can't confirm. At any rate, if the 32 bit FreeBSD runs and satisfies your needs why keep fiddling. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Suspend/Resume on Thinkpad x40
On Sat, 22 Aug 2009, Joe Snikeris wrote: On Fri, Aug 21, 2009 at 11:53 PM, Ian Smithsmi...@nimnet.asn.au wrote: On Fri, 21 Aug 2009, Joe Snikeris wrote: On Thu, Aug 20, 2009 at 10:58 PM, Ian Smithsmi...@nimnet.asn.au wrote: [..] At any rate, I gave up on ACPI. I've got suspend-to-ram and suspend-to-disk (hibernation) working perfectly using APM. Does anyone know if there are any disadvantages related to power-saving features when using APM over ACPI? Is powerd able to do its job just as well? The answer to that (at 5.5-STABLE) used to be 'no', but there is some APM code in powerd.c, related to how it determines the AC line state, though it's not clear to me if it would require compiling APM in kernel. Certainly /etc/rc.d/power_profile can't set CPU CX states without ACPI. Ok. Just did a search to find out what CPU CX states were. For a good explanation of the CX states: http://lists.freebsd.org/pipermail/freebsd-current/2009-May/006436.html Good hunting; a good overview of current load/power handling on FreeBSD, also posted to -mobile and/or -acpi as I recall. Switching speeds relies on the dev.cpu.0.freq and dev.cpu.0.freq_levels sysctls - are these available when you're running on APM? If so, try running powerd(8) in verbose foreground mode (-v) and see what happens. Yes they are. And powerd in verbose foreground mode shows that it is lowering the frequency all the way down to 75 MHz depending on the load. Cool. At 75MHz, it should be :) cheers, Ian___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What should be backed up?
Jeffrey Goldberg wrote: On Aug 21, 2009, at 2:33 PM, John Almberg wrote: I am currently using rsnapshot to back up these directories on a FreeBSD 7.2 webserver: /etc /usr/home /usr/local /var/cron Here is my exclude list from my rsnapshot.conf exclude /var/log exclude /var/tmp exclude /usr/obj exclude /usr/ports/distfiles exclude /usr/local/squid Also I backup by file system, so I'm already excluding /tmp Yes, it's easy to miss something that should have been backed up. There is no point in backup of files other than those you modify yourself, unless you plan to create an exact image and recover using dd. After installation you can do # date /tmp/TIMESTAMP then you can create a list of files that have been modified after that time with find, # find / -newer /tmp/TIMESTAMP /tmp/backupfilelist If you have a backup cronjob, then you can use the same method to backup only files modified since last backup. On a base system with no services running, I'd restrict backup to /etc /home If you've got any ports installed, add /usr/local/etc /var/db/ports What else to add to the list really depends on which services you run, named, mail, cvs, web, ftp, nis, etc. and if these have critical files in other directories. If you have any databases or ldap service, then you want to add those as well, but it is recommended to dump these rather than backup the files themselves. I wouldn't backup source or the ports distribution, you have an online backup available :) If you rely on a particular snapshot, then you should configure that in your supfiles. But if you need to recover without network access you should backup source and the ports tree as well as distfiles or build packages whenever you install from ports and keep those backed up. BR, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to install ien-firmware on Freebsd 7.2 Stable?
Hello Anybody knows how to install iwn-firmware on Freebsd 7.2 Stable? (I need it for: Intel Wireless WiFi Link 4965AGN) I do not have /usr/ports/net/iwn-firmware dir since it is only in 8.0. Is a way to install it and use that firmware? I've searched alot on Google, but I did not find a howto for installation of wifi firmwares to FreeBSD (other that with make install from ports, which is possible only if I have the firmware for my freebsd). I want to use a firmware from here: http://www.intellinuxwireless.org/?n=downloadsf=ucodes_4965 best regards ovi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /etc/rc.d/named dilemma
On Fri, 21 Aug 2009 21:37:09 -0700
Nerius Landys nlan...@gmail.com wrote:
Then why
can't I do a lookup right after named starts?
Possibly it's a delay in bind being ready or maybe you don't have any
network access - the latter is common with ppp.
By the way, the underlying issue that I'm trying to address is that
ntpdate, which comes right after named in the boot sequence, is not
able to resolve the DNS for the time servers.
Try putting the following in /usr/local/etc/rc.d/waitfordns and make it
executable (untested)
#!/bin/sh
#
# PROVIDE: waitfordns
# REQUIRE: named
# BEFORE: ntpdate
. /etc/rc.subr
: ${waitfordns_enable:=yes}
name=waitfordns
rcvar=`set_rcvar`
stop_cmd=:
start_cmd=waitfordns_start
waitfordns_start(){
/usr/bin/dig +time=1 +retry=99 @127.0.0.1 google.com 21 /dev/null
}
load_rc_config ${name}
run_rc_command $1
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Crash dump freebsd 7.2
I have several jails running on my freebesd machine and lately it started to crash when it gets a bit loaded. I followed the freebsd kernel debugging manual, and got some output, but I have no idea what to do with it. The only thing I think I understand of it that the bit that matters are just the two last lines. Is there anyone that can help? # kgdb kernel.debug /var/crash/vmcore.2 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x10 fault code = supervisor read, page not present instruction pointer = 0x20:0xc07d4a21 stack pointer = 0x28:0xe9c879c4 frame pointer = 0x28:0xe9c879d8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 18223 (libssl.so) trap number = 12 panic: page fault cpuid = 1 Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x6e727598 fault code = supervisor read, page not present instruction pointer = 0x20:0xc08bf945 stack pointer = 0x28:0xc72bfaa8 frame pointer = 0x28:0xc72bfacc code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 30 (em1 taskq) trap number = 12 panic: page fault cpuid = 1 Uptime: 12h20m45s Physical memory: 3827 MB Dumping 295 MB: 280 264 248 232 216 200 184 168 152 136 120 104 88 72 56 40 24 8 Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/nullfs.ko...Reading symbols from /boot/kernel/nullfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/nullfs.ko Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from /boot/kernel/fdescfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/fdescfs.ko #0 doadump () at pcpu.h:196 196 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /etc/rc.d/named dilemma
Thanks for the script. I found the underlying problem on my system.
My server is at a data center and I don't know what kind of equipment
the server is connected to. It appears that it takes 30 seconds for
the networking to start. I added this script as
/etc/rc.d/waitfornetwork, and enabled it in rc.conf:
===
#!/bin/sh
# PROVIDE: waitfornetwork
# REQUIRE: NETWORKING
# BEFORE: named
. /etc/rc.subr
: ${waitfornetwork_enable:=NO}
name=waitfornetwork
rcvar=`set_rcvar`
stop_cmd=:
start_cmd=waitfornetwork_start
waitfornetwork_start()
{
echo Waiting for network to initialize.
for i in 0 1 2 3 4 5 6 7 8 9; do
#echo Iteration $i
if ping -c 1 198.41.0.4 | grep -q '^1 packets transmitted, 1
packets received, 0.0% packet loss'; then
break
fi
done
}
load_rc_config ${name}
run_rc_command $1
===
It goes through 4 or 5 iterations (the for loop) before it exits.
This takes about 30 seconds. Without this startup script, ntpdate and
ntpd fail, regardless of whether or not I use named as my local DNS
caching server. With this script enabled, ntpdate and ntpd are able
to resolve the listed DNS for the time servers, regardless of whether
I'm using 127.0.0.1 or some other DNS in my resolv.conf.
This 30 second delay for the network to start on every reboot (at the
data center) - is this normal?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /etc/rc.d/named dilemma
One last question. I'm getting interesting [kernel?] messages during bootup. You know, the kind that are highlighted white in the console. The relevant lines of rc.conf look like this right now: defaultrouter=64.156.192.1 hostname=daffy.nerius.com ifconfig_em0=inet 64.156.192.169 netmask 255.255.255.0 waitfornetwork_enable=YES named_enable=YES sshd_enable=YES #ntpdate_enable=YES ntpd_enable=YES linux_enable=YES apache22_enable=YES mysql_enable=YES Early on in the bootup, the ifconfig shows for em0: inet 64.156.192.169 ... media: Ethernet autoselect status: no carrier Then later on: Waiting for network to initialize. highlightedem0: link state changed to UP/highlighted highlightedcalcru: runtime went backwards from 37332 usec to 16577 usec for pid 47 (sh).../highlighted ... (more messages about calcru) And then everything starts fine, including ntpd. Why is em0 only brought up when I do my ping command in /etc/rc.d/waitfornetwork? And are these calcru messages something to be worried about? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /etc/rc.d/named dilemma
highlightedcalcru: runtime went backwards from 37332 usec to 16577 usec for pid 47 (sh).../highlighted Not to seem like I'm talking to myself, but I fixed this problem: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIVE-RUNTIME (Turn off Intel® Enhanced SpeedStep.) I am still bambuzzled by the network taking 30 seconds to come up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /etc/rc.d/named dilemma
Nerius Landys wrote: I am still bambuzzled by the network taking 30 seconds to come up. I don't remember the original description, but any time I hear about a 30 second gap during startup, I think of the well-known DNS reverse look-up issue. Are you sure this is not the case here? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /etc/rc.d/named dilemma
I don't remember the original description, but any time I hear about a 30 second gap during startup, I think of the well-known DNS reverse look-up issue. Are you sure this is not the case here? Indeed, I have forgotten to have the PTR record set up for my new IP address. However the original description is that when I issue a ping -c 100 x.y.z.w to a well-known IP address, only the last 70 packets get returned, not the first 30 (hence 30 seconds). This ping command is issued very early in the rc.d scripts, after NETWORK and before named, and the script does not exit until a ping request is successful. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /etc/rc.d/named dilemma
On Saturday 22 August 2009 21:11:01 Nerius Landys wrote: I don't remember the original description, but any time I hear about a 30 second gap during startup, I think of the well-known DNS reverse look-up issue. Are you sure this is not the case here? Indeed, I have forgotten to have the PTR record set up for my new IP address. However the original description is that when I issue a ping -c 100 x.y.z.w to a well-known IP address, only the last 70 packets get returned, not the first 30 (hence 30 seconds). This ping command is issued very early in the rc.d scripts, after NETWORK and before named, and the script does not exit until a ping request is successful. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Nerius; I had the same problem until I put: # REQUIRE: SERVERS cleanvar ppp-user in /etc/rc.d/named script, which means that named won't start until the ppp -ddial adsl command, which is called by in /etc/rc.d/ppp-user, is finished. By then, DNS and default route will be established. I also put: # PROVIDE: ppp-user in /etc/rc.d/ppp-user. Sorry for writing you directly but I don't know why, the freebsd-questions list (in fact, all freebsd lists i'm subscribed to) is refusing my posts. Not even the list manager/owner gets them. If you would be so kind to forward this to them, I'd be very greatful. Maybe they could find out why so I could take action to try remedy what is causing the refusals of my e-mail. Thanks and Best wishes, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winedows FREE) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: No Device Node assigned for HD?
Rob wrote: The only difference I've found is that in the RocketRAID BIOS, the 3 500GB drives are recognized with a Legacy Status, whereas the 1TB is recognized as New Status. Not sure what that means or how to change it. Your problem is that the old drives you have hooked up to the RocketRAID card all have a partition table. When the RR BIOS sees that partition table it assumes it is a Legacy drive and exposes it to the OS as a single drive JBOD array. Your brand new 1 TB drive has nothing on it, and your RocketRAID card is waiting for you to initialize it and create an array with it before exposing it to the OS. You have two options: 1. Use the RR2310 BIOS screen (or hptraidconf from inside FreeBSD) to initialize the drive and create a single drive JBOD array with it. 2. Connect the drive to a header on your motherboard and create a partition table on it, then reconnect it to your RR2310 card. Partition table example: # gpart create -t GPT adXX # gpart add -b YY -s ZZ -t freebsd-ufs adXX /Daniel Eriksson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
