Re: multiprocessors
Eric McCoy wrote: You are looking in the wrong place. A C *column*, not a CPU *row*. FreeBSD will only ever show the total CPU time on the CPU row. This is something like what you will see on an SMP system: PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 89704 emccoy960 2484K 1660K CPU1 0 0:00 0.51% 0.05% top 97005 root 960 3092K 1248K select 1 29:28 0.00% 0.00% ntpd Except that that column isn't present by default when it's not running SMP, even if there are two processors. Here's the output from a fresh install (yesterday) on a dual Opteron without SMP enabled yet: PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 240 root 960 3268K 1776K select 0:07 0.00% 0.00% dhclient 408 root 960 9468K 3572K select 0:00 0.00% 0.00% sendmail 425 root 80 3620K 1264K nanslp 0:00 0.00% 0.00% cron Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot use cvsup with 5.3-release
Tetsuji Maverick Rai wrote: *default host=cvsup.jp.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix src-all I don't think you want tag=. as the default. That would put you the most current sources for the OS, which may have plenty of transient issues you don't want to have to deal with. I use the following supfile regularly. You can see that I set the default tag to RELENG_5_3 which is basically the original release of 5.3 plus security updates (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html). I do that because these are servers that I try to keep as stable as possible. For a personal system, you may prefer to use RELENG_5 to get something more up to date, without being the bleeding edge of CVS updates. You can also see that I specify a different tag to grab for ports, so that I can get the updates on them. *default host=cvsup12.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_5_3 *default delete use-rel-suffix *default compress src-all ports-all tag=. Good luck, Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rebuilding everything
Darksidex wrote: How could I re-compile and re-install everything to take into account the new directives in make.conf? Ciao Vittorio You can use portupgrade -vaf Though that would only affect ports/packages you've installed, and not the rest of your system. I regularly cvsup /usr/ports and /usr/src and use portupgrade -arR to upgrade my ports and make buildworld make buildkernel KERNCONF=GENERIC make installkernel KERNCONF=GENERIC make installworld to update the rest of my system. I still consider myself very new to most of this, though, so I'm not certain, but I think the system should be able to determine your CPUTYPE automatically, without needing it hardcoded in make.conf. I think you should only need to use this directive if for some reason it's improperly detecting your cpu type. Hopefully someone can confirm or disprove that for you, though. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [OT] Re: MS Exchange server on FreeBSD?
That is truly one of the most disturbing things I've ever read (about technology, anyway). Must be careful not to frighten small children, or all but the most experienced sysamins, with that one. Tom Ean Kingston wrote: As someone who has inhereted an Exchange server I have a few hints for you. 1 Run Exchange on a Dedicated Windows Server (2000 or 2003). Do not fiddle with VMware or Wine. You are going to need a license for Windows to run Exchange under VMware (or bochs). You are probably going to need a license of Windows to run it under wine (if that is even possible). In any case, you will lose stability if you don't dedicate a system to Windows. 2 You need to keep the disk where Exchange stores its mail database at least 55% free or Exchange will not work properly. This is because you need to periodically rebuild the Exchange database to keep performance tollerable. Also when mail is deleted in an exchange mail store, it is not actually deleted but just marked for deletion. You need to take the mail store offline (so nobody can access their mailbox) periodically and run a tool to purge the deleted items. This takes hours on any decent sized mail system. When this happens it creates temporary files roughly 110% the size of the mail store. 3 Exchange is a pig. You would be best to have another Windows system running Active Directory to support your Exchange server. If you are thinking of using the Active Directory emulation available in Samba, forget it. Exchange changes the structure of the Active Directory when it is installed. You need a real Active Directory server. 4 On the topic of Exchange being a pig; you should set up a couple of FreeBSD systems that act as your MX hosts for inbound e-mail. Put something like Postfix or Exim (or any other smtp software you like) on there and setup at least simple spam filtering (even if it is just RBLs). Have these Postfix (or exim) system feed mail to your Exchange server. There are articles on the Web about how to get Postfix to check the validity of recipients against an Exchange server so you can bounce bogus mail at the border if you want. You could also have this system do the virus scanning (again numerous articles are available). 5 Exchange does an enormous amount of logging so those disks are going to fill up quickly. You need to run special tools before you delete the logs or you run the risk of not being able to recover your mail database in the event of catastrophic failure. Read over item 3 again, the process is similar. 6 Exchange shuts down when the disk that holds the mail store is 90% full. It will not restart until you free up some disk space. If you reach this situation you probably aren't following point 5 or point 3 enough. 7 Familiarize yourself with http://support.microsoft.com/?scid=kb;en-us;313184spid=1760sid=global you are going to be reading it (and related sites) a lot. 8 Unless you have users demanding shared calendars and automatic meeting scheduling, try to find a solution other than Exchange. I'm partial to Postfix, Courier-IMAP, OpenLDAP, SquirrelMail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is this a good or a bad idea to delete all off this ?
Gert Cuykens wrote: can i do controle C when i want to go to sleep while upgrading ? A cleaner solution, regardless of whatever you're running that you'd like to ^c, is to just let it run inside a screen session and reattach to the screen session later to see how it went. Screen should be every sysadmin's best friend. =) Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Received mail timestamp is off by 7 hours
Luke wrote: 1) NTP is difficult to configure. I've done it, but it wasn't trivial. It's always seemed rather straightforward to me, what in particular gave you trouble, perhaps we could help? 2) Finding an NTP server willing to accept traffic from the public isn't easy either. For me it involved a scavenger hunt through out-of-date websites and a lot of failed attempts. time.nist.gov is public, and has it's own atomic clock. A google search for public ntp servers also found this: http://www.pool.ntp.org/ 3) If your clock tends to run noticably fast or slow, constant NTP corrections tend to do more harm than good, at least in my experience. It got to where I couldn't even run a buildworld because NTP kept tinkering with the clock in the middle of the process. That suggests larger problems on your system, to me, but I dunno. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recommended trouble ticketing system
(redirecting back to the list) I've not used specialized bug tracking software before, so I'm not sure what kind of bug tracking specific features they might offer, but RT is, as the name suggests, just a generic request tracking system, and I don't see why it couldn't also be used for bug tracking. Normal usage typically involves a user sending an email to an RT address (of your choice) to make a request (of any type). RT then sends an email to a list of people who are set to respond to that RT queue, one of them will then respond and take (ownership of) the ticket and when done, change the status to resolved (there are other allowable statuses, as well). When necessary, multiple people can get involved with a given ticket, and/or it can be redirected to someone else as needed. Tom dave wrote: Hi, Question on rt, is it a general bug tracking software package as well? I'm looking for something like gnats which i have not been able to get working or bugzilla which i do not like because it puts email cleartext on the page. I've heard good things about rt, but don't know if it'll suit my situation. Thanks. Dave. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recommended trouble ticketing system
RT is wonderful, it does an excellent job managing information and emails, and is very customizable. If you want it to display something it normally wouldn't, you can query it's MySQL db yourself to generate the reports/stats you're interested in, or even modify it's main page to display information a program you wrote collects. Tom Mark Jayson Alvarez wrote: Hi, I'm looking for a software that we can use for trouble ticketing system. We are using Open Ticket Request System(OTRS) before but my superiors, told me that I can search for another better software for this purpose. Can you suggest me some of the trouble ticketing systems you have used before aside from OTRS and if there's any problem you have encountered using it or its advantages over OTRS. I did a quick search on google and freebsd ports and found Request Tracker(RT), also Trouble Ticket System from Freshmeat, and lastly WebTTS, but I'm having a hard time deciding which one to use. Suggestions are very much welcome. Thanks! __ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250 ___ 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]
Re: how long does it takes you to do a make buildworld
~35min, iirc. dual 2.2GHz Opterons 4GB RAM 36GB RAID 1 SCSI SCA Wouter van Rooij wrote: I'm very curious about how long it took you guys to do a make buildworld. So I thought let's start a topic about it.;-) See who is the most fast and please also put your hardware in the reply: like for example HP 3.4ghz 250gb hd 1024mb ram Wouter van Rooij ___ 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]
Re: web software
Peter Risdon wrote: If, on the other hand, you want to use a FreeBSD desktop and are looking for a good graphical website development tool, you might try Quanta. This is also in the ports. Or nvu might be worth a try as well, it's also in ports. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp on same partition as /
Chad Morland wrote: In your opinion is having /tmp on the same partition as / really THAT bad in this case? I'm just wondering cause some people have mentioned that its a major security risk. Really, I don't think it is for what this box is doing. It's obviously a much bigger security risk on a multiuser machine, but even without that being the case, I'm assuming the machine will be providing some sort of network service? Then it can still be a risk worth taking into account. One or more network services may be making use of /tmp, and if so an unauthenticated external user could plausibly find ways to make those services max out their usage of /tmp, possibly filling your root partition in the process. Even without worrying at all about malicious intent, /tmp on / makes it very easily to *accidentally* fill your root partition, but'll still be a pain for you to have to deal with it if that happens. More seriously, a vulnerability could be found in one of those services that could depend on files in /tmp being executable (which should never be true). With a separate /tmp partition, you can easily have it mounted with the noexec option for an added layer of security, so that even if they create a malicious executable in /tmp, they won't be able to execute it without moving it to another file system, which would probably require they already have shell access, defeating the purpose. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: groff/font/devX100 segfault in make installworld
Okay, so, no response initially, hopefully you guys won't mind some quicker and more specific followups, then. I just reinstalled again, followed only the steps I documented below (minus the vim portupgrade installs), and had identical results. This time, however, I tried changing the tag in my cvs-supfile from RELENG_5_3 to RELENG_5 and was able to successfully rebuild the source tree, but I know I tried that to no avail when I first encountered this problem a few months ago, and I'm not sure why it worked now (to be sure I then rolled it back to RELENG_5_3, saw the same problem, and successfully switched back to RELENG_5 again). But, ideally, I'd like to keep my production servers on RELENG_5_3 so that the only regular changes should be security patches (of course, these are exactly the kinds of surprises I was hoping to avoid by sticking with RELENG_5_3). So, my questions: 1) Was this not the best place to post a question like this? If not, I apologize, but where would have been more appropriate? 2) Was I not following the instructions/documentation properly for upgrading my system after install? (I got most of it initially from a series of Dru Lavigne articles on Oreilly, but followed up by reading the relevant portions of the handbook as well.) 3) If it does appear I was doing things properly, should I report this somewhere as a possible problem? I have been able to repeatedly reproduce this on multiple computers (though identical in hardware) across the span of at least 3 months (updating the source tree minutes before trying, each time), many of which were completely fresh installs. 4) Is there some way I could make the buildworld/installworld just skip at least the devX100 font if not all of groff in order to avoid this problem? Obviously that approach could be a problem for many other programs, but groff doesn't seem worth worrying over if it's preventing me from keeping my system patched. Or, if that's not a good idea, what might be a better work around? Thanks again! Tom Tom Trelvik wrote: So I ran into this problem a few months ago when I first started setting up a couple new servers. At the time I found one person online who'd had a very similar sounding problem some time before that, and he said it had gone away on its own for him, and that he suspected it was something corrupt in the source tree. I moved /usr/src out of the way and tried to cvsup a fresh source tree, and things started working. But now, it looks like I had just gotten lucky somehow. I've reinstalled one of those systems and the same issue cropped back up again, and I'm at a loss as to what to do about it this time. Pretty much all I did was install the User distribution set from 5.3-RELEASE-amd64-miniinst.iso and then installed bash2, sudo, screen, vim (NO_GUI=yes), portupgrade, cvsup-without-gui from ports (not that I expect those to matter, I'm just trying to be thorough since I did so little that I can think of that might affect this). I then created the following cvs-supfile: $ cat /root/cvs-supfile *default host=cvsup12.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_5_3 *default delete use-rel-suffix *default compress src-all ports-all tag=. and ran the following commands: # cd /usr/src \ cvsup -g -L 2 /root/cvs-supfile \ make buildworld \ make buildkernel KERNCONF=GENERIC \ make installkernel KERNCONF=GENERIC \ make installworld and the make installworld ends with this segfault: === gnu/usr.bin/groff/doc install-info --quiet --defsection=Miscellaneous --defentry= groff.info /usr/s hare/info/dir install -o root -g wheel -m 444 groff.info.gz /usr/share/info === gnu/usr.bin/groff/font === gnu/usr.bin/groff/font/devX100 Segmentation fault (core dumped) *** Error code 139 I tried moving /usr/src out of the way again, and cvsup'ing a fresh source tree again, but to no avail, and I'm once again at a loss, and not really sure how to diagnose what's causing this. I don't suppose anyone has any suggestions or pointers? Thanks a ton, I really appreciate it! Tom ___ 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]
Re: groff/font/devX100 segfault in make installworld
Bah, I knew I'd forget something ...
Tom Trelvik wrote:
{...}
So, my questions:
{...}
5) Is there documentation I haven't found on how to go about diagnosing
a problem such as this? I was very surprised my problem was not in the
build stage, but the actual install stage, which made me wonder if it
might be something as simple as a permission problem, but I have no idea
where to look for what.
Thanks again,
Tom
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
groff/font/devX100 segfault in make installworld
So I ran into this problem a few months ago when I first started setting up a couple new servers. At the time I found one person online who'd had a very similar sounding problem some time before that, and he said it had gone away on its own for him, and that he suspected it was something corrupt in the source tree. I moved /usr/src out of the way and tried to cvsup a fresh source tree, and things started working. But now, it looks like I had just gotten lucky somehow. I've reinstalled one of those systems and the same issue cropped back up again, and I'm at a loss as to what to do about it this time. Pretty much all I did was install the User distribution set from 5.3-RELEASE-amd64-miniinst.iso and then installed bash2, sudo, screen, vim (NO_GUI=yes), portupgrade, cvsup-without-gui from ports (not that I expect those to matter, I'm just trying to be thorough since I did so little that I can think of that might affect this). I then created the following cvs-supfile: $ cat /root/cvs-supfile *default host=cvsup12.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_5_3 *default delete use-rel-suffix *default compress src-all ports-all tag=. and ran the following commands: # cd /usr/src \ cvsup -g -L 2 /root/cvs-supfile \ make buildworld \ make buildkernel KERNCONF=GENERIC \ make installkernel KERNCONF=GENERIC \ make installworld and the make installworld ends with this segfault: === gnu/usr.bin/groff/doc install-info --quiet --defsection=Miscellaneous --defentry= groff.info /usr/s hare/info/dir install -o root -g wheel -m 444 groff.info.gz /usr/share/info === gnu/usr.bin/groff/font === gnu/usr.bin/groff/font/devX100 Segmentation fault (core dumped) *** Error code 139 I tried moving /usr/src out of the way again, and cvsup'ing a fresh source tree again, but to no avail, and I'm once again at a loss, and not really sure how to diagnose what's causing this. I don't suppose anyone has any suggestions or pointers? Thanks a ton, I really appreciate it! Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
