Memory usage increased
Hi, I'm running v2.7.2.3.g01603-DEVELOPMENT on a box which I've just upgraded from an AMD64 3200+ single core with 1.5GB of RAM to a Phenom II 955 quad core with 4GB of RAM. The usage pattern hasn't changed. Prior to the upgrade the box was using around 250 megs of swap and apparently needed it because it would be swapping in and out. After the upgrade (and modifying the kernel for SMP support and adjusting the ethernet and audio devices) the box is showing around 1.5GB active, 1GB inactive and about 600MB between wired, cache and buf. The active and inactive alone would have been enough to run me out of swap on the old box. How can I find out what is using all the memory, and whether or not anything is astray ? -- Steve O'Hara-Smith | Directable Mirror Arrays C:WIN | A better way to focus the sun The computer obeys and wins.|licences available see You lose and Bill collects. |http://www.sohara.org/
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
This is the final Call. I will push my BIND removal patch-set sometime really soon, probably today. You can use bind form pkgsrc as a replacement (either build locally or using prebuild binaries). The stability problem has been worked around in pkgsrc nad packages are available now. Justin already setup a wiki page for 2.8 to document the needes steps. I have updated these to what I finally used to make it work. Of course there are different possibilites to achieve the same (use the User option when building BIND or moving the config files to /usr/pkg and so on). Please choose for yourself. http://www.dragonflybsd.org/release28/ Also, you can change to BIND from pkgsrc *before* updating world to latest master. That will give you the opportunity to test with BIND from pkgsrc and still keep the BIND in base as a fallback. Jan -- professional: http://www.oscar-consult.de private: http://neslonek.homeunix.org/drupal/
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
On Thu, 6 May 2010 19:10:07 +0900, YONETANI Tomokazu qhwt+d...@les.ath.cx wrote: On Thu, May 06, 2010 at 11:50:25AM +0200, Jan Lentfer wrote: This is the final Call. I will push my BIND removal patch-set sometime really soon, probably today. You can use bind form pkgsrc as a replacement (either build locally or using prebuild binaries). The stability problem has been worked around in pkgsrc nad packages are available now. I'm wondering if you really need to import libldns and drill into the base, if you're not planning to replace the resolver in the libc. Just removing BIND from the base and adding net/drill to PKGSRC_PACKAGES in nrelease/Makefile appears to me to be enough. The only problem with the current patchset, though, is that pkgsrc doesn't know that we have libldns in the base, so it'll want to install libldns from pkgsrc first then build other things (net/nsd, for instance) linked to it. Maybe not really a big issue. Ok, I am a little bit puzzled and also frustrated now. I only brought libldns and drill in because a lot of people on IRC claimed dig or something like dig needs to be in base. ldns is only used for that, so if we don't want drill in base I can also kick ldns again, no problem except of some hours lost on worthless work. Finally we could also just add BIND from pkgsrc, that would have the minimum effect on end users, because everything they are used to being is would still be there, just in /usr/pkg. Jan -- professional: http://www.oscar-consult.de private: http://neslonek.homeunix.org/drupal/
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
On Thu, 6 May 2010, Jan Lentfer wrote: The stability problem has been worked around in pkgsrc nad packages are available now. Were the kqueue issues in DragonFly itself looked at/fixed?
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
+1 for having something like dig/host in base. 2010/5/6 Jan Lentfer jan.lent...@web.de: On Thu, 6 May 2010 19:10:07 +0900, YONETANI Tomokazu qhwt+d...@les.ath.cx wrote: On Thu, May 06, 2010 at 11:50:25AM +0200, Jan Lentfer wrote: This is the final Call. I will push my BIND removal patch-set sometime really soon, probably today. You can use bind form pkgsrc as a replacement (either build locally or using prebuild binaries). The stability problem has been worked around in pkgsrc nad packages are available now. I'm wondering if you really need to import libldns and drill into the base, if you're not planning to replace the resolver in the libc. Just removing BIND from the base and adding net/drill to PKGSRC_PACKAGES in nrelease/Makefile appears to me to be enough. The only problem with the current patchset, though, is that pkgsrc doesn't know that we have libldns in the base, so it'll want to install libldns from pkgsrc first then build other things (net/nsd, for instance) linked to it. Maybe not really a big issue. Ok, I am a little bit puzzled and also frustrated now. I only brought libldns and drill in because a lot of people on IRC claimed dig or something like dig needs to be in base. ldns is only used for that, so if we don't want drill in base I can also kick ldns again, no problem except of some hours lost on worthless work. Finally we could also just add BIND from pkgsrc, that would have the minimum effect on end users, because everything they are used to being is would still be there, just in /usr/pkg. Jan -- professional: http://www.oscar-consult.de private: http://neslonek.homeunix.org/drupal/ -- Cheers, Antonio Huete
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
Am 06.05.2010 13:06, schrieb Antonio Huete Jimenez: +1 for having something like dig/host in base. You could easily have it by just installing bind from pkgsrc (or drill, as you prefer). And new installations would have it anyways because it comes on the LiveCD. The only question is: Do we want to _maintain_ a drill and libldns in our base from now on? Because that's what we would have to do if it's in base. IMO it's generally not a good thing if something is in base and exists in pkgsrc and the version in pkgsrc is much newer in due to lack of maintenance of the version in base. Even if you install the pkgsrc version then, you still have the problem that the base version shadows it (per $PATH), and you can't delete the base version without a knob that prevents re-installation, and so on. Sascha -- http://yoyodyne.ath.cx
Fwd: BSDday 2010 - Pre Call for Papers (Pre-CFP)
BSDday Argentina 2010 - http://www.bsdday.org/ Buenos Aires City * OpenBSDeros - OpenBSD User Group and * BUG-DC-UBA-AR BSD User Group of Computer Department of the Faculty of Natural Sciences, University of Buenos Aires, call to the community of free software, users, system administrators and developers of BSD systems for participation to BSDday 2010. The subject of the event is BSD operating systems, BSD-licensed software, licensing issues, BSD philosophy and related topics. There is no maximum number of speakers or length of the talks, but you should indicate those both at the time of the talk submission. Talks and slides can be in Spanish or English, talks with practical/lab content besides theoretical content in which attendees can perform labs practices and exercises are preferred over purely theoretical ones. For lab talks the speaker should indicate the materials assistants must have (i.e. a laptop with such and such OS). NOTE: On budget issues, the organizators may pay some of the passages or hotel, in whole or in part, to the selected authors residing outside the Buenos Aires City (Argentina). We appreciate the contribution of everyone in the dissemination of this call and the event itself, feel free to forward this email to any individuals/organizations you may think would be interested in it. == Where to send? == The information of the paper should be sent in plain text and slide attachments (if you have) to the following address of email: llamcha [in] bsdday.org. == How to send == The sending of the proposed talk should have the following information: * Title: Title of the paper. * Author's Name: Brief description of each, place of residence, association, BUG, agency or enterprise to which he belongs, if applicable. * Type: It can be traditional or workshop. * Estimated time of duration: The talks are usually 45 'and the workshops have a length of 1:45. If it is more or less the time required, please tell us. * Brief description of the talk: One or two paragraphs to explain the content of the presentation. * Level of the attendees: newbie / intermediate / advanced / expert. * Background information: Specify that knowledge must have assistants. * Subject: programming, multimedia, communications, workstation, network services, interoperability, education, kernel, etc. * Phone of the author: To communicate with you. * Residence: of the author. == Format == The shipment of the slides should be one of the following formats: * Openoffice.org presentation * HTML standard * Postscript * PDF * Plaintext * LaTex == License == Specify a license that allows the event organizers and distribute material that can be downloaded from the BSDday website. -- http://dfbsd.trackbsd.org.ar
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
On Thu, 6 May 2010 06:04:19 -0500 (CDT), Jeremy C. Reed r...@reedmedia.net wrote: Were the kqueue issues in DragonFly itself looked at/fixed? Afaik it is a bug in BIND and Samuel send a report to ISC. Jan -- professional: http://www.oscar-consult.de private: http://neslonek.homeunix.org/drupal/
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
On Thu, May 6, 2010 at 8:47 AM, Jan Lentfer jan.lent...@web.de wrote: On Thu, 6 May 2010 06:04:19 -0500 (CDT), Jeremy C. Reed r...@reedmedia.net wrote: Were the kqueue issues in DragonFly itself looked at/fixed? Afaik it is a bug in BIND and Samuel send a report to ISC. Jan I received a follow-up from ma...@isc, they think it's a kernel bug. So it's still up in the air. I'll dig in further soon. Sam
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
Sascha Wildner wrote: The only question is: Do we want to _maintain_ a drill and libldns in our base from now on? Because that's what we would have to do if it's in base. there needs to be some way to verify DNS out of the box. period. without pkgsrc. period. this is non optional, IMHO. otherwise I might as well port System-III unix and start UUCPing my email with a 300bps acoustic coupler.. kernel!dragonfly!ucbvax anyone?
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
On Thu, May 6, 2010 at 11:01 AM, Chris Turner c.tur...@199technologies.orgwrote: Sascha Wildner wrote: The only question is: Do we want to _maintain_ a drill and libldns in our base from now on? Because that's what we would have to do if it's in base. there needs to be some way to verify DNS out of the box. period. without pkgsrc. period. this is non optional, IMHO. otherwise I might as well port System-III unix and start UUCPing my email with a 300bps acoustic coupler.. kernel!dragonfly!ucbvax anyone? If you just need to verify that DNS works (resolve hostname to IP), then what's wrong with ping some.host.com? ;) Kills two birds with one stone: DNS lookups work, and Internet connection is live (if using a hostname on the Internet). No need for host, dig, nslookup, etc. ;) -- Freddie Cash fjwc...@gmail.com
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
Freddie Cash wrote: If you just need to verify that DNS works (resolve hostname to IP), then what's wrong with ping some.host.com http://some.host.com? ;) Kills two birds with one stone: DNS lookups work, and Internet connection is live (if using a hostname on the Internet). ok fair enough. was hopped up on coffee. blame it on the drugs. sorry bout that. :)
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
Jan Lentfer schrieb: Ok, I am a little bit puzzled and also frustrated now. I only brought libldns and drill in because a lot of people on IRC claimed dig or something like dig needs to be in base. ldns is only used for that, so if we don't want drill in base I can also kick ldns again, no problem except of some hours lost on worthless work. Finally we could also just add BIND from pkgsrc, that would have the minimum effect on end users, because everything they are used to being is would still be there, just in /usr/pkg. After another discussion I have decided to do the following: I will only remove BIND from base, no ldns and drill import. So anyone wanting to have either of the both will have to install them from pkgsrc (before updateing their world, I would recommend). We will see until next release how we will proceed with this. I prefer to just leave it this way and add pkgsrc-BIND to the Live-CD. Jan
unsubscribe
Re: [HEADS UP] pkgsrc stuff
On Wed, May 5, 2010 10:13 pm, Justin C. Sherrill wrote: Thing 1: I've finally almost got a 2.7 build of pkgsrc-2010Q1 complete, so I'm going to shift the default pkg_radd target to point at it for each architecture within the next 24 hours. Aaaand it's pointed. Packages downloaded through pkg_radd (or directly) for 2.6 and 2.7 are now from pkgsrc-2010Q1.
