pkg_updating -d
Hello, I am new to using pkg_updating -d to look at new entries in /usr/ports/UPDATING. From what I have read I should be able to just use: # pkg_updating -d 20130301 (for example) And that should give me everything in /usr/ports/UPDATING newer than that date. When I run that command I get: root@monitor:/ # pkg_updating -d 20130301 root@monitor:/ # When I try # pkg_updating -d 20130201 root@monitor:/ # pkg_updating -d 20130201 root@monitor:/ # When I try # pkg_updating -d 20130101 root@monitor:/ # pkg_updating -d 20130101 root@monitor:/ # When I try # pkg_updating -d 20121201 root@monitor:/ # pkg_updating -d 20121201 20121211: AFFECTS: users of devel/pcre AUTHOR: bdrew...@freebsd.org The pcre library has been updated to version 8.32. Please rebuild all ports that depend on it. If you use portmaster: portmaster -w -r pcre If you use portupgrade: portupgrade -fr devel/pcre If you use pkgng with binary packages: pkg install -fR devel/pcre root@monitor:/ # Now that confuses me even more, it only returned one of the 2 advisories on 12/11/2012. I am running: 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 I have "portsnap fetch update" today. Any ideas on how I can correct this behavior? Thank you, Peter ___ 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"
Some GMirror questions.
Hello All, There are a number of gmirror resources available online but there are a few discrepancies. I thought someone here might be able to shed some light on them. Also, this is on FreeBSD 8.0 RELEASE. Does creating the mirror need to be done from a Livefs CD (in Fixit mode) or can it be done directly from the OS? The Handbook makes no reference to things like: # Install FreeBSD on to ad0. # Reboot with the Install CD. # Enter Fixit mode. chroot /dist mount -t devfs devfs /dev gmirror load gmirror label -v -b round-robin gm0 /dev/ad0 mount /dev/mirror/gm0s1a /mnt echo geom_mirror_load="YES" >> /mnt/boot/loader.conf It just indicates jumping right in with gmirror label from the OS (at least it seems to). Also, these next 2 entries in /etc/rc.conf. The Handbook does not make any mention of them. The way the authors state their purpose it would seem as though that should be done in all cases of disk mirroring. Is that true? # tell the system that the swap file will be on a mirror, not a raw drive. echo ’swapoff=”YES”‘ >> /mnt/etc/rc.conf # need to do this to make dumping cores happy since it won’t use a gmirror’ed drive dumpdev=”NO” Lastly, I know at one point the 'load' algorithm had some performance problems and people were saying to only use 'round-robin'. It seems as though some code was committed back in Dec 2009 to fix it's this. Is there a practical rule of thumb to using 'load' vs 'round-robin'? Is this an accurate way to look at it? "Round-robin because if you have two disks in a mirror, they’re both under the same 'load' constraints, and it is best to KISS." Cheers, Peter ___ 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"
Livefs/fixit
Hello, I have a amd64 8.0-RELEASE-P2 FreeBSD box. I was building a spam/av gateway. Something has happened and there seems to be some OS corruption. I am not sure what did it but symlinks all over the system seem to be gone. Links like /home pointing at /usr/home. The data is still there in /usr/home/user_blah but the link pointing there is gone. There could be more issues that I have not discovered yet. I would like to repair the base os from the 8.0 DVD. I believe I should use the livecd/fixit method. Is this the right way to go about doing this? Are there some concise instructions for this? Will this affect the installed ports, ie. things like getting rid of all the configs in /usr/local/etc, rc.conf, passwd, /etc/groups ? I imagine I will need to reinstall all the ports like one would do after a buildworld. Any help would be appreciated. Peter ___ 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: Dependency confusion
Dan Nelson wrote: In the last episode (Jul 02), Peter Clark said: I have a number of ports installed on my 7.2Release box. When I issue pkg_info I see that I have both db41-4.1.25_4 and db46-4.6.21.4 installed. Is there an easy way to see which program is linked to which db? Is this some sort of redundant listing and I really only have db4.6 installed or can you have both side by side? My real concern is about which db backend my cyrus-imap-23 is linked against. All the db* ports install files with the version number embedded in them, so you can have multiple versions installed without conflicts. "ldd /path/to/exe" will tell you which library a given binary is linked with, and you can run "pkg_info -R 'db4*'" to determine which ports depend on which versions of db. Thanks Dan and Bill. Dan, ldd and pkg_info -R did the trick. I really appreciate it. Peter ___ 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"
Dependency confusion
Hello, I have a number of ports installed on my 7.2Release box. When I issue pkg_info I see that I have both db41-4.1.25_4 and db46-4.6.21.4 installed. Is there an easy way to see which program is linked to which db? Is this some sort of redundant listing and I really only have db4.6 installed or can you have both side by side? My real concern is about which db backend my cyrus-imap-23 is linked against. Thank you, Peter ___ 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"
Crusty upgrade (was Make Question)
Lowell Gilbert wrote: Manolis Kiagias writes: I have inherited an old FreeBSD 5.1 machine(5.1-RELEASE-p18). I realize that the short answer to my question is more than likely to upgrade the OS to a current release and I would if I had that option right now, but I do not. I needed to upgrade the perl/openssh/openssl implementation on this box. My first thought was to use the port on the machine that was from that era but make fails. So then I thought to csup the ports tree and try with a new version, that fails as well. The error is as follows: 5.1 (in fact all 5.X) has reached EOL. The latest ports tree won't compile stuff for 5.X. Use the following line in your ports-supfile to get the last ports tree that was supported in 5.X: *default release=cvs tag=RELEASE_5_EOL instead of *default release=cvs tag=. Still, since this is going to be really old you may still have problems (missing distfiles and so on). But is worth trying if you must stay with 5.X for whatever reason. One thing it won't do is get you any of the bug fixes to the ssh port. As a number of people have pointed out this is turning into a bigger headache than it needs to be. The good thing is that allowed me to get the ok to upgrade the system. This box will be taken out of service in the near future but I do need it to remain functional for a couple months. Is there a recommended upgrade path? I know about cvsup and whatnot. What I mean is are there some blatant gotchas when making this big a jump (5.1p18 -> 6.4)? Are there some recommended stops along the way or can it be done in one fell swoop. Is Colin Percival's freebsd-update.sh a viable way to approach this? http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html This is a production box so I want to cover my bases before I jump into this. Peter ___ 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"
Make Question
Hello, I have inherited an old FreeBSD 5.1 machine(5.1-RELEASE-p18). I realize that the short answer to my question is more than likely to upgrade the OS to a current release and I would if I had that option right now, but I do not. I needed to upgrade the perl/openssh/openssl implementation on this box. My first thought was to use the port on the machine that was from that era but make fails. So then I thought to csup the ports tree and try with a new version, that fails as well. The error is as follows: make config "/usr/ports/Mk/bsd.port.mk", line 1780: warning: String comparison operator should be either == or != "/usr/ports/Mk/bsd.port.mk", line 1780: Malformed conditional ((${OSVERSION} >= 77 || ${OSVERSION} < 70)) "/usr/ports/Mk/bsd.port.mk", line 1780: Missing dependency operator "/usr/ports/Mk/bsd.port.mk", line 6276: if-less endif "/usr/ports/Mk/bsd.port.mk", line 6276: Need an operator make: fatal errors encountered -- cannot continue I even tried to run portmanager -s to see what condition all the ports were in and that same failure showed up: portmanager -s portmanager 0.4.1_9: Collecting installed port data 00026 perl-5.10.0_3 /lang/perl5.10 libtool-1.3.4_4 /devel/libtool is no longer in the ports collection, see /usr/ports/MOVED this port must be removed for portmanager to continue is it OK to remove libtool-1.3.4_4 from your system? (yes/no/auto yes to all) [y/n/a] [y] Will timeout after 5 minutes and default to [Y] if no selection is made y removing: libtool-1.3.4_4 /usr/sbin/pkg_delete -f libtool-1.3.4_4 executing: /bin/rm -r /usr/ports/devel/libtool (OK to ignore error) 00025 expat-2.0.1 /textproc/expat2 00024 gettext-0.17_1 /devel/gettext 00023 libtool-1.5.26 /devel/libtool15 00022 libiconv-1.11_1 /converters/libiconv 00021 gmake-3.81_3 /devel/gmake 00020 ezm3-1.2_1 /lang/ezm3 00019 cvsup-without-gui-16.1h_4 /net/cvsup-without-gui 00018 db41-4.1.25_4 /databases/db41 00017 pam_pwdfile-0.95_1 /security/pam_pwdfile 00016 cyrus-sasl-2.1.23 /security/cyrus-sasl2 00015 openssl-0.9.8k_2 /security/openssl 00014 makedepend-1.0.1,1 /devel/makedepend 00013 xproto-7.0.15 /x11/xproto 00012 pkg-config-0.23_1 /devel/pkg-config 00011 rc_subr-1.31_1 /sysutils/rc_subr "/usr/ports/Mk/bsd.port.mk", line 1780: warning: String comparison operator should be either == or != "/usr/ports/Mk/bsd.port.mk", line 1780: Malformed conditional ((${OSVERSION} >= 77 || ${OSVERSION} < 70)) "/usr/ports/Mk/bsd.port.mk", line 1780: Missing dependency operator "/usr/ports/Mk/bsd.port.mk", line 6276: if-less endif "/usr/ports/Mk/bsd.port.mk", line 6276: Need an operator make: fatal errors encountered -- cannot continue MGdbAdd error: attempt to place null data into record halted Assertion failed: (0), function MGdbAdd, file MGdbAdd.c, line 78. Abort (core dumped) The very first thing I did in all this was to upgrade perl to 5.10. The upgrade was successful but the rebuild of the perl dependent ports was not: portupgrade -fr perl [Updating the pkgdb in /var/db/pkg ... ** Stale lock file was found. Removed. - 25 packages found (-1 +1) (...). done] ** Makefile possibly broken: mail/cyrus-imapd2: "/usr/ports/Mk/bsd.port.mk", line 1780: warning: String comparison operator should be either == or != "/usr/ports/Mk/bsd.port.mk", line 1780: Malformed conditional ((${OSVERSION} >= 77 || ${OSVERSION} < 70)) "/usr/ports/Mk/bsd.port.mk", line 1780: Missing dependency operator "/usr/ports/Mk/bsd.port.mk", line 6276: if-less endif "/usr/ports/Mk/bsd.port.mk", line 6276: Need an operator make: fatal errors encountered -- cannot continue /usr/local/sbin/portupgrade:1468:in `get_pkgname': Makefile broken (MakefileBrokenError) from /usr/local/sbin/portupgrade:622:in `main' from /usr/local/sbin/portupgrade:613:in `each' from /usr/local/sbin/portupgrade:613:in `main' from /usr/local/sbin/portupgrade:588:in `catch' from /usr/local/sbin/portupgrade:588:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:1310:in `call' from /usr/local/lib/ruby/1.8/optparse.rb:1310:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1306:in `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1306:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1248:in `order!' from /usr/local/lib/ruby/1.8/o
Re: I've just found a new and interesting spam source - legitimatebounce messages
Paul Schmehl wrote: --On Monday, October 20, 2008 10:11:36 -0700 Jeremy Chadwick <[EMAIL PROTECTED]> wrote: On Mon, Oct 20, 2008 at 11:16:31AM -0500, Paul Schmehl wrote: The best solution *by far* that I have found for spam (using Postfix) is mail/postfix-policyd-weight. It routinely rejects 50 to 70% of incoming mail with no false positives. It took *very* little tweaking to get it to this point, and it rejects the mail before postfix even deals with it. I use spamassassin as well, but policyd-weight does the heavy lifting. We used to use numerous features in postfix to block mail during different phases of the SMTP handshake, requiring strings meet RFC standards, comply with being FQDNs, resolve, blah blah... It worked great... until... One day, one of my users mailed me stating they were in a lot of trouble: they hadn't been receiving any mails from eBay, specifically contact from buyers/sellers (to negotiate payment means, etc.), and outbid notifications. I went digging through logs, and sure enough found the cause: eBay's HELO strings were what pedants would call "absolutely preposterous". They violated 3 or 4 different checks postfix had. At first I tuned postfix to allow certain IP blocks through that check, only to find that it's nearly impossible to determine all of the IP blocks eBay has -- in fact, some of their mail gets siphoned through a third-party mailer, and it looks like that mailer uses IPs all over the place. Meaning: administrative nightmare. There is nothing worse than telling your users "Okay, I've fixed it", only to get mail from them 24 hours later stating "Umm, no you didn't, and this is really starting to piss me off". I went through the same ordeal with other users and their LiveJournal mail notifications being blocked. The point I'm trying to make is that all this overly-aggressive filtering might work great if you're one guy maintaining your own box only used by you -- and I have a feeling a lot of people who post on this list are exactly that. It's a **completely** different game when you've got other people reliant upon your mail filtering decisions. The problem with blocking mail "early on" (meaning before it's queued, e.g. SMTP 5xx or 4xx rejections) is that the end-user has no knowledge of this. They simply do not get the mail. They're left in the dark, wondering "Did send the mail? Are they lying to me? What's going on???". It's a very sensitive thing when you're a hosting provider. In the case of my users, they would much rather get the mail and have it incorrectly flagged as spam, than not get it at all. I personally believe this directly reflects on the state of anti-spam affairs: we've gotten so aggressive that *who KNOWS* what kind of legitimate mail we're blocking. That's why it's critically important that whatever tools you use be highly configurable. In the case of policyd-weight, you can configure it so that it passes *everything* through but marks it in such a way that you can filter it appropriately. In my case, I run a small hobby website with a minimal number of email addresses. When I first installed policyd-weight, I watched it closely and discovered it was blocking legitimate mail from sbcglobal because they didn't have their mail servers' dns properly configured. The result was a score just slightly higher than the threshold for rejection (a tenth of a point or two.) I decided to make that particular check worth less overall, and that solved the problem. I have yet to receive a single complaint about mail not getting through, and, although there's only a handful of accounts on the server, we get mail from our website users constantly. I fully understand where you're coming from, Jeremy. We have the same issues at UTD. But for many smaller sites, policyd-weight would be a godsend Is there an opinion on the end of policyd-weight? Specifically on the alternative listed on the main page, postfwd. Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PF syntax error
Yury Michurin wrote: Hello, I have in my pf.conf: pass in proto tcp from ! to any port www flags S/SA synproxy state (max-src-conn 20, max-src-conn-rate 30/60, overload flush global) and it seems to work just fine... Regards, Yury. On Wed, Oct 15, 2008 at 7:00 PM, Peter Clark <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Hello, I am not sure if I should be here or over at a pf specific list but here is my problem. I am trying my hand at pf on a 7.0-p5 RELEASE box and one rule is giving me problems. pass in quick on $ext_if proto tcp from any to any port 22 flags S/SA \ (max-src-conn 15, max-src-conn-rate 5/3, overload flush global) Actually the "pass in" line does not generate the error. The next line does. /etc/pf.conf:71: syntax error If I remove the line the error goes away (obviously). I have tried using the exact line from the FreeBSD pf.conf man page: (max-src-conn-rate 100/10, overload flush global) (I changed to )and that generates the same error. I tried just using: (max-src-conn-rate 100/10) but that too gives me a syntax error. Any help is appreciated. Peter Clark ___ freebsd-questions@freebsd.org <mailto:freebsd-questions@freebsd.org> mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>" It is because I do not have a "keep state" directive in mine. I took it out because the pf 4.1 default is "flags S/SA keep state". Yours works because you have the synproxy state directive. Thanks, Peter Clark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PF syntax error
Hello, I am not sure if I should be here or over at a pf specific list but here is my problem. I am trying my hand at pf on a 7.0-p5 RELEASE box and one rule is giving me problems. pass in quick on $ext_if proto tcp from any to any port 22 flags S/SA \ (max-src-conn 15, max-src-conn-rate 5/3, overload flush global) Actually the "pass in" line does not generate the error. The next line does. /etc/pf.conf:71: syntax error If I remove the line the error goes away (obviously). I have tried using the exact line from the FreeBSD pf.conf man page: (max-src-conn-rate 100/10, overload flush global) (I changed to )and that generates the same error. I tried just using: (max-src-conn-rate 100/10) but that too gives me a syntax error. Any help is appreciated. Peter Clark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
boot -s hangs
Hello, I have a FreeBSD install that will hang when trying to enter single user mode. If I use "shutdown now" from the console the system will return "System shutdown time has arrived" as expected but it will just hang there indefinitely. If I use option 4 (enter single user mode) from the boot options menu everything seems to boot properly until: "Trying to mount root from ufs:/dev/mfid0s1a" and that is where it hangs. In both cases it never returns a cursor or the expected "enter path" statement. In both cases I can ctrl-alt-delete the box once and it synchs disks and nicely reboots. If I go through standard booting it boots just fine. I am a bit stumped by this. Is this some weird raid card issue? I am not sure how to really trouble shoot this. /var/log/messages and /var/log/console do not even show the hung boot as having happened. # uname -a FreeBSD greed.mtmary.edu 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #0: Wed Jul 23 14:19:22 CDT 2008 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/PETE-GENERIC-AMD64 amd64 # dmesg Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE-p3 #0: Wed Jul 23 14:19:22 CDT 2008 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/PETE-GENERIC-AMD64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz (2336.82-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x10676 Stepping = 6 Features=0xbfebfbff Features2=0xce3bd> AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 4 usable memory = 2133131264 (2034 MB) avail memory = 2058424320 (1963 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard lapic0: Forcing LINT1 to edge trigger acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 cpu0: on acpi0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 720072006000720 device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 720072006000720 device_attach: est1 attach returned 6 p4tcc1: on cpu1 cpu2: on acpi0 est2: on cpu2 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 720072006000720 device_attach: est2 attach returned 6 p4tcc2: on cpu2 cpu3: on acpi0 est3: on cpu3 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 720072006000720 device_attach: est3 attach returned 6 p4tcc3: on cpu3 acpi_button0: on acpi0 pcib0: port 0xca2,0xca3,0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 0.0 on pci2 pci3: on pcib3 pcib4: at device 0.0 on pci3 pci4: on pcib4 mfi0: mem 0xb8b0-0xb8b0,0xb890-0xb891 irq 18 at device 14.0 on pci4 mfi0: Megaraid SAS driver Ver 2.00 mfi0: 1093 (270141940s/0x0020/0) - Shutdown command received from host mfi0: 1094 (4278190080s/0x0020/0) - PCI 0x041000 0x04411 0x048086 0x043501: Firmware initialization started (PCI ID 0411/1000/3501/8086) mfi0: 1095 (4278190080s/0x0020/0) - Type 18: Firmware version 1.12.00-0310 mfi0: 1096 (4278190080s/0x0020/0) - PCI 0x041000 0x04411 0x048086 0x043501: Firmware initialization started (PCI ID 0411/1000/3501/8086) mfi0: 1097 (4278190080s/0x0020/0) - Type 18: Firmware version 1.12.00-0310 mfi0: 1098 (4278190095s/0x0008/0) - Battery temperature is normal mfi0: 1099 (4278190095s/0x0008/0) - Battery Present mfi0: 1100 (4278190095s/0x0020/0) - Type 18: Board Revision mfi0: 1101 (4278190137s/0x0002/1) - PD 03(e0/s3) err 3: PD 03(e0x00/s3) reset (Type 03) mfi0: 1102 (4278190141s/0x0004/0) - PD 11(e1/s255) event: Enclosure (SES) discovered on PD 0b(c None/p1) mfi0: 1103 (4278190141s/0x0002/0) - PD 11(e11/s255) event: Inserted: Encl PD 0b mfi0: 1104 (4278190141s/0x0002/0) - Type 29: Inserted: PD 0b(c None/p1) Info: enclPd=0b, scsiType=d, portMap=09, sasAddr=50015074f5c46000, mfi0: 1105 (4278190141s/0x0002/0) - PD 12(e11/s0) event: Inserted: PD 0c(e0x0b/s0) mfi0: 1106 (4278190141s/0x0002/0) - Type 29: Inserted: PD 0c(e0x0b/s0) Info: enclPd=0b, scsiType=0, portMap=00, sasAddr=0b221d0a75787d4a, mfi0: 1107 (4278190141s/0x0002/0) - PD 13(e11/s1) event: Inserted: PD 0d(e0x0b/s
Gmirror Load vs Round-Robin
Is there a best practice usage for these 2 balance options. In reading the man page, freebsd handbook and various how to's I see no clear usage. Or at least it isnt clear to me. When should you use either one? I am setting up a Raid 1 in FreeBSD 7.0-p2 Release with some SCSI drives. Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Default path.
Hello. I have a FreeBSD 7.0 p2 box. I have upgraded openssl by installing the latest port. When I use openssl version I am still calling the base /usr/bin/openssl. How do I change my default path to use /usr/local/bin/openssl instead? I am the only one (for now) who logs into this box but would it be "better" to make this a system wide change or just a per login? I and all subsequent users use tcsh. I have tried adding /usr/local/bin/openssl to path variable in /etc/login.conf. I logged out and back in but it did not work. Any help would be appreciated. Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dependencies in portmaster
> I am trying to figure out what-all would happen if I were to install > a particular port. IOW I want to do something like > > # portmaster {some set of options} name-of-port > > and have it report something along the lines of > > name-of-port vn #.## requires: > port status > -- > dependency-1 OK > dependency-2 need vn 2.22, current 1.05 > dependency-3 not installed > ... > > dependency-2 vn 2.22 requires: > port status > -- > dependency-4 OK > dependency-5 need vn 5.03, current 4.57 > ... > > dependency-3 vn #.## requires: > port status > -- > dependency-6 not installed > > ... > > I do not want it to actually build or install anything. > > If I am understanding the portmaster manpage correctly this is close > to what -n would do, but I don't even want it to do 'make config' -- > I just want a report of what would have to be added or upgraded in > order to install the port in question. (I imagine portmaster has > to already be collecting this sort of information internally, the > question is how to get it reported externally.) > > BTW I am looking for a solution that does not involve portupgrade, > because I do not have portupgrade installed and before attempting > to install it I would want to see this sort of report regarding it. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > If you truly are just looking at the dependency list and do not wish to have make do anything, wouldn't this do the trick: http://portsmon.freebsd.org/portdependencytree.py I guess you would need to have an up to date ports tree for this to be accurate. Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Computers that us FreeBSD. HELP!!!!!!!
Ryan Jenkins wrote: Hello, I currently have a Computer System that is based off the FreeBSD Operating System and I am trying to find a new supplier of hardware. Right now I am having a hard time finding a Computer Manufacture that can make a system that uses FreeBSD. I currently have found a product from MPC or Micron/Gateway that creates systems with no Operating System, but my programmers are having a hard time with getting the software loaded on the system. Can you please help me find a supplier that builds Desktop or All-in-One computers that will operate FreeBSD. Ryan Jenkins P.O. Box 21138 P: 406 896-9900 F: 406 896-0045 C: 406 208-8193 Email: [EMAIL PROTECTED] I have had very good experiences with FreeBSD Systems (now called freedomtc). http://www.freedomtc.com/ Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Build part of a port.
Hello, I am building a 7.0-RC1 FreeBSD LDAP server. I have installed OpenLDAP from ports and now want to move on to the wed front end. I am using Litespeed as the webserver (built from source), PHP-5 (built from source and customized) and would like to install phpldapadmin. There is a port for it but the port (and some of it's dependencies) will try to install the php5 port and the apache port. Is there a way to install phpldapadmin from ports while telling it (and it's dependencies) I have php5 already installed and not to install apache? Thank you, Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Updating Ports
Robert Huff wrote: Peter Clark writes: Is there a "better" (I realize everything is relative) option when looking at portupgrade vs portmanager? From what I am reading it seems that portmanager will upgrade and reinstall a port and all it's dependencies no matter if the dependency needs it or not and portupgrade will only do the port specified (unless certain flags are present to do all depend). I am using FreeBSD 6.2-p7. Ca you describe the behavior you would like to see? Robert Huff Now that I have reread what I wrote, it seems a bit unclear. I have not used either service before. Seeing as I am looking at using this in production server environment I would not look at frequently making changes as one might in a desktop application. I am looking for an elegant way to update ports when it is required to. Are there more concerns about one updater over the other? Maybe this is a moot point. If you installed a port with some additional config args can you either supply them the upgrade program or can it be reread from the previous install somehow? I really am just trying to find a relatively simple way to make sure that a port gets upgraded and that I do not lose any of it dependencies in the process. Thanks, Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Updating Ports
Hello, Is there a "better" (I realize everything is relative) option when looking at portupgrade vs portmanager? From what I am reading it seems that portmanager will upgrade and reinstall a port and all it's dependencies no matter if the dependency needs it or not and portupgrade will only do the port specified (unless certain flags are present to do all depend). I am using FreeBSD 6.2-p7. Thank you, Peter Clark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD systems
Hello all, Does anyone have any experience dealing with www.freebsdsystems.com ? I am looking to purchase some servers that will work a with a minimum of hardware challenges. Thanks in advance, Pete ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Low-cost dedicated FreeBSD server or non-jail VPS?
Is this up your alley? http://www.johncompanies.com/jc_vps.html > Thanks, Derek. I'm not looking to run this machine from home or to > co-locate an existing box (though I suppose I could do that). > > As Jay mentions, I'm looking for something like: > > http://tektonic.net/unmanaged.html > http://www.leeware.com/vps100.html > http://rosehosting.com/virtserv.html > > (all bad examples because none of them offer FreeBSD) > > -- > We're just a Bunch Of Regular Guys, a collective group that's trying > to understand and assimilate technology. We feel that resistance to > new ideas and technology is unwise and ultimately futile. > > On 2/7/07, Jay Chandler <[EMAIL PROTECTED]> wrote: >> Derek Ragona wrote: >> > FreeBSD runs on most i386 based hardware as long as you have 64 MB ram >> > or more. So you can recycle an old desktop PC to run FreeBSD and then >> > have at it. Or buy a cheap new desktop or refurbished. >> > >> > -Derek >> > >> >> The problem with this approach is that it doesn't get you a static IP >> with proper rDNS and a host of other things... >> >> I'd have interest in the answer to this question as well, as a jailed >> environment isn't quite what I want either. >> >> >> -- >> Jay Chandler >> Network Administrator, Chapman University >> 714.628.7249 / [EMAIL PROTECTED] >> Today's Excuse: Too many interrupts >> >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "[EMAIL PROTECTED]" >> > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Extending a slice
Hello, I have and existing FreeBSD 5.4 box with 2 6GB hard drives in a RAID 1 mirror using gmirror. Due to physical space restrictions I cannot put more drives into this box and yet I need more physical drive space. I have 2 blank 40GB drives to replace my 2 current 6GB drives. I broke the mirror and inserted one 40GB drive into the mirror and removed the remaining 6GB drive. So, now I have a 40GB drive with only 6GB's of space on it and 34GB's of unused space. I have and existing mount point in the 6GB of space called /data. I would like to extend the slice and add the 34GB of unused space to the current /data mount point. Does someone even "extend" an UFS slice? Or do I create a new slice in the unused section and somehow merge the existing slice's /data with the new one? Or am I missing something rudimentary? Any direction would be appreciated. Thank You. Peter Clark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Device Busy
Hello, I am installing a FreeBSD 6.1 i386 machine and using IPF. When I apply some variables to sysctl for IPF I end up with a device busy response. the variables in question are: net.inet.ipf.fr_tcpclosed=1 net.inet.ipf.fr_tcpclosewait=60 net.inet.ipf.fr_tcphalfclosed=300 net.inet.ipf.fr_tcpidletimeout=7200 net.inet.ipf.fr_tcplastack=20 net.inet.ipf.fr_tcptimeout=120 net.inet.ipf.fr_udptimeout=120 The problem occurs both on startup with these in sysctl.conf and if I try do enter it manually: imap# sysctl net.inet.ipf.fr_tcpclosed=1 net.inet.ipf.fr_tcpclosed: 120 sysctl: net.inet.ipf.fr_tcpclosed: Device busy These are the same variables that I have been using successfully on other versions of FreeBSD (5.x and 4.x) so I am inclined to think that I am missing something obvious in this latest version. I am running: FreeBSD 6.1-RELEASE-p2 with: ipf: IP Filter: v4.1.8 (416) Any pointers? Thanks, Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"