Re: xfce4 broke after pkgdb -Ff
KAYVEN RIESE [EMAIL PROTECTED] writes: i did the command pkgdb -Ff and it broke my X (xfce4) the desktop had been able to come up, but the cursor was the X that it has while it is booting.. i was able to start a terminal, but not a mozilla browser. i had been able to use the terminal, but i could not move it around the desktop. pkgdb -Ff had had a pango problem, so i did a portupgrade -f pango. now i can't even get a terminal in my xfce4 I think you missed some of the instructions in /usr/ports/UPDATING. I'm also a bit confused on exactly what you did, because pkgdb doesn't make any changes to the programs you can run. At this point, you need to start by making sure that programs that use pango are updated to use the new one. Something like portupgrade -fr pango. This question would probably have been most appropriate for the freebsd-ports mailing list. Be well. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server
Hi, FreeBSD 6.2 Kernel don't support Broadcom NIC BCM 5708S model. One need to patch kernel Source to make it live. Below i written steps i took. 1, Download patch http://people.freebsd.org/~dwhite/patches/bce-serdes-20070111.tar.gz 2, cd /usr/src/sys/i386/conf 3, cp GENRIC MYKERNEL 4, mkdir /root/kernels 5, cp GENRIC /root/kernels/MYKERNEL 6. ln -s /root/kernels/MYKERNEL 7, cd /usr/src 8, make buildkernel KERNCONF=MYKERNEL 9 make installkernel KERNCONF=MYKERNEL Now Reboot !! Sachin Sharma Sr. Engineer Systems (Linux) Net4India Ltd. D-25 Sector 3 Noida-201301 INDIA Tel: 0120-5323500 Fax: 0120-5323520 URL: http://www.net4.in This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. Scott Long wrote: Sachin Sharma wrote: Hi All, NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server. I need FreeBSD in these server . Please help me. Thanks Support for this card has been added since 6.2 was released. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xfce4 broke after pkgdb -Ff
On Thu, 17 May 2007 08:51:13 -0400 Lowell Gilbert [EMAIL PROTECTED] wrote: pkgdb -Ff had had a pango problem, so i did a portupgrade -f pango. now i can't even get a terminal in my xfce4 I think you missed some of the instructions in /usr/ports/UPDATING. I'm also a bit confused on exactly what you did, because pkgdb doesn't make any changes to the programs you can run. At this point, you need to start by making sure that programs that use pango are updated to use the new one. Something like portupgrade -fr pango. And don't forget the big warning about gettext upgrade to 0.16, which may break things which depend on gettext (which is a lot of things, including Xfce). -- Ricardo Nabinger Sanchez [EMAIL PROTECTED] Powered by FreeBSD Left to themselves, things tend to go from bad to worse. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
fast rate of major FreeBSD releases to STABLE
I have mentioned this before about releasing a new major version of FreeBSD at such short intervals. Now I am wondering what path the FreeBSD community is taking in regards to server and desktop use. Stuff I would love to see in FreeBSD 7.x (CURRENT) before 7.0 release which looks like it isnt going to happen Multi IP Jails - waiting since 4.x, patches done for both 5.x and 6.x but never commited. Dynamic tcp windows - I think is patched but not heard if commited. More hardware support - FreeBSD still has poor hardware support when compared to other OS's, in particular vendors such as realtek nics. A more user friendly installer so datacentres stop been put off FreeBSD. Work on the network code so STABLE stops panicing and lagging on low amounts of ddos that 4.x barely flexed at and even 5.x could cope with. The recent ports freeze has also concerned me, this is the longest ports freeze I have witnessed since I started using FreeBSD years ago and its for a desktop element of the os, does it matter if servers running FreeBSD have to remain on vulnerable versions of ports as a result of this? The viability of upgrading FreeBSD to a new major version at least every 2 years is small, can choose not to upgrade as security patches will exist but ports only get supported on the latest STABLE tree now and I expect 5.x development will be killed off like 4.x was when 7.0 hits release. Why cant 7.0 be released when more long awaited features are added and then not as STABLE tree only as CURRENT (like 5.0 was) and if 7.0 is considered stable then 7.1 can be STABLE branch. I consider 6.2 to be the first release in 6.x branch close to proper stability and that release is under a year old before a new major release is due. Please dont flame me as I am a avid FreeBSD server user not a fan of linux so not been a troll this is a serious post. Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xfce4 broke after pkgdb -Ff
so the -r option will be the significant difference for the portupgrade comamnd, just verifying On Thu, 17 May 2007, Lowell Gilbert wrote: KAYVEN RIESE [EMAIL PROTECTED] writes: i did the command pkgdb -Ff and it broke my X (xfce4) the desktop had been able to come up, but the cursor was the X that it has while it is booting.. i was able to start a terminal, but not a mozilla browser. i had been able to use the terminal, but i could not move it around the desktop. pkgdb -Ff had had a pango problem, so i did a portupgrade -f pango. now i can't even get a terminal in my xfce4 I think you missed some of the instructions in /usr/ports/UPDATING. I'm also a bit confused on exactly what you did, because pkgdb doesn't make any changes to the programs you can run. At this point, you need to start by making sure that programs that use pango are updated to use the new one. Something like portupgrade -fr pango. This question would probably have been most appropriate for the freebsd-ports mailing list. Be well. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server
2007/5/16, Sachin Sharma [EMAIL PROTECTED]: Hi, NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server. I need FreeBSD in these server . Please help me. it works with 6.2-STABLE. download a 6.2 snapshot and install it. works fine here -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fast rate of major FreeBSD releases to STABLE
On Thu, May 17, 2007 at 04:30:50PM +0100, Chris wrote: The recent ports freeze has also concerned me, this is the longest ports freeze I have witnessed since I started using FreeBSD years ago and its for a desktop element of the os, does it matter if servers running FreeBSD have to remain on vulnerable versions of ports as a result of this? I'll leave the src release discussion for others, and just remark that this claim is entirely false: every release cycle has had a longer ports freeze than this one, with the same consequences. We don't take freezes lightly, and the alternative is to import a bunch of incompletely tested changes that will cause untold chaos for our users. I'm sure you wouldn't advocate that. Kris (for portmgr) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fast rate of major FreeBSD releases to STABLE
On Thu, 2007-05-17 at 16:30 +0100, Chris wrote: Stuff I would love to see in FreeBSD 7.x (CURRENT) before 7.0 release which looks like it isnt going to happen [snip] More hardware support - FreeBSD still has poor hardware support when compared to other OS's, in particular vendors such as realtek nics. Do you actually have a card which isn't recognised or doesn't work? I can only see one open PR about an unsupported Realtek NIC, and that is a specific 3 port NIC, which is probably trivial to support. I note also that Realtek do provide FreeBSD drivers for all of their PCI network cards. If you are having problems, open a PR, and include information about the card, a verbose dmesg, and the output of pciconf -l at the bare minimum. A more user friendly installer so datacentres stop been put off FreeBSD. Although work on a new installer is ongoing, nobody ever seems to be clear what the problems are with the current installer that they are trying to fix. I believe PC-BSD uses a different installer, which is the current candidate, although I personally prefer the current one. I'm guessing a new installer never make everybody happy. Work on the network code so STABLE stops panicing and lagging on low amounts of ddos that 4.x barely flexed at and even 5.x could cope with. Again, 6.x is proving very stable for a *lot* of people. What sort of problems are you seeing? URLs to posts on mailing lists would be fine. As there are so many people using 6.x for huge work loads, it may well be something specific to your workload/hardware etc, in which case you may well have to help with debugging. The recent ports freeze has also concerned me, this is the longest ports freeze I have witnessed since I started using FreeBSD years ago and its for a desktop element of the os, does it matter if servers running FreeBSD have to remain on vulnerable versions of ports as a result of this? Kris has already responded to this. The viability of upgrading FreeBSD to a new major version at least every 2 years is small, can choose not to upgrade as security patches will exist but ports only get supported on the latest STABLE tree now and I expect 5.x development will be killed off like 4.x was when 7.0 hits release. [ I speak purely as a FreeBSD user myself, here] Information on EoLs of various releases is available at http://www.freebsd.org/security/ - showing that support for both both 5.5 and 6.1 extend over a year from now. Given the current plan is to release 7.0 some time this year, there's at least 6 months of overlap there. And given 6.3 isn't yet released, and will be supported by the Security Officer for a minimum of 12 months after the release, there will be a fair amount of overlap there too. And I wouldn't be surprised if at least one more 6.x release is designated an extended support release. Why cant 7.0 be released when more long awaited features are added and then not as STABLE tree only as CURRENT (like 5.0 was) and if 7.0 is considered stable then 7.1 can be STABLE branch. http://www.freebsd.org/doc/en_US.ISO8859-1/articles/version-guide/past-schedules.html explains this far better than I ever could. I consider 6.2 to be the first release in 6.x branch close to proper stability and that release is under a year old before a new major release is due. Again, without knowing what issues you saw, I'm not sure anyone can answer that. The only real issues I am aware of with 6.0/6.1 that weren't fixed with errata patches were either quota, IPv6 or CARP related. Please dont flame me as I am a avid FreeBSD server user not a fan of linux so not been a troll this is a serious post. Please don't take my response as a flame :) Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xfce4 broke after pkgdb -Ff
Please don't top-post. KAYVEN RIESE [EMAIL PROTECTED] writes: so the -r option will be the significant difference for the portupgrade comamnd, just verifying Yes. Otherwise, you may end up with some of the ports that depend on pango being unable to use the new version. Make sure you look through the UPDATING file to see if there are any other issues you need to take special action for at the same time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server
On Thu, May 17, 2007 at 07:08:39PM +0530, Sachin Sharma wrote: Hi, FreeBSD 6.2 Kernel don't support Broadcom NIC BCM 5708S model. One need to patch kernel Source to make it live. Below i written steps i took. 1, Download patch http://people.freebsd.org/~dwhite/patches/bce-serdes-20070111.tar.gz 2, cd /usr/src/sys/i386/conf 3, cp GENRIC MYKERNEL 4, mkdir /root/kernels 5, cp GENRIC /root/kernels/MYKERNEL 6. ln -s /root/kernels/MYKERNEL 7, cd /usr/src 8, make buildkernel KERNCONF=MYKERNEL 9 make installkernel KERNCONF=MYKERNEL Now Reboot !! The code/patch in question was committed to the RELENG_6 tree a while ago. All you need to do is cvsup/csup your sourcecode to the most recent snapshot/version of 6.2 (not what's on the CD, and not 6.2-RELEASE), and that should suffice. For instructions on how to do this, see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Note that 6, however, comes with a tool called csup (the C version of cvsup), which performs identically and does not require you to install ports/net/cvsup. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fast rate of major FreeBSD releases to STABLE
Date: Thu, 17 May 2007 16:30:50 +0100 From: Chris [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] I have mentioned this before about releasing a new major version of FreeBSD at such short intervals. Now I am wondering what path the FreeBSD community is taking in regards to server and desktop use. Stuff I would love to see in FreeBSD 7.x (CURRENT) before 7.0 release which looks like it isnt going to happen Multi IP Jails - waiting since 4.x, patches done for both 5.x and 6.x but never commited. No idea. Dynamic tcp windows - I think is patched but not heard if commited. It should be in 7.0. 7.0 will have really major network improvements. I even had one vendor tell us that if we wanted to improve the performance of their 10GE card, we should switch from Linux to FreeBSD-current. More hardware support - FreeBSD still has poor hardware support when compared to other OS's, in particular vendors such as realtek nics. An on-going issue. Linux simply has more people working on device support, so it often (but no always) gets support first. Current does have several new network devices including more wireless NICs. A more user friendly installer so datacentres stop been put off FreeBSD. While sysinstall is ugly, I find it very easy to use and use it for non-installation stuff (fdisk and bsdlabel) for its friendlier user interface. I have never been happy with GUI installers although a re-write if sysinstall would probably be a good thing. Work on the network code so STABLE stops panicing and lagging on low amounts of ddos that 4.x barely flexed at and even 5.x could cope with. This is probably better, but I have not done much testing. The recent ports freeze has also concerned me, this is the longest ports freeze I have witnessed since I started using FreeBSD years ago and its for a desktop element of the os, does it matter if servers running FreeBSD have to remain on vulnerable versions of ports as a result of this? Now this is totally bogus. The freeze before the 6.0 release was VERY long and several have been longer than this one has been so far. The ports collection is one of the greatest things about FreeBSD and having lots of ports break when a major one (such as Xorg) is updated is very difficult and takes a lot of time to build test everything. Just creating an upgrade procedure that works for everyone running FreeBSD of any supported version is a major effort. The viability of upgrading FreeBSD to a new major version at least every 2 years is small, can choose not to upgrade as security patches will exist but ports only get supported on the latest STABLE tree now and I expect 5.x development will be killed off like 4.x was when 7.0 hits release. ??? I should leave this to others, but in the past FreeBSD has received heavy criticism for taking too long between releases. I guess you just can't win. Yes, V5 development is pretty well at an end (though V5 was not one of FreeBSD's better releases and I never used it on production systems), but V6 support will continue for quite a while. Why cant 7.0 be released when more long awaited features are added and then not as STABLE tree only as CURRENT (like 5.0 was) and if 7.0 is considered stable then 7.1 can be STABLE branch. I consider 6.2 to be the first release in 6.x branch close to proper stability and that release is under a year old before a new major release is due. The release of V5.0 was as a development release because V5.0 had so many changes from V4 that all developers had to know that there were going to be problems, but the RE team also realized that, if they did not draw a line in the sand, it would only get worse. I am VERY sure that RE and the developers NEVER want to go through that again. As of today, CURRENT is in pretty excellent shape, but it still does have a few issues and more will certainly pop up when it is released. No one who has any experience is going to drop 7.0 on any critical system. I run it on one desktop and my laptop. I am NOT going to install 7.0 on my DNS servers or any other critical system. Depending on how things go with 7.0, I will probably install 7.1 on most systems. I may be braver than most, though (or more foolish). Please dont flame me as I am a avid FreeBSD server user not a fan of linux so not been a troll this is a serious post. I'm not flaming (yet), because you ask some good questions and are probably suffering from fading memory of prior releases. (I know that I try to forget a couple of them.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpklYjpz3zjx.pgp Description: PGP signature
Re: fast rate of major FreeBSD releases to STABLE
On Thu, May 17, 2007 at 05:51:07PM +0100, Gavin Atkinson wrote: On Thu, 2007-05-17 at 16:30 +0100, Chris wrote: A more user friendly installer so datacentres stop been put off FreeBSD. Although work on a new installer is ongoing, nobody ever seems to be clear what the problems are with the current installer that they are trying to fix. I believe PC-BSD uses a different installer, which is the current candidate, although I personally prefer the current one. I'm guessing a new installer never make everybody happy. As someone who has had to show many people how to use the FreeBSD installer, I can confirm what Chris is referring to. Here's some of the generic end-user complaints I've heard (and some of which I have); 1) Difficult to tell what's in-focus (selectiom menu vs. OK/Cancel) on the screen. This could be solved by using a different colour for the selection area (instead of blue, use something like cyan/teal), I think. 2) Many buttons are labelled Cancel rather than Go Back. Some cancel the entire operation (go back to the main menu), others go back a step. Users find this inconsistency to be confusing. 3) Conflicting definitions of keypresses in the menu vs. the OK/Cancel box at the bottom. For example, under Keymap, one of the menu items is labelled (C)entral European ISO, while C is also used for (C)ancel, depending upon which focus/menu context you're in. This confuses people. 4) Some Cancel/Abort items are labelled (C)ancel, others are (X)Exit. Make up your mind; people want a consistent key! 5) I forget which stage of the installation this happens in, but when choosing Cancel/Abort, the dialog you get asks you if you want to continue with the operation or abort. If you choose abort, it reboots the machine. This seems unnecessary. 6) I'll point out that you can hit X to jump to the Exit (go back) menu item, but *only* if that menu item is visible on the screen. I've heard numerous complaints about that as well (and personally I agree with it). 7) The Options menu area requires you to scroll all the way to the bottom of the left column of options, and further down past it to reach the right column. Users hit the Right Arrow key to go to the right column, which does nothing. 8) Video console is 80x25. I am quite happy with this myself, but some others want something larger. This gets complex since to get something larger I believe we require use of VESA. I thought I'd mention it anyways. 9) Lack of mouse support in the menus. I haven't confirmed this, but it seems to me that based on the installer's look, people expect the mouse to work. I personally don't like the mouse (I find gpm to be better/more responsive/capable than moused.), but their point is still valid. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fast rate of major FreeBSD releases to STABLE
On Thu, May 17, 2007 at 10:24:15AM -0700, Kevin Oberman wrote: The recent ports freeze has also concerned me, this is the longest ports freeze I have witnessed since I started using FreeBSD years ago and its for a desktop element of the os, does it matter if servers running FreeBSD have to remain on vulnerable versions of ports as a result of this? Now this is totally bogus. The freeze before the 6.0 release was VERY long and several have been longer than this one has been so far. I think the complaint may be more a result of this being a deeper freeze than normal. When ports is frozen before a release, it is often still possible to get things like security fixes and minor updates approved and committed. The only time it's completely frozen is during branching, which typically doesn't take very long. I don't know if portmgr@ has approved any commits during the xorg freeze or not. Even if so I suspect the critical bar may be higher this time due to the need to manually merge changes into the git repository. That said, it's a major undertaking and there are valid arguments on both sides. Hopefully it will be done soon (keep in mind this is still a volunteer project!) ??? I should leave this to others, but in the past FreeBSD has received heavy criticism for taking too long between releases. I guess you just can't win. Yes, V5 development is pretty well at an end (though V5 was not one of FreeBSD's better releases and I never used it on production systems), but V6 support will continue for quite a while. One thing to keep in mind is that with shorter releases, it's a lot easier to move from one release to the next. It was a Very Big Deal to upgrade from 4.x to 5.x and required lots of pain and planning, mostly because so much had changed. Going from 5.x to 6.x was much easier -- for those upgrading from source it wasn't much different than point releases on the 5.x line. I recently upgraded a 6.x server to 7-CURRENT to test out zfs and again it was just like cvsupping and building stable. There's some library version issues, but those should be resolved before the 7.0 release happens. It's still nowhere near the massive undertaking from 4 to 5. I am VERY sure that RE and the developers NEVER want to go through that again. Nor the users ;) No one who has any experience is going to drop 7.0 on any critical system. I run it on one desktop and my laptop. I am NOT going to install 7.0 on my DNS servers or any other critical system. I'm running -current on my home file server, which is fairly critical to me, but then again I'm obsessive about backups, which helps :) I don't think I'd be brave enough to try it on business-critical systems though, which I suspect is your meaning. Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xfce4 broke after pkgdb -Ff
On Thu, 17 May 2007, Lowell Gilbert wrote: Please don't top-post. KAYVEN RIESE [EMAIL PROTECTED] writes: so the -r option will be the significant difference for the portupgrade comamnd, just verifying Yes. Otherwise, you may end up with some of the ports that depend on pango being unable to use the new version. Make sure you look through the UPDATING file to see if there are any other issues you need to take special action for at the same time. this guy seems to disagree jnielsendotnet:Try what I asked in my first reply (deleting and reinstalling pango manually), and see if you can get any error messages from xfce. If portupgrade -f is failing portupgrade -fr isn't likely to succeed either. Ricardo's comment (in your parallel thread on the freebsd-stable mailing list) about the gettext upgrade is probably relevant as well. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
make mplayer failed
here is my error message onfigure: error: Package requirements (glib-2.0 = 2.12.0atk = 1.9.0 pa ngo = 1.12.0cairo = 1.2.0) were not met: No package 'atk' found Requested 'cairo = 1.2.0' but version of cairo is 1.0.2 Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables BASE_DEPENDENCIES_CFLAGS and BASE_DEPENDENCIES_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. === Script configure failed unexpectedly. Please run the gnomelogalyzer, available from http://www.freebsd.org/gnome/gnomelogalyzer.sh;, which will diagnose the problem and suggest a solution. If - and only if - the gnomelogalyzer cannot solve the problem, report the build failure to the FreeBSD GNOME team at [EMAIL PROTECTED], and attach (a) /usr/ports/x11-toolkits/gtk20/work/gtk+-2.10.11/config.log, (b) the output of the failed make command, and (c) the gnomelogalyzer output. Also, it might be a good idea to provide an overview of all packages installed on your system (i.e. an `ls /var/db/pkg`). Put your attachment up on any website, copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) with the attachment. Try to avoid sending any attachments to the mailing list ([EMAIL PROTECTED]), because attachments sent to FreeBSD mailing lists are usually discarded by the mailing list software. *** Error code 1 Stop in /usr/ports/x11-toolkits/gtk20. *** Error code 1 Stop in /usr/ports/multimedia/mplayer. bsd@/root# find / -name gnomelogalyzer.sh ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
last email
what i sent may or may not make sense. i run pine for email client and am having some buffer lag right now. my keystrokes are not being immeditaelyt echoed and i didn't really mean to send it. if it DOES make sense, feeel free to comment. sorry about that. also typos are a symptom of the keystroke buffer sitch. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xfce4 broke after pkgdb -Ff
On Thu, 17 May 2007, John Nielsen wrote: On Thursday 17 May 2007 02:37:15 pm KAYVEN RIESE wrote: On Thu, 17 May 2007, Lowell Gilbert wrote: Please don't top-post. KAYVEN RIESE [EMAIL PROTECTED] writes: so the -r option will be the significant difference for the portupgrade comamnd, just verifying Yes. Otherwise, you may end up with some of the ports that depend on pango being unable to use the new version. Make sure you look through the UPDATING file to see if there are any other issues you need to take special action for at the same time. this guy seems to disagree jnielsendotnet:Try what I asked in my first reply (deleting and reinstalling pango manually), and see if you can get any error messages from xfce. If portupgrade -f is failing portupgrade -fr isn't likely to succeed either. Portupgrade with the -r option is very useful, and you will probably want to use it. My point was that _before_ you try that you should figure out why portupgrade is failing to upgrade pango, and/or upgrade it manually. Otherwise it will just keep failing. JN i guess i can see how u guys r on the same page then. he says -r won't help, u say it's nice. makes sense ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xfce4 broke after pkgdb -Ff
On Thursday 17 May 2007 02:37:15 pm KAYVEN RIESE wrote: On Thu, 17 May 2007, Lowell Gilbert wrote: Please don't top-post. KAYVEN RIESE [EMAIL PROTECTED] writes: so the -r option will be the significant difference for the portupgrade comamnd, just verifying Yes. Otherwise, you may end up with some of the ports that depend on pango being unable to use the new version. Make sure you look through the UPDATING file to see if there are any other issues you need to take special action for at the same time. this guy seems to disagree jnielsendotnet:Try what I asked in my first reply (deleting and reinstalling pango manually), and see if you can get any error messages from xfce. If portupgrade -f is failing portupgrade -fr isn't likely to succeed either. Portupgrade with the -r option is very useful, and you will probably want to use it. My point was that _before_ you try that you should figure out why portupgrade is failing to upgrade pango, and/or upgrade it manually. Otherwise it will just keep failing. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
mysql frequently crash on 6.2
Greetings everyone... I am observing what appears to be a similar problem as well... I have a dedicated server with *very* light traffic. It looks like every day or so my server load slowly climbs from 0.20 to 14.00 and then stays there indefinitely locking down the system [until I do an apachectl restart] after which the server load drops back down. I'm not getting any weird Fatal Errors from PHP or any Warnings [though a lot of PHP Notices.]. The apache httpd_error.log shows the following error, usually, when the slow climb to 14.00 server load begins: httpd in free(): error: recursive call httpd in free(): error: recursive call [Usually it only shows about three or four of these repeated errors.] I am using FreeBSD 6.2 and MySQL 4.1. I am trying to use the libthr threading mechanism through the libmap.conf setting, as to earlier in this thread post, as a possible fix. [Though, I don't know if I have in fact been successful in switching to libthr or not... because I'm not sure if I need to recompile / reboot? I don't know if mysql was install from a port or not.] In any event, my libmap.conf settings are now [located in /etc/libmap.conf]: [mysqld] libc_r.so libthr.so libc_r.so.6 libthr.so.2 libthr.so.2 libthr.so.2 libpthread.so libthr.so libpthread.so.2 libthr.so.2 and I also added ... WITH_LIBMAP= yes to my make.conf file. Is there something else I need to do [e.g., recompile? / reboot?] in order to activate libthr? The problem remains even with these adjustments. Blessings, Albert Wong www.ithou.org PS. The mysql_logfile is completely empty... I don't know if that is unusual or not. PPS. Here's the my.cnf settings for this machine: [mysqld] safe-show-database skip-innodb max_connections = 500 key_buffer = 32M myisam_sort_buffer_size = 64M join_buffer_size = 1M read_buffer_size = 1M sort_buffer_size = 2M table_cache = 1800 thread_cache_size = 384 wait_timeout = 90 connect_timeout = 10 tmp_table_size = 64M max_heap_table_size = 64M max_allowed_packet = 16M max_connect_errors = 10 read_rnd_buffer_size = 524288 bulk_insert_buffer_size = 8M query_cache_limit = 3M query_cache_size = 80M query_cache_type = 1 query_prealloc_size = 163840 query_alloc_block_size = 32768 skip-name-resolve [mysqld_safe] open_files_limit = 8192 [mysqldump] quick max_allowed_packet = 16M [myisamchk] key_buffer = 16M sort_buffer = 16M read_buffer = 16M write_buffer = 16M [mysqlhotcopy] interactive-timeout log = /var/log/mysql/mysql_logfile ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xfce4 broke after pkgdb -Ff
KAYVEN RIESE [EMAIL PROTECTED] writes: On Thu, 17 May 2007, Lowell Gilbert wrote: Please don't top-post. KAYVEN RIESE [EMAIL PROTECTED] writes: so the -r option will be the significant difference for the portupgrade comamnd, just verifying Yes. Otherwise, you may end up with some of the ports that depend on pango being unable to use the new version. Make sure you look through the UPDATING file to see if there are any other issues you need to take special action for at the same time. this guy seems to disagree jnielsendotnet:Try what I asked in my first reply (deleting and reinstalling pango manually), and see if you can get any error messages from xfce. If portupgrade -f is failing portupgrade -fr isn't likely to succeed either. That's true. I seem to have missed wherever it was that you said that the portupgrade of pango had failed. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fast rate of major FreeBSD releases to STABLE
On Thu, May 17, 2007 at 01:35:10PM -0500, Craig Boston wrote: Now this is totally bogus. The freeze before the 6.0 release was VERY long and several have been longer than this one has been so far. I think the complaint may be more a result of this being a deeper freeze than normal. That's correct. When ports is frozen before a release, it is often still possible to get things like security fixes and minor updates approved and committed. The only time it's completely frozen is during branching, which typically doesn't take very long. Most freezes are really more of a slush. This is the first time we've done an absolute, hard, freeze of this length in a long time. But importnng or upgrading several hundred ports, moving those and others from X11BASE to LOCALBASE, and all the associated testing and retesting and re-retesting just simply requires that we have everything locked down tight right now. The alternative would have been to commit what we had and _then_ found out all the bugs in the upgrade process (note: you won't be able to just blindly use portupgrade -af; you will need to read the UPDATING file for the proper procedure. This is the unusual case of being such a sweeping change that the port management tools are not completely up to the task.) I don't know if portmgr@ has approved any commits during the xorg freeze or not. Nope. There are simply too many ports that have interdependencies among the xorg ports. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
mysql frequently crash on 6.2
Greetings everyone... I am observing what appears to be a similar problem as well... [referring to the posts from earlier this month with the same subject]... I have a dedicated server with *very* light traffic. It looks like every day or so my server load slowly climbs from 0.20 to 14.00 and then stays there indefinitely locking down the system [until I do an apachectl restart] after which the server load drops back down. I'm not getting any weird Fatal Errors from PHP or any Warnings [though a lot of PHP Notices.]. The apache httpd_error.log shows the following error, usually, when the slow climb to 14.00 server load begins: httpd in free(): error: recursive call httpd in free(): error: recursive call [Usually it only shows about three or four of these repeated errors.] I am using FreeBSD 6.2 and MySQL 4.1. I am trying to use the libthr threading mechanism through the libmap.conf setting, as to earlier in this thread post, as a possible fix. [Though, I don't know if I have in fact been successful in switching to libthr or not... because I'm not sure if I need to recompile / reboot? I don't know if mysql was install from a port or not.] In any event, my libmap.conf settings are now [located in /etc/libmap.conf]: [mysqld] libc_r.so libthr.so libc_r.so.6 libthr.so.2 libthr.so.2 libthr.so.2 libpthread.so libthr.so libpthread.so.2 libthr.so.2 and I also added ... WITH_LIBMAP= yes to my make.conf file. Is there something else I need to do [e.g., recompile? / reboot?] in order to activate libthr? The problem remains even with these adjustments. Blessings, Albert Wong www.ithou.org PS. The mysql_logfile is completely empty... I don't know if that is unusual or not. PPS. Here's the my.cnf settings for this machine: [mysqld] safe-show-database skip-innodb max_connections = 500 key_buffer = 32M myisam_sort_buffer_size = 64M join_buffer_size = 1M read_buffer_size = 1M sort_buffer_size = 2M table_cache = 1800 thread_cache_size = 384 wait_timeout = 90 connect_timeout = 10 tmp_table_size = 64M max_heap_table_size = 64M max_allowed_packet = 16M max_connect_errors = 10 read_rnd_buffer_size = 524288 bulk_insert_buffer_size = 8M query_cache_limit = 3M query_cache_size = 80M query_cache_type = 1 query_prealloc_size = 163840 query_alloc_block_size = 32768 skip-name-resolve [mysqld_safe] open_files_limit = 8192 [mysqldump] quick max_allowed_packet = 16M [myisamchk] key_buffer = 16M sort_buffer = 16M read_buffer = 16M write_buffer = 16M [mysqlhotcopy] interactive-timeout log = /var/log/mysql/mysql_logfile ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: mysql frequently crash on 6.2
Yes... this is possible Currently, I am on MySQL 4.1.20 ... but I believe that MySQL is backwards compatible... so I can definitely try this. Do you know if this bug is squashed with MySQL 5.0.37 ? Thanks, Albert -Original Message- From: Abdullah Ibn Hamad Al-Marri [mailto:[EMAIL PROTECTED] Sent: Thursday, May 17, 2007 1:17 PM To: Albert Wong Cc: freebsd-stable@freebsd.org Subject: Re: mysql frequently crash on 6.2 On 5/17/07, Albert Wong [EMAIL PROTECTED] wrote: snip Can you go for MySQL 5.0.37? -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysql frequently crash on 6.2
On 5/17/07, Albert Wong [EMAIL PROTECTED] wrote: snip Can you go for MySQL 5.0.37? -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fast rate of major FreeBSD releases to STABLE
Jeremy Chadwick wrote: As someone who has had to show many people how to use the FreeBSD installer, I can confirm what Chris is referring to. Here's some of the generic end-user complaints I've heard (and some of which I have); [...] As someone who only very rarely plays with the installer, I sometimes get bitten by the Space/Enter thing. -- Tuomo ... Great, so now I get to take shit from Finns on both sides of the Atlantic for a guy I didn't elect and whose policies I don't support. -- http://www.axis-of-aevil.net/archives/2004/11/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysql frequently crash on 6.2
Hello In general This is what I use for my libmap.conf , it works fine for me any you may want to give it a try. [mysqld] libpthread.so libthr.so libpthread.so.2 libthr.so.2 Note nothing in MySQL 4.1 compiled on FreeBSD 6.2 should use libc_r.so . The other thing in your libmap that looks odd is the line libthr.so.2 libthr.so.2 not sure what that will do. In any event, my libmap.conf settings are now [located in /etc/libmap.conf]: [mysqld] libc_r.so libthr.so libc_r.so.6 libthr.so.2 libthr.so.2 libthr.so.2 libpthread.so libthr.so libpthread.so.2 libthr.so.2 One thing I normally turn off in MySQL is the query_cache . If your DB is constantly receiving updates the query_cache is flushed to with each update. This creates alot of useless overhead, in fact if set it very high like to 1G or so you will see some nasty side effects of how MySQL tries to flush the cache. As for you log you may want to move that in to the [mysqld] section of the config. In this setup I beleive that mysqlhotcopy would be the only mysql* command using that directive. table_cache should not be greater the amount of tables your databases have . read_rnd_buffer_size = 524288 looks way to high your key_buffer_size is only 32M Maybe you want to lower this to 64M of even leave it undefined to see what the default does for you. PPS. Here's the my.cnf settings for this machine: [mysqld] safe-show-database skip-innodb max_connections = 500 key_buffer = 32M myisam_sort_buffer_size = 64M join_buffer_size = 1M read_buffer_size = 1M sort_buffer_size = 2M table_cache = 1800 thread_cache_size = 384 wait_timeout = 90 connect_timeout = 10 tmp_table_size = 64M max_heap_table_size = 64M max_allowed_packet = 16M max_connect_errors = 10 read_rnd_buffer_size = 524288 bulk_insert_buffer_size = 8M query_cache_limit = 3M query_cache_size = 80M query_cache_type = 1 query_prealloc_size = 163840 query_alloc_block_size = 32768 skip-name-resolve [mysqld_safe] open_files_limit = 8192 [mysqldump] quick max_allowed_packet = 16M [myisamchk] key_buffer = 16M sort_buffer = 16M read_buffer = 16M write_buffer = 16M [mysqlhotcopy] interactive-timeout log = /var/log/mysql/mysql_logfile -- Mark Saad ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
udp fragmentation with pf/ipf
Hello, While making some tests with fragmented udp DNS responses (with EDNS0), we discovered a possible problem with ipf and pf in FreeBSD 6.2 and 7.0 (200705 snapshot). Our test is a DNS query to an DNSSEC enabled server which replies with a ~4KB udp response. We do this with the following dig command: dig @192.36.144.107 se dnskey +dnssec +bufsize=4500 +retry=0 ipf and pf in FreeBSD 6.2 or 7.0 block the fragments and the DNS queries timeout. Disabling the firewall, complete replies are received with no problem. We've made the same tests with FreeBSD 4.11 with ipf and OpenBSD 4.1 with pf with no problems. You can see a summary of the tests below. OS + fwdig result fbsd4.11 + ipf OK obsd4.1 + pfOK fbsd6.2 OK fbsd6.2 + ipf timeout fbsd6.2 + pf timeout fbsd7.0 OK fbsd7.0 + ipf timeout fbsd7.0 + pf timeout Complete test results (including tcpdump output and firewall rule sets) are attached. Can somebody tell us if he hit a bug or if there is something we are missing? Thanks, Hugo ## FreeBSD 4.11 + ipfilter - dig OK fbsd4.11# uname -v FreeBSD 4.11-RELEASE #0: Fri Jan 21 17:21:22 GMT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC fbsd4.11# ipf -V ipf: IP Filter: v3.4.35 (336) Kernel: IP Filter: v3.4.35 Running: yes Log Flags: 0 = none set Default: pass all, Logging: available Active list: 0 fbsd4.11# ipfstat -ion @1 pass out log quick on bge0 proto udp from xxx.xxx.xxx.113/32 to any port = 53 keep state keep frags @2 pass out quick on bge0 proto tcp/udp from xxx.xxx.xxx.113/32 to any keep state @3 pass out quick on bge0 proto icmp from xxx.xxx.xxx.113/32 to any keep state @4 pass out quick on lo0 from any to any @5 block out log from any to any @1 pass in quick on bge0 proto tcp from xxx.xxx.xxx.81/32 to xxx.xxx.xxx.113/32 port = 22 keep state @2 pass in quick on lo0 from any to any @3 block in log from any to any fbsd4.11# tcpdump -i bge0 -np host 192.36.144.107 tcpdump: listening on bge0 09:46:16.546878 xxx.xxx.xxx.113.2897 192.36.144.107.53: 37118+ [1au] Type48? se. (31) 09:46:16.789319 192.36.144.107.53 xxx.xxx.xxx.113.2897: 37118*- 8/10/24 Type48[|domain] (frag 8851:[EMAIL PROTECTED]) 09:46:16.789325 192.36.144.107 xxx.xxx.xxx.113: udp (frag 8851:[EMAIL PROTECTED]) 09:46:16.789331 192.36.144.107 xxx.xxx.xxx.113: udp (frag 8851:[EMAIL PROTECTED]) fbsd4.11# grep 192.36.144.107 /var/log/messages May 17 09:46:16 fbsd4.11 ipmon[54]: 09:46:16.546867 bge0 @0:1 p xxx.xxx.xxx.113,2897 - 192.36.144.107,53 PR udp len 20 59 K-S K-F OUT May 17 09:46:16 fbsd4.11 ipmon[54]: 09:46:16.789339 bge0 @0:1 p 192.36.144.107,53 - xxx.xxx.xxx.113,2897 PR udp len 20 1500 K-S K-F IN May 17 09:46:16 fbsd4.11 ipmon[54]: 09:46:16.789347 bge0 @-1:-1 p 192.36.144.107 - xxx.xxx.xxx.113 PR udp len 20 (1500) (frag 8851:[EMAIL PROTECTED]) K-S K-F IN May 17 09:46:16 fbsd4.11 ipmon[54]: 09:46:16.789353 bge0 @-1:-1 p 192.36.144.107 - xxx.xxx.xxx.113 PR udp len 20 (1154) (frag 8851:[EMAIL PROTECTED]) K-S K-F IN fbsd4.11# /usr/local/bin/dig @192.36.144.107 se dnskey +dnssec +bufsize=4500 +retry=0 ; DiG 9.4.1 @192.36.144.107 se dnskey +dnssec +bufsize=4500 +retry=0 ; (1 server found) ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 37118 ;; flags: qr aa rd; QUERY: 1, ANSWER: 8, AUTHORITY: 10, ADDITIONAL: 24 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags: do; udp: 4096 ;; QUESTION SECTION: [...] ;; Query time: 245 msec ;; SERVER: 192.36.144.107#53(192.36.144.107) ;; WHEN: Thu May 17 09:46:16 2007 ;; MSG SIZE rcvd: 4086 ## FreeBSD 6.2 + no firewall - dig OK fbsd6.2# uname -v FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP fbsd6.2# dig @192.36.144.107 se dnskey +dnssec +bufsize=4500 +retry=0 ; DiG 9.3.3 @192.36.144.107 se dnskey +dnssec +bufsize=4500 +retry=0 ; (1 server found) ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 7745 ;; flags: qr aa rd; QUERY: 1, ANSWER: 8, AUTHORITY: 10, ADDITIONAL: 24 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags: do; udp: 4096 ;; QUESTION SECTION: ;se.IN DNSKEY [...] ;; Query time: 243 msec ;; SERVER: 192.36.144.107#53(192.36.144.107) ;; WHEN: Thu May 17 11:31:39 2007 ;; MSG SIZE rcvd: 4086 ## FreeBSD 6.2 + pf - dig timeout fbsd6.2# uname -v FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP fbsd6.2# pfctl -sr No ALTQ support in kernel ALTQ related functions disabled scrub in all fragment reassemble block drop in log all pass in on bge0 inet proto tcp from xxx.xxx.xxx.81 to xxx.xxx.xxx.87 port = ssh keep state pass out on bge0 proto tcp all keep state pass out on bge0 proto udp all keep state pass out on bge0 proto icmp all keep state fbsd6.2# tcpdump -i bge0 -np host 192.36.144.107
Re: udp fragmentation with pf/ipf
This should be rejected as keep frags is meaningless here. pass out log quick on bge0 proto udp from xxx.xxx.xxx.113/32 to any port = 53 keep state keep frags You need pass in quick from any to any with frag keep frag -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: udp fragmentation with pf/ipf
This should be rejected as keep frags is meaningless here. pass out log quick on bge0 proto udp from xxx.xxx.xxx.113/32 to any port = 53 keep state keep frags You need pass in quick from any to any with frag keep frag The reason is that ip fragments not have next level headers. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysql frequently crash on 6.2
Hello Albert, Hello @list, first, i be a native german speaker, so please excuse my ugly english. Greetings everyone... I am observing what appears to be a similar problem as well... I have a dedicated server with *very* light traffic. It looks like every day or so my server load slowly climbs from 0.20 to 14.00 and then stays there indefinitely locking down the system [until I do an apachectl restart] after which the server load drops back down. I'm not getting any weird Fatal Errors from PHP or any Warnings [though a lot of PHP Notices.]. The apache httpd_error.log shows the following error, usually, when the slow climb to 14.00 server load begins: httpd in free(): error: recursive call httpd in free(): error: recursive call [Usually it only shows about three or four of these repeated errors.] --8---snip---8--- I have experiences with an similar Problem with apache in combination with php4 and it's modules. If you have the wrong modules / order of modules in the extensions.ini so that apache disappears with segfault ( my be signal 6 or 11 ) if you try an reload. hope this helps a little bit. greetings michael -- === michael-schuh.net === Michael Schuh Preußenstr. 13 66111 Saarbrücken phone: 0681/8319664 mobil: 0177/9738644 @: [EMAIL PROTECTED] === Ust-ID: DE251072318 === ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: mysql frequently crash on 6.2
Mark: Thanks for the tips about the placement of the log into [mysqld] -- maybe it will start to show some error messages if I put it up into the mysqld section. :-) I will also take a look at table_cache and query_cache and read_rnd_buffer_size. [I've got some reading / figuring out to do!] Michael: And thanks also for the suggestion at looking into extensions.ini for the order of the modules. I'm not quite sure what do to there, but I'll definitely research this. Blessings, Albert One thing I normally turn off in MySQL is the query_cache . If your DB is constantly receiving updates the query_cache is flushed to with each update. This creates alot of useless overhead, in fact if set it very high like to 1G or so you will see some nasty side effects of how MySQL tries to flush the cache. As for you log you may want to move that in to the [mysqld] section of the config. In this setup I beleive that mysqlhotcopy would be the only mysql* command using that directive. table_cache should not be greater the amount of tables your databases have . read_rnd_buffer_size = 524288 looks way to high your key_buffer_size is only 32M Maybe you want to lower this to 64M of even leave it undefined to see what the default does for you. PPS. Here's the my.cnf settings for this machine: [mysqld] safe-show-database skip-innodb max_connections = 500 key_buffer = 32M myisam_sort_buffer_size = 64M join_buffer_size = 1M read_buffer_size = 1M sort_buffer_size = 2M table_cache = 1800 thread_cache_size = 384 wait_timeout = 90 connect_timeout = 10 tmp_table_size = 64M max_heap_table_size = 64M max_allowed_packet = 16M max_connect_errors = 10 read_rnd_buffer_size = 524288 bulk_insert_buffer_size = 8M query_cache_limit = 3M query_cache_size = 80M query_cache_type = 1 query_prealloc_size = 163840 query_alloc_block_size = 32768 skip-name-resolve [mysqld_safe] open_files_limit = 8192 [mysqldump] quick max_allowed_packet = 16M [myisamchk] key_buffer = 16M sort_buffer = 16M read_buffer = 16M write_buffer = 16M [mysqlhotcopy] interactive-timeout log = /var/log/mysql/mysql_logfile -- Mark Saad ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fast rate of major FreeBSD releases to STABLE
Chris wrote: and its for a desktop element of the os, does it matter if servers running FreeBSD have to remain on vulnerable versions of ports as a result of this? This looks like another call to have RELENG_x branches on ports, with which I agree. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fast rate of major FreeBSD releases to STABLE
Ivan Voras wrote: Chris wrote: and its for a desktop element of the os, does it matter if servers running FreeBSD have to remain on vulnerable versions of ports as a result of this? This looks like another call to have RELENG_x branches on ports, with which I agree. Hmm... Branching is not about to do it, or not to do it, but about who will invest their time to do it. By making it as an official offer we have to make sure that: - STABLE branch is well maintained. What's the rule of MFC in these branches? For src/ the answer is clear, but for ports/ I do not think it's obvious. What's the standard choosing particular ports' version? Who will be responsible for that? - packages are continuously built and mirrored. This could cause confusion about should I use -HEAD ports/, or RELENG_X ports/? Not to mention that it needs a doubled computation resource for package cluster. So, while I agree that having branches is a very nice idea I feel that it is not quite exercisable at the moment. It's easy for committers to do make universe to verify that their work does not break build, but it's not that easy for porters to make sure that a commit does not break the -STABLE branch... Cheers, -- Xin LI [EMAIL PROTECTED] http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
Re: mysql frequently crash on 6.2
- Albert Wong [EMAIL PROTECTED] wrote: key_buffer = 32M key_buffer has the most influence over the performance of MyISAM database. You should increase it as much as possible. On a dedicated 2GB server, 1GB is good. But it only helps, if you actually have indexes. There is no point is increasing it bigger than the size of your indexes (*.MYI files). But if you can hold all of the indexes in RAM, everything gets really, really fast. BTW, I agree with the other comments about the MySQL query cache. It is more of a work around for two problems: * A poorly indexed database, so that queries that return small results don't use an index, so caching the results is required. * Dumb applications that send the same query over and over again, even though the database has not changed. Some e-mail servers do this. A query cache should be small (5MB or less), if you use it at all. And you should never cache large results (there is an option that sets the size threshold). But I use MySQL 5.0 on several FreeBSD 6 systems, and they are moderately busy (250 q/s 450 q/s), and it works ok. MyISAM is the problem, and I need to switch to InnoDB. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
