Re: Network sort of stops working with the em (intel) driver under load.
mark rowlands wrote: > Newly built and cvsupped system,with GENERIC kernel, when copying > large amounts of data over a gigabit link via scp the network will > hang after a couple of gig. I can then no longer login via ssh. If I > leave it be, after about 12-24 hours I can then login again. (A reboot > of course fixes the issue immediately...) . > > The system is very vanilla, only accf_http in loader.conf. No sysctl > tuning done, no firewall hankypanky. > > pciconf -lv | grep -A4 ^em > e...@pci0:3:4:0: class=0x02 card=0x001e8086 chip=0x100e8086 rev=0x02 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'Gigabit Ethernet Controller (82540EM)' > class = network > subclass = ethernet > > em0: port > 0xec00-0xec3f mem 0xfeae-0xfeaf,0xff irq 17 at device 4.0 on > pci3 > > Suggestions as to where I could look for more information as to the > precise nature of the problem gratefully received. Current plan is to > purchase another variety of gigabit card to see if it is specific to > the intel card. > If memory serves, I think there may have been some traffic about something like this on the -CURRENT list. You might look/search there and see if it sounds similar. If it seems like it might be the same thing, look for an MFC back to -STABLE. Sometimes the fix for very a specific item which has been addressed is to take a system to -STABLE in order to obtain the fixed bits. Research and confirm first, before considering such an update. My policy on -STABLE in the past is I only think about going there for a very narrow and specific situation where I know I have a problem that the devs have seen, analyzed, and fixed, with subsequent MFC. Something else too - if you can disable the vr and the USB chips completely, it might provide a data point. IRQ sharing is supposed to work well, and it is something that may be eliminated from the scenario easily if you do not need these things. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: what would take to allow binary upgrade to amd64?
Rob Farmer wrote: > On Sun, May 30, 2010 at 11:51 AM, Eitan Adler > wrote: >> I know that attempting to change from i386 to amd64 is is not possible > > The proper procedure for such an upgrade is as follows: > > 1) download and burn the relevant amd64 iso > 2) update your backups > 3) reformat and reinstall the OS from the CD > 4) restore your data and system config from the backups > 5) resume normal operation > > If the thought of reformatting your system is scary, because you don't > have backups or aren't sure they are comprehensive or work, then solve > that problem, rather than trying to invent workarounds to cover for > bad system administration. It will serve you much better in the long > run. I agree with this wholeheartedly. I recently posed the question about doing this with a make buildworld/etc dance from i386 to amd64, e.g. if there was a known sane method for accomplishing this. The general consensus was 'well, maybe if you spend enough time mucking with myriad problems as they come up maybe it's possible...'. Basically you will spend less time following the above directions, finish the project and be free to move on to others more quickly. It is easier when dealing with servers as they usually only have a fairly limited number of ports installed. Having the appropriate backups on hand, as if for bare-metal recovery, also allows for rolling it back to the previous state fairly quickly should one get into a stop/no-go/stuck situation. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: I can't install php5-mhash from ports
Yavuz Maşlak wrote: > I use freebsd7.3 . I ran portsnap update . > > I can't install php5-mhash from ports > cd /usr/ports/security/php5-mhash > # make > ===> Vulnerability check disabled, database not found > ===> License check disabled, port has not defined LICENSE > ===> Extracting for php5-mhash-5.3.2 > => MD5 Checksum OK for php-5.3.2.tar.bz2. > => SHA256 Checksum OK for php-5.3.2.tar.bz2. > tar: php-5.3.2/ext/mhash: Not found in archive > tar: Error exit delayed from previous errors. > *** Error code 1 > > Stop in /usr/ports/security/php5-mhash. > > There is no mhash directory in php-5.3.2 Have you read /usr/ports/UPDATING? Particularly section 20100409: Can't answer to possibility of the portsnap update being stale; I use csup along with portsdb -uF && pkgdb -u for tree/index refresh. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading default Apache1.3 to Apache22 port??
Kaya Saman wrote: [snip] > > It seems to have worked I just go into the config and check it; only > that part seems missing?? Maybe it's in a different place then /etc in > FreeBSD and I haven't worked it out yet. Even apache22 daemon is not in > /etc/rc.d. > > Oh well am sure will all be fine more Google'ing I think for me :-) > FreeBSD has a slightly different layout than Linux or Solaris. The configs and startup scripts belong in /usr/local/etc and /usr/local/etc/rc.d respectively. To invoke the startup script on boot up, simply place apache22_enable="YES" into the /etc/rc.conf file. The manual method using apachectl will still work at a command prompt. This is very general and you will find most things you install will operate this way. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Is the freeBSD mailing list using an automated ticket system?
James Phillips wrote: > Sorry about the blank post (hit enter by mistake): I feel I may have > received a phishing e-mail. This may explain why somebody pasted their > root password on the mailing list over the last few days: > [snip] The answer is no. Some script kiddie thought it might be fun to stick the email list into this companies ticketing system, and/or vice versa by subscribing the list to the ticketing system. > > This is an automated response to inform you that your question has been > entered into our system, and will be reviewed shortly. Your ticket has > been submitted into the "General Support" department. > > We will respond to you as soon as possible. > > == > Please keep this information, and use it when refering to your ticket: > > Ticket subject: Re: 7.0/i386 to 8.0/amd64 - gmirror/gstripe migration > Ticket number: 24508771 > Ticket link: https://secure.mpcustomer.com/ticket.php?ticket=24508771 > Ticket body: > Hi! > A lot of people are seeing this, some have complained to the powers that be on both sides. I'm not 'in the loop' or totally privy but I seem to get the impression from what little I've read about the situation is it has been reported to both the company involved and postmaster. I think the last thing I recall was the company is expecting the list postmaster to 'fix' it, and have done nothing with the issue. Someone with more details may elaborate. Me, and my $.02, is that if it affected *my* ticketing system I'd do whatever I had to do to fix *my* ticketing system, irregardless of what other third party might be involved. But that's just me -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [#24506597] apache 2.2.15_7 upgrade fails
dedica...@midphase.com wrote: > > Hi, > > Let us know the server IP in question, along with the root login details > so we could check further. And, of course, since this content is currently being mirrored on the public mailing list freebsd-questions it will be publicly available. While most of the true list users are professionals who would not abuse such information, that cannot be said for all the people who may come across such publicly available information. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Interpretting 3Ware error messages
Matthew Seaman wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 18/05/2010 15:43:25, Doug Poland wrote: >> Hello, >> >> I have a 7.2-R i386 system running a 3ware 9500S-4LP SATA 150 >> controller with 4 SATA drives. I recently starting seeing the >> following in my logs >> >> smartd[906]: Device: /dev/twa0 [3ware_disk_00], 1 Currently unreadable >> (pending) sectors >> smartd[906]: Device: /dev/twa0 [3ware_disk_00], 1 Offline ^^^ >> uncorrectable sectors ^ I think this error usually indicates that there are sectors that are pending remap, but will not get remapped or marked out until the next write occurs to them. On blank space these can easily be gotten rid of with a write from dd, however you don't want to be messing with this around active data. >> Using the twi_cli program, I can examine the disk subsystem, but I do >> not see any issues with an underlying drive. >> >> Unit UnitType Status %RCmpl %V/I/M Port Stripe Size(GB) >> >> u0 RAID-10 OK - - - 64K 298.002 >> u0-0 RAID-1OK - - - - - >> u0-0-0 DISK OK - - p2- 149.001 >> u0-0-1 DISK OK - - p3- 149.001 >> u0-1 RAID-1OK - - - - - >> u0-1-0 DISK OK - - p0- 149.001 >> u0-1-1 DISK OK - - p1- 149.001 >> >> >> I suspect a disk problem, but cannot identify the individual disk or >> the nature of the problem. Can anyone shed some light on this? >> > Look at the SMART data for the disk(s) -- my guess is that you're seeing > sectors failing and being re-mapped by the drive firmware. If this is > happening to any significant extent the disk may well be reaching the > end of its usable life: happily you would seem to have been alerted to > that in time to do something about it without needing to run around in a > blind panic. If the remap area is not yet filled these should still get remapped at next write. If it is full replace the drive. > There's a background task you can set up on 3ware controllers that will > attempt to access all sectors of a disk specifically to bring to light > problems like this, which otherwise could go unnoticed for a long time > and lead to silent data corruption. Many controllers refer to this as 'disk scrub' or 'disk verify'. If the remap zone still has space available a scrub should juggle sectors around and clear this counter. Periodic scrubbing can find and fix the 'silent data corruption', which is data sectors which have failed between the time of the last write and the next read. When this pattern is spread out across multiple drives you won't know it until you have a drive go bad, pull it and replace, then find the array will not rebuild. I scrub my arrays every Friday night. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
re: building apr1 fails
DA Forsyth wrote: [snip] >> I just updated Apache to 2.2.15_5 yesterday and it builds fine when >> the above mentioned option is turned off. It was actually the day before yesterday, when it was still 2.2.15_5. > Yes indeed, I upgraded the main server yesterday and it built fine > except for having to turn 'mod_ssl' off as it kept dying in the ssl > code. I don't need ssl anyway. > > However, today an update (cvsup) shows that that option has been > removed entirely, I have just searched the Makefile to confirm it, > also mentioned in UPDATING. I see what you mean. I just csup'd and it is now apache-2.2.15_7, with the changes you described. So I just #'d out the WITHOUT_APR_FROM_PORTS=true line in my /var/db/ports/apache22/options file. Tried a simple portupgrade -a which usually does the trick for upgrading Apache painlessly, but it completely bombed with errors. > So now apache HAS to use devel/apr1 but apr1 will not compile with no > real clue as to why not. So I changed to /usr/ports/devel/apr1, built and installed this port manually to see if it would error out. It built and installed OK, pulling in some dependencies during the process. So I then tried to manually upgrade apache-2.2.15_5 with the make deinstall && make reinstall dance and it barfed because when apache compiles it builds the apr1 ports *again*. OK - so I pkg_deinstalled the apr1 install and did make clean for the apache build and started over. This time it built OK, and make deinstall && make reinstall succeeded. So now I somehow actually have upgraded to apache-2.2.15_7. > I have just finished upgrading perl to 5.10.1, with a forced > recompile of everything that depends on it, and of course > apache22/apr still fails. > Differences between us are that I am still using perl 5.8.9, and possibly I have an WITHOUT_X11= yes entry in my make.conf that you may not. You might try and see if the apr1 port will build and install by itself. I'm also wondering if my installing it, then removing it somehow left behind a file that the apache build process was expecting to be present. I recall somewhere in the process something complained that apr-1-config could not be found. The apr1 port does need to be removed because apache build will rebuild it a second time and bomb trying to install it if the port is already installed. As to exactly *why* I eventually succeeded I'm not entirely clear. :-) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Apache web server being attacked
Aiza wrote:
> I put apache13 in a jail and left inbound port 80 open in my firewall.
> There is no domain name pointing to my web server. The content there is
> a small apache web application that fools web
> email address harvest programs into harvesting bogus email address from
> web page. http://www.monkeys.com/wpoison This is what I am doing.
>
> Since setting this up I have not had any bots scan the site for email
> address. But have had port 80 attacks that did not work. MY Apache
> access and error logs follow.
>
[snip log content]
> As you can see looks like a script kiddy is running something they dont
> understand. "/usr/local/www/data//phpmyadmin2/config.inc.php"
> there should only be a single / between data/phpmyadmin2.
>
> But beside that looks like php config.inc.php file is a target and
> phpmyadmin also is a target. The apache return code 404 means not found
> so no effect to me.
>
> Has anyone seen this junk hitting their apache web servers or have any
> different explanation of what this means?
Sorry to tell you this, but this kind of thing goes on all the time. You can
fine tune mod_security for some control for SQL injection techniques, as
well as many other generic forms of locking down the web server in general.
Generally speaking, the bulk of this does nothing more than filling the logs
- BUT - all it takes is for one app to let the attacker "leak" onto your
hard drive and they're in. I see a lot of scans for roundcube and
phpMyAdmin. Have also seen a lot of phpBB in the past.
The attackers spew lots of requests but the needle in the haystack they are
looking for is that one app that has a known vulnerability. In addition to
securing the web server itself you should monitor any app running on it for
reported security flaws and keep them updated to the latest "safe" versions.
You can also add to the hardening of your web server (if Apache) with
various .htaccess + mod_rewrite tricks. Examples include:
# block all smarty templates (no reason to have these exposed)
RedirectMatch gone ^/.*\.tpl$
# block all .log (log files), .sql (sql dump/export) and .conf (config
files) files in case some day these files move to another directory
RedirectMatch gone ^.*\.(sql|log|conf)$
# block access to the 'Smarty-*' directory
RedirectMatch gone ^.*Smarty.*$
# block common files present that you don't want served
RedirectMatch gone CHANGELOG.*
RedirectMatch gone COPYRIGHT.*
RedirectMatch gone INSTALL.*
RedirectMatch gone NEW.*
RedirectMatch gone README.*
RedirectMatch gone UPGRADE.*
RedirectMatch gone VERSION.*
# block access to directories
Redirect gone /upgrade
Redirect gone /tmp
Redirect gone /var
Redirect gone /sql
#Redirect pesky stuff based on referrer
Options -MultiViews -Indexes
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_USER_AGENT} ^Twiceler [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^Morfeus [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^Toata [NC]
RewriteRule .* - [F,L]
There is much and many more, just a couple of examples for ideas. :-)
-Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: building apr1 fails
DA Forsyth wrote: > Hiya all > > Going round in circles here tryign to update apache 2.0 to 2.2 > I have read UPDATING and it says to uninstall apache before updating > apr. Yes - the presence of 2.0 conflicts with 2.2 so it is necessary to remove first. > However, apr will not build, giving > > ===> Building for apr-ipv6-devrandom-gdbm-db42-1.4.2.1.3.9_1 > cd /usr/ports/devel/apr1/work/apr-1.4.2; /usr/bin/env SHELL=/bin/sh > NO_LINT=YES ACLOCAL=/usr/local/bin/aclocal-1.9 > AUTOMAKE=/usr/local/bin/automake-1.9 AUTOMAKE_VERSION=19 > AUTOCONF=/usr/local/bin/autoconf-2.62 > AUTOHEADER=/usr/local/bin/autoheader-2.62 [snip] > /usr/ports/devel/apr1/work/apr-1.4.2/libtool: Xpasswd/apr_getpass.lo: > not found > libtool: compile: cannot determine name of library object from `': > not found > *** Error code 1 > > Stop in /usr/ports/devel/apr1/work/apr-1.4.2. > *** Error code 1 > > Stop in /usr/ports/devel/apr1/work/apr-1.4.2. > *** Error code 1 > > Stop in /usr/ports/devel/apr1. > *** Error code 1 > > Stop in /usr/ports/devel/apr1. > == > > I've tried a bunch of stuff, including rebuilding libtool22, > upgrading to python26 and a few other things I cannot recall now. > I have seen before reports concerning problems with building Apache utilizing the devel/apr port (the recommended default). Since the variables controlling the Apache version have changed over time you should look at your make.conf and ensure there is no left over cruft of the WITH_APACHE=xx or USE_APACHE=xx variety. In the beginning of the move towards 2.0 and the subsequent introduction of 2.2 it was necessary to set these, but that is no longer true. When you do 'make config' for the Apache build, deselect the 'APR_FROM_PORTS "Use devel/apr (recommended)"' option. It is "ON" by default and is the recommended selection. It has some kind of problem and this error has been reported on these lists before. I just updated Apache to 2.2.15_5 yesterday and it builds fine when the above mentioned option is turned off. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: glabel nor tunefs save my labels
Demelier David wrote: > Hi, > I was trying to follow this guide to make labels : > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-glabel.html > > It does not work here, I boot single user and ran these commands : > glabel label usr /dev/ad0s1f [snip] If there was older software on the drive previously you might try blanking the MBR. I know I had trouble installing 8.0 on a drive that previously had 6.2 installed on it. Something about the MBR support in 8.0 was different and the labels from 6.2 were invisible to it. So when it came time for disklabel to write out the labels during the 8.0 install it would fail. This is what I did: Boot from a LiveFS CD and execute: sysctl kern.geom.debugflags=16 dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 Replace 'x' in adx with your drive number. If your problem is being caused by the same situation I experienced this should take care of it. > > Do I am missing something? On my other machine it prints a lot of > GEOM: ad2s1a: geometry does not match label (255h,63s != 16h,255s). > GEOM: ad2s1c: geometry does not match label (255h,63s != 16h,255s). > GEOM: ad2s1: geometry does not match label (255h,63s != 16h,255s). > For the most part simply ignore these. Lots of people see them nowadays and considered to be cosmetic and harmless. I believe it has something to do the drift away from the old MBR DOS compatibility days and the move to newer slicing/partitioning schemes. In other words these will eventually disappear, but in the meantime are probably a red herring. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FWIW, a datapoint.
Gary Kline wrote: > > Hopefully no one will face this, but the only way around getting > past pcbsd seems to be via an over-the-wire upgrade. The > 8.0-bootonly.iso for the i386 failed to boot. About two hours > ago tho i was able to csup ports from its 07jan to 10may status. > Next I will pull over the stable-cvsup stuff and see if I can > fire off a build. hope this works. the kybd is hard to use. > [etc.] > I put a PCBSD install on an unused space on my drive. Back when I did it the FreeBSD 8.0 version was still in beta, and that is what I installed. The current state of affairs is now release status with FreeBSD 8.0 P2. I haven't seen it or used it in a while now. When I installed it I did not install any of the extra addon software packages, but rather installed the ports system and proceeded to csup it to current status. I then used the ports system to install any additional stuff I wanted. Generally speaking it was a fairly positive experience in that by and large mostly everything "Just Worked". Seeing the Flash support already installed and functioning in Firefox was surprising, to say the least. Since the install comes with KDE 4.3.5 and I want to upgrade it to 4.4.x I will be giving portupgrade another go around. I had used portupgrade to successfully update all ports once before and it worked as it normally would on a regular (non PCBSD) install of Freebsd. FWIW, by not installing anything (except the base install which includes KDE,etc) using the PCBSD software installer utilizing the normal methods of installing with the ports system and maintenance with portupgrade seems to work just as it would on a normal FreeBSD install. When I get adventurous I'll see how it does with the KDE 4.4.x upgrade one of these days. Have been waiting for the dust to settle there. As to why your bootonly or LiveCD CD's have problems booting, that is probably a separate issue. But I did notice the PCBSD install is using GPT labeling for it's partition labels. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: php-cgi 5.3.x and APC 3.1.3
Joe Auty wrote: > Hello, > > I'm trying to get the APC user cache to work for me... It works with PHP > installed as an Apache module, but not as a CGI. I run Apache with the event mpm. This may, or may not be wise, but I've been doing it for a while now and had no problems with it. I also use Xcache so my comments are not APC specific. Since not all of PHP is considered thread safe it is not advisable to run PHP on the event mpm as it is a threaded version. The way around this is to not use mod_php but instead run mod_fcgid.so so PHP can be run as a FastCGI. > I understand that in order to get this to work one has to add a: > >> FastCgiConfig -maxClassProcesses 1 > > to their Apache config (for those that use Apache). I've done this, but > I'm still not seeing any evidence that the user cache is working. This I do not know about and have never seen, but I do recall floundering around in the beginning and being very confused by the difference between exec'ing PHP code as a CGI as opposed to running it in a FastCGI process. There is a huge difference, with the FastCGI being many times faster. > The reason why I'm writing to this list rather than a PHP list is > because I'm a little confused by some of the PHP install options. It > looks like in 5.2 there was a FastCGI compile option. I'm assuming this > is enabled by default in 5.3? Not sure about what is in the default config, I'd have to look. But to use what I've described above you do not need to build/install mod_php, or have it in the LoadModule section of httpd.conf. But you do need to build PHP with CGI and CLI support. I have mod_fcgid.so in the LoadModule directives section of my httpd.conf. See the part below about "connecting" Apache to a "long running" PHP process. >> # php-cgi -v >> PHP 5.3.2 with Suhosin-Patch (cgi-fcgi) (built: May 7 2010 12:53:07) >> Copyright (c) 1997-2009 The PHP Group >> Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies > > What's confusing is the existence of both mod_fastcgi and mod_fcgi. Is > PHP compiled against fastcgi or fcgi? It looks like the former is > required for my setup. Since the key ingredient to this is the > FastCgiConfig directive above, I'm not sure if there is a way to test > that this directive has been recognized? I'm not seeing it in my > phpinfo() screens... Could I have mod_fcgi built into php-cgi and this > FastCGI Apache directive is being ignored? IIRC correctly, the mod_fastcgi became deprecated when the Apache Foundation took over and imported the mod_fcgi codebase into the Apache project. Not totally sure, but this is what I seem to think I remember. But neither mod_fastcgi nor mod_fcgi get built into php-cgi, to reuse your terminology. These are Apache server modules designed to connect the Apache server to a different process running outside and separate from Apache. The module is just a gateway for connecting to the PHP FastCGI process. When you execute php -v as a CLI, it runs, returns the info, and exits. The difference between this and a FastCGI process is the FastCGI is what is known as a "long running process". It starts the PHP interpreter as well as loading any PHP modules specified in extensions.ini, but it does not exit or "end", but continues to run. The advantage of this is it does not waste resource overhead creating and destroying interpreters to run each piece of PHP code that comes along. > In case this is relevant, I'm not doing any suexec stuff just yet. > Me, I would try and avoid suexec whenever/wherever possible. It is very slow. At any rate, this stuff is *very* confusing. So this example from a working Apache running the event mpm and PHP as a FastCGI. In addition to the LoadModule line mentioned above there is also the following: [...other stuff here...] # added for mod_fcgid #SetHandler fcgid-script FCGIWrapper /usr/local/bin/php-cgi .php Options ExecCGI # end of mod_fcgid change # added to enable mod_fcgid AddHandler fcgid-script .fcgi .php SocketPath /var/run/fcgidsock/ IPCConnectTimeout 10 IPCCommTimeout 20 OutputBufferSize 0 MaxRequestsPerProcess 500 In phpinfo(); you can see this: Server API CGI/FastCGI My options for PHP build: WITH_CLI=true WITH_CGI=true WITH_APACHE=true WITHOUT_DEBUG=true WITH_SUHOSIN=true WITH_MULTIBYTE=true WITHOUT_IPV6=true WITHOUT_MAILHEAD=true WITH_REDIRECT=true WITH_DISCARD=true WITH_FASTCGI=true WITH_PATHINFO=true Also keep in mind that any time PHP is rebuilt APC will need to be rebuilt too. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Space on root partition
Chip Camden wrote: > When partitioning the drive, I took the defaults -- which seems to create > a root partition that's too small. I'm at 59% usage, and every time I > install a new kernel I have to rm /boot/kernel.old to get it to go. > > Two questions: > > 1. Is there an easy way to resize partitions? It is not too much of a problem if it is the last partition followed by free space. But the location of / in the scheme of things generally precludes this. There are a few different approaches one can take to accomplish this, but my general feeling is doing so on a production box can invite disaster and you wind up with more problems than you started with. > 2. Is there anything in root I could safely symlink off to another > partition? I would tend to not want to go this route, as it is good to have / a fairly self-contained entity for recovery purposes. A lot of things can go wrong with a box, and if you can get to / in single user many may be fixable. > Here's a df: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ad4s1a507630 27338819363259%/ > devfs 11 0 100%/dev > /dev/ad4s1e507630 18467002 0%/tmp > /dev/ad4s1f 463086528 21941374 404098232 5%/usr > /dev/ad4s1d 4848462 201194 4259392 5%/var Example from one of my servers: Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a193M 91M 87M51%/ [snip] The other approach would be to decrease the size of what is installed in /. The main question [criterion] you should use if you need to pursue this is exactly how much code debugging do you need to hold in abeyance? For instance, I only run Release on production boxen with the only maintenance for security branch updates. For me the bits have been very stable, but if you should ever need code debugging the following practice will be a problem. You can comment out 'makeoptionsDEBUG=-g' from your kernel config file along with all other debugging facilities, and set WITHOUT_PROFILE= true in src.conf. I also have STRIP= -s in my make.conf, but IIRC this should only apply to ports builds. Delete all of the symbol files in /boot/kernel and /boot/kernel.old. After two kernel builds/installs the huge GENERIC gets moved out of the way. My i386 box has 91MB of space used in / and the 64 bit boxen are typically about 93-95MB. I only have one i386 box left and it's crunched down kernel is 4.2MB, and my 64 bit ones average around 4.5MB. This will mitigate a / being too small, but at the cost of kernel code debugging. If you are running Release on production boxen which just sit there and do their job, you may be able to forego the debugging facilities. In a different situation such as following -STABLE or -CURRENT and the code changing from time to time, you may need the kernel debugging facilities to assist the developers with problem resolution. Whether you can use this approach depends on your situation, e.g., do I need debugging or can I get away without it? YMMV! -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 8: gdbm.h: No such file or directory
perikillo wrote: > Hi. > > I want to install http://www.csamuel.org/software/vacation/ > > Version vacation-1.2.7.0, the INSTALL say: > > "under FreeBSD type 'gmake' to compile > the program. To install it you will need to do (as root) 'make install' > or, for FreeBSD, 'gmake install'." > This version is very old. [snip] > > "In file included from vacation.c:92:" ===> static GDBM_FILE db; in > vacation.h > > Now, I copy /usr/local/include/gdbm.h to /usr/include > > But now I got: > > gcc -g -Wall -DMAIN -Xlinker -warn-common > -D_PATH_VACATION=\"/usr/bin/vacation\" -o vacation vacation.c strlcpy.c > strlcat.c rfc822.c -lgdbm > /usr/bin/ld: cannot find -lgdbm > gmake: *** [vacation] Error 1 > > Perl is install with gdbm, what could cause the error? > Why not try using the one in the ports system? So much easier. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: help
Peter Winn wrote: > Could someone help me? I am running freebsd 7.2 and trying to connect > to my ISP using pppoa. > I have a usb Alcatel speedtouch modem but the driver cannot find the > modem. The kernel says the modem > is - cdce0: usb0 on uhub0but when I look in /dev I cannot see > that device. When I try to ./MAKEDEV cdce0 > it says command not found. Don't have this arrangement [Verizon DSL with PPPoE here]. However there is a page on this in the Handbook: http://www.freebsd.org/doc/en/books/handbook/pppoa.html Have no clue as to whether it is stale and out of date, or not. But you might give it a go if you haven't tried it yet. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 8.0 upgrade & geometry does not match label
Reinhard Haller wrote: > Hi, > > as far as I know my disk is not operating in dangerously dedicated mode. > Despite this I'm unable to upgrade to freebsd 8.0. Here is what the > gpart, mount, bsdlabel say. > [snip] > > I remember problems with the initial sysinstall because of geometry > problems -- the only way to get FreeBSD installed was to dedicate all of > the available space to FreeBSD. The geometry warnings are mostly a cosmetic error and generally can be ignored. Especially the one in sysinstall. > I've found a suggested solution to repair the mbr/label problem with > > dd if=/dev/zero of=/dev/ad4 count=1 oseek=1 > > and a warning not trying it on boot disks. > > Is there a better / safer solution around? > If there is I do not know of it. This is what I did when I had this problem: http://www.mail-archive.com/freebsd-questions@freebsd.org/msg227610.html -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Postfix signal 11
Ron wrote: > After I did a big portupgrade on the April 25th, I am now getting a lot > these... > > +pid 53508 (conftest), uid 0: exited on signal 11 (core dumped) > +pid 28553 (smtp), uid 125: exited on signal 11 > +pid 28569 (smtp), uid 125: exited on signal 11 > +pid 28657 (smtp), uid 125: exited on signal 11 > > ..in my logs. I've tried forcing a rebuild of postfix and all dependency > to no avail. I don't seem to be loosing any email. > > I'm assuming it's postfix (I don't use sendmail), but I could be wrong. > Anyone know what this is or where I should start looking? Did I not > upgrade something correctly after the big changes? > One quick thing you can check is your /etc/mail/mailer.conf: # Execute the Postfix sendmail program, named /usr/local/sbin/sendmail # sendmail /usr/local/sbin/sendmail send-mail/usr/local/sbin/sendmail mailq/usr/local/sbin/sendmail newaliases /usr/local/sbin/sendmail I've had this happen before when I did a system rebuild and the original system based sendmail became used again instead of the Postfix install. If this file got reset back to pointing at the system sendmail somehow you will see these errors. IIRC Postfix has a switch which selects where it gets installed. Perhaps the upgrade didn't put it back where it originally was located, in which case you are again executing the sendmail binary instead of the mail getting picked up by Postfix. This is what my current /etc/rc.conf looks like: #sendmail_enable="NONE" postfix_enable="YES" sendmail_enable="NO" #sendmail_flags="-bd" #sendmail_pidfile="/var/spool/postfix/pid/master.pid" #sendmail_procname="/usr/local/libexec/postfix/master" sendmail_outbound_enable="NO" sendmail_submit_enable="NO" sendmail_msp_queue_enable="NO" Also, if you are using sasl auth you might try rebuilding that as well. You might get more info looking in the /var/log/maillog too. Just a few quickies off the top of my head to get started with... -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Which CPUTYPE in make.conf?
C. P. Ghost wrote: > On Sat, Apr 24, 2010 at 7:32 PM, Michael Powell > wrote: >> I think this matters more to third party ports software builds than it >> does the system. I thought that large pieces of the kernel were designed >> to not make much, if any, use the various SIMD extensions. Maybe this has >> changed and I'm behind the times. > > I wouldn't bother setting CPUTYPE at all. It's more trouble than it's > worth. Actually, I've been setting CPUTYPE for many years and have never had any trouble as a result. I've always used the form: CPUTYPE?= blah instead of CPUTYPE= without the question mark. > And you're right: for most ports and for the whole system, it doesn't > really matter. If you have a very specific port that needs particular > tuning, it has either already been tuned individually by the port > maintainer, or you could apply more optimizations yourself (which would > likely require a specially compiled tool chain, when -O with > the base gcc/binutils isn't enough). I have also used CFLAGS= -O2 -pipe COPTFLAGS= -O2 -pipe. About the only place it will really make any difference is in some multimedia apps. And you're right that if needed the port maintainer has already taken care of this. > Unless you have a very specific need, better leave CPUTYPE alone. Thing is, any performance increase is only going to be very small. So small the difference can probably not be seen subjectively. I'll do it as long as it creates no problem; if any problem were to arise over this I'd kill it in a heartbeat and not fuss over it. It is a point of diminishing returns. [snip] -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installation queries
Glen Barber wrote: > Hi, > > Jorge Biquez wrote: >> I would like to hear if possible your comments and advice on this >> taht's related .. >> >> What if you have a to have several OS and distros to study or give >> consulting and developing services. I have this scenario now and I >> guess I have this optios. [snip] >> > > VirtualBox? YES! >> Thinking that you are looking to continue learning and you are >> offering consulting services where clients have different >> instllations. What would you choose of the above, if any? Or what would >> you do? >> > > FWIW, I run VirtualBox on all of my FreeBSD machines and my > Mac for similar purposes. It is much more convenient than carrying around > extra disks or obscure disk partitioning. > Me too. I have an AMD quad core and 8GB RAM. Virtualbox is one of the most painless ways to do this. Whichever OS you install in a VM it won't run as fast as it can if not a VM, but on the larger horsepower box it is very nearly unnoticeable. It's close enough that I'm quite satisfied. In fact it is what I do if I need Office for anything, fire up a Windows VM. I originally started doing this with a Pentium D 940 and 2GB RAM and it made the box a little sluggish. The move up to the higher horsepower box eliminated that. Virtualbox and higher horsepower gets my vote over continually monkeying around with altering slice/partitioning schemes. The more often you mess with that the higher the chance that you sooner or later make a little 'uh oh' and lose gobs of time wiping your drive and starting over. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Which CPUTYPE in make.conf?
Mike Clarke wrote: > > I have a AMD Athlon 4850e which is described as "Athlon 64 X2" > Dual-Core" processor. > > /usr/share/examples/etc/make.conf lists recognised CPU types, but which > of athlon64, athlon-mp or athlon-xp is the most appropriate for this > CPU? I've been using "athlon64" so far without any problems but I don't > know if it's the most appropriate choice or if there's even any > significant difference between them. > athlon64 is probably a good choice. I haven't looked at it in a while, and there isn't much difference. IIRC the older athlon-xp included support for 3D Now and mmx while the athlon64 adds sse and/or sse2. I think this matters more to third party ports software builds than it does the system. I thought that large pieces of the kernel were designed to not make much, if any, use the various SIMD extensions. Maybe this has changed and I'm behind the times. Your use of athlon64 seems reasonable to me. It is what I've been using. If it can be done better I'm always on the look out for better. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: KDE 4.4.2
ajtiM wrote: [snip] >> > ...and again my question: why upgrade on 4.4.2 after two months if >> > 4.4.3 coming out in the end of the month?? The version 4.4 was out in >> > February 9th! >> >> Because the release of this software on FreeBSD does not happen on the >> same day as KDE releases it. It has to be patched and ported by people >> who are volunteering their free time. These patches are needed to make >> compiling >> and running KDE on FreeBSD a worthwhile experience. This takes time. >> >> A lot of third party apps are not as 100% portable as they could be, and >> many contain a lot of 'Linuxisms' which need to be adjusted out. >> >> So do not look at the release dates on the KDE site and think that >> because KDE x.y.z is released by KDE on xx somemonth that it will >> magically appear in the FreeBSD ports immediately. This stuff has to be >> patched first. >> >> -Mike [snip] >> > I understand it but advertisement was not on KDE site but on the FreeBSD > KDE site. > Ah - Ok. I did not do an exhaustive review of the site so maybe I missed it, but I did not see any mention of KDE 4.4.2. The last was 4.3.4. Perhaps you misread the one all the way at the bottom as 4.4.2 when it is really 4.2.4? Probably I missed something. It is possible to check out from area51 what will be forthcoming. This is subject to quite a lot of change and me, I prefer to wait until it actually gets finalized and into the ports tree. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: KDE 4.4.2
ajtiM wrote: > On Friday 23 April 2010 13:39:44 Bruce Cran wrote: >> On Fri, Apr 23, 2010 at 07:58:12PM +1200, Andrew Hill wrote: >> > Hi does anyone know if kde 4.4.2 is in freebsd ports? >> >> It's not yet - a big upgrade to Xorg and KDE is being worked on so I >> guess it'll be available in a few days. >> > ...and again my question: why upgrade on 4.4.2 after two months if 4.4.3 > coming out in the end of the month?? The version 4.4 was out in February > 9th! > Because the release of this software on FreeBSD does not happen on the same day as KDE releases it. It has to be patched and ported by people who are volunteering their free time. These patches are needed to make compiling and running KDE on FreeBSD a worthwhile experience. This takes time. A lot of third party apps are not as 100% portable as they could be, and many contain a lot of 'Linuxisms' which need to be adjusted out. So do not look at the release dates on the KDE site and think that because KDE x.y.z is released by KDE on xx somemonth that it will magically appear in the FreeBSD ports immediately. This stuff has to be patched first. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Disk Usage
ill...@gmail.com wrote: > On 22 April 2010 12:02, Jerry wrote: >> I just did a fresh install of FreeBSD-8.0/amd64. Previously, I had >> FreeBSD-7.3/i386 installed. It appears the the size of "/" has >> increased dramatically. >> >> $ df -H >> Filesystem SizeUsed Avail Capacity Mounted on >> /dev/ad0s1a1.0G527M428M55%/ >> devfs 1.0k1.0k 0B 100%/dev >> /dev/ad0s1d520M 18k478M 0%/tmp >> /dev/ad0s1e236G6.0G212G 3%/usr >> /dev/ad1s1d238G720M218G 0%/var >> >> When I attempted to build World and a new kernel after first installing >> 8.0, I received an error that "/" was at 106% and the process stopped. I >> reinstalled 8.0 and increased the size to 1.0G and now everything >> appears to be working correctly. >> >> In my old installation, the root directory only used a minuscule amount >> of space. Why has it increased so dramatically in 8.0/amd64? >> > > 64bit executables are going to be larger, > sometimes as much as 2x, but do you > now have a bunch of (large) > /boot/kernel/*.symbols > files now? > You can comment out 'makeoptionsDEBUG=-g' from your kernel config file, along with all other debugging facilities and set WITHOUT_PROFILE= true in src.conf. I also have STRIP= -s in my make.conf, but IIRC this should only apply to ports builds. The downside to this is if you need to do some serious troubleshooting you're screwed. On production boxen I run Release versions, and only do security updates/patches or upgrade to the next Release. In the past using the most quiescent code has been good to me. After two kernel builds/installs the huge GENERIC gets moved out of the way. My i386 box has 91MB of space used in / and the 64 bit boxen are typically about 93-95MB. I only have one i386 box left and it's crunched down kernel is 4.2MB, and my 64 bit ones average around 4.5MB. This can be an effective strategy to mitigate a / being too small, but at the cost of reducing one's ability to get down and dirty troubleshooting code bugs. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: question about FreeBSD installing
王跃辉 wrote: > hi > I have a problem when I try to install FreeBSD as client OS on a Linux > OS. Sorry, but this does not make any sense to me. How are you trying to install FreeBSD on Linux? FreeBSD is an operating system, not an application. > following the instruction I find that I can't open the website of > www.fsmware.com to finish some download work. If you want to learn how to install FreeBSD you should start with The Handbook: English: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html another alternative: http://www.freebsd.org/doc/zh_CN.GB2312/books/handbook/index.html You may notice there is no mention of any downloading from www.fsmware.com. Perhaps the instructions you are trying to follow are incorrect? The Handbook might be better as it is the official documentation for FreeBSD. > it seems that the dns server > don't support the address in China Mainland. do you have any way to solve > the problem? > Nope. It is a problem with government politics in China and not FreeBSD related. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mplayer/mencoder build problems
Bernt Hansson wrote: > Hello again list! > > > I'm having problems building mplayer/mencoder. Did a csup today > 2010-04-21 but that did not help. If someone can point me to > the problem. > > cc -O2 -pipe -O -fomit-frame-pointer -fno-strict-aliasing -I./libavcodec > -I./libavformat -Wdisabled-optimization -Wno-pointer-sign > -Wdeclaration-after-statement -I. -I. -I./libavutil -O2 -pipe -O > -fomit-frame-pointer -fno-strict-aliasing -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -DHAVE_CONFIG_H > -I/usr/local/include/freetype2 -I.. -I../libavutil -I/usr/local/include > -I/usr/local/include -I/usr/local/include/SDL -I/usr/local/include > -D_REENTRANT -I/usr/local/include/freetype2 -I/usr/local/include > -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 > -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 > -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 > -I/usr/local/include -I/usr/local/include/glib-2.0 > -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 > -I/usr/local/include/freetype2 -I../libavcodec -I../libavformat > -Wdisabled-optimization -Wno-pointer-sign -Wdeclaration-after-statement > -I. -I.. -I../libavutil -O2 -pipe -O -fomit-frame-pointer > -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > -D_LARGEFILE64_SOURCE -DHAVE_CONFIG_H -I/usr/local/include/freetype2 > -I... -I.../libavutil -I/usr/local/include -I/usr/local/include > -I/usr/local/include/SDL -I/usr/local/include -D_REENTRANT > -I/usr/local/include/freetype2 -I/usr/local/include -D_THREAD_SAFE > -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include > -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo > -I/usr/local/include/pango-1.0 -I/usr/local/include > -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include > -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -c -o > dvb_tune.o dvb_tune.c > dvb_tune.c:33:19: error: error.h: No such file or directory > gmake[1]: *** [dvb_tune.o] Error 1 > gmake[1]: Leaving directory > `/usr/home/user/disk2/ports/multimedia/mplayer/work/MPlayer-1.0rc2/stream' > gmake: *** [stream/stream.a] Fel 2 > *** Error code 1 > > Stop in /usr/home/user/disk2/ports/multimedia/mplayer. > *** Error code 1 > > Stop in /usr/home/user/disk2/ports/multimedia/mplayer. > ___ See: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/145636 -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: lighten kernel
xyz wrote: > Thank you for your answer. > But how I can only choose the intel agp driver, without all others by > puting "agp" in the kernel configuration file? > Please don't top post - it is bad form. I think you may be confusing "agp" driver and video driver. The agp support in the kernel is for the agp slot on the motherboard chipset. If your motherboard uses an agp slot this is where an agp video card would be inserted. You would want this kernel support if such were the case. Video drivers, on the other hand, are part of the Xorg installation. This is a third party software installed from the ports system. The "all the others" you mention are probably the myriad of video card drivers installed along with Xorg. For the most part, the bulk of this software is not kernel related; the exception(s) being certain kernel modules such as dri and nvidia. The "all the others" video drivers are not kernel related. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Disabling DNS
Leslie Jensen wrote: > On 2010-04-20 15:41, pe...@vfemail.net wrote: >> >> I can change named_enable="YES" to named_enable="NO" in the /etc/rc.conf >> file. Should I delete the following line from the /etc/rc.conf file that >> says: [snip] > > > I would suggest that you remove both lines. > > named is off by default in /etc/defaults/rc.conf > To expand a little. The defaults mentioned here reside in /etc/defaults. The files under /etc/defaults should not be edited or changed as they can get overwritten during upgrades. The file /etc/rc.conf is designed to contain overrides to alter or change the default behaviors. It is the one to edit, not the ones under /etc/defaults. So yes, pretty much all of the suggestions will turn DNS off. You can safely delete the lines in /etc/rc.conf. Should you need to put them back in at some time in the future you can look these lines up in /etc/defaults/rc.conf, then edit /etc/rc.conf accordingly. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Disabling DNS
pe...@vfemail.net wrote: > > I have a FreeBSD server that, among other things, used to provide DNS for > a handful of domain names and a small network. All DNS is now provided by > new machines. On the old machine, DNS starts when the machine boots, and > bind continues to run lots of useless named and named-xfer processes > throughout the day. How do I turn off the DNS processes on the old > machine and stop it from starting every time the machine boots? > Look for named_enable="YES" in /etc/rc.conf and change the "YES" to "NO". This is for the standard built-in Bind. If some other way to start has been scripted manually, in say /etc/rc.local you'll need to look there. The third possibility is if some add on version from ports has been installed the start up script location should be in /usr/local/etc/rc.d - if this is the case and it utilizes the standard rc.subr startup system the first thing mentioned above should have taken care of it. If there is some other kind of manually created hard-coded script in /etc/local/etc/rc.d it will either need to be deleted or chmod to not execute. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: pyglet segfaults on FreeBSD 8.0/amd64/nVidia
Giuseppe Pagnoni wrote:
> Hello,
>
> First of all, let me apologize for the re- and cross-posting , but
> after a couple of weeks scouring the web and forums to no avail, I
> thought I would try again and query the FreeBSD mother source...
>
> I installed pyglet from the ports (latest version as of yesterday,
> py26-pyglet-1.1.2_1) on a FreeBSD 8.0 amd64 box, running the latest
> version of the ports' nvidia driver (nvidia-driver-195.36.15). I
> found that I cannot use either font.Text or text.label without causing
> segfaults. Here is some sample code that makes python crash:
>
> - SNIPPET 1
> import pyglet
> luxi = pyglet.font.load('Luxi Sans', 14)
> --- > SEGMENTATION FAULT
>
> - SNIPPET 2
> import pyglet
> window = pyglet.window.Window()
> label = pyglet.text.Label('Hello, world',
>font_name='Luxi Sans',
>font_size=36,
>x=window.width//2,
>y=window.height//2,
>anchor_x='center',
>anchor_y='center')
> --- > SEGMENTATION FAULT
>
> It seems that the problem arises already at the stage of font loading.
> I am not at all a python expert, perhaps somebody can suggest a
> way to narrow down the problem?
I'm not a coder, but possibly this may help:
http://pyglet.org/doc/api/index.html
Then look at pyglet.font and pyglet.font.base for example purposes.
> Here is some more information on my system reported by a routine
> included in a python package (PsychoPy) I am trying to use:
>
> System info:
> FreeBSD-8.0-RELEASE-p2-amd64-64bit-ELF
>
> Python info
> /usr/local/bin/python
> 2.6.4 (r264:75706, Mar 23 2010, 15:20:14)
> [GCC 4.2.1 20070719 [FreeBSD]]
> numpy 1.4.0
> scipy 0.7.1
> matplotlib 0.99.1
> pyglet 1.1.2
> PsychoPy 1.60.03
>
> OpenGL info:
> vendor: NVIDIA Corporation
> rendering engine: GeForce 9500 GT/PCI/SSE2
> OpenGL version: 3.2.0 NVIDIA 195.36.15
> (Selected) Extensions:
>True GL_ARB_multitexture
>True GL_EXT_framebuffer_object
>True GL_ARB_fragment_program
>True GL_ARB_shader_objects
>True GL_ARB_vertex_shader
>True GL_ARB_texture_non_power_of_two
>True GL_ARB_texture_float
To drive a wedge you might consider as an experiment temporarily replacing
the Nvidia driver in xorg.cong with the nv driver. If same problem, it may
be confirming the problem is not an interaction with a video display driver
but rather the Python coding itself. Notice the different approach in the
doc example(s).
I'm not really a coder and don't know a whole lot about Python, but since
this seems to have been a problem to you for a while now I thought maybe I'd
toss out my ideas. YMMV :-)
-Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: downgrade php5
doug schmidt wrote: > After upgrading to php 5.3.2, we have a few in house applications that > broke and our developers will not be able to work this out for at > least another week or so, so I need to downgrade back to 5.2.12 in the > mean time. > > I've used portdowngrade lang/php5 and lang/php5-extensions, during > make install of php5-extensions it fails on php5-filter > [snip] > > Stop in /usr/ports/lang/php5-extensions. > > Since some ports have been removed as they are bundled with 5.3.2, how > can I get this downgraded properly. (devel/php5-pcre is no longer > in the ports tree). > I feel for you, as I am slogging my way through the PHP upgrade myself. I've been fairly lucky so far as most of it I've been able to fairly easily get by. Only outstanding item for me at this point in time is php5_pdo-mysql is horribly broken [Again]. It has been a long time since I've had to do anything like this, but I believe what you will probably end up needing to do is to csup the ports tree back one step to the earlier date/state. Then build the php5-pcre as it was when it was before. Not entirely sure about how big a mess that might be in attempting to properly confuse portdowngrade. In the past when I've had trouble of this nature I step in and just build/install whatever ports are problematic manually by hand and bypass using the portupgrade tools. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Default labeling and space for rebuilding the kernel.
Leon Meßner wrote: > Hi, > > if one uses the default labeling with current installer it is not > possible to rebuild the kernel (GENERIC). It fails on installing the > wlan.ko. > > Isn't that wrong somehow ? > > ===> wi (install) > install -o root -g wheel -m 555 if_wi.ko /boot/kernel > install -o root -g wheel -m 555 if_wi.ko.symbols /boot/kernel > ===> wlan (install) > install -o root -g wheel -m 555 wlan.ko /boot/kernel > install -o root -g wheel -m 555 wlan.ko.symbols /boot/kernel > > /: write failed, filesystem is full > install: /boot/kernel/wlan.ko.symbols: No space left on device [snip] There has been some discussion lately about possibly changing the defaults. If you become faced with having to reinstall jot down your current partition sizes and adjust manually making / larger. Since it is full, if you intend to try and recover it will entail deleting something. This could get tricky, especially if the new 'kernel' space is what filled up. This would presuppose that the kernel.old area was already written out successfully. If the machine will not boot successfully with the new kernel it is imperative that kernel.old still be healthy in order to recover. However, if the new kernel does actually boot, with the result being that some modules are missing you may be able to delete the kernel.old in order to buy space. Messing around with this can potentially be problematic, for obvious reasons. A strong 'YMMV' is indicated here. If you can get past that, you may be able to mitigate the / being too small. Place STRIP= -s into /etc/make.conf and WITHOUT_PROFILE= true into /etc/src.conf. The con of this is that you lose some debugging ability. The pro is new kernels will now fit. I have two servers set up this way at home, and one uses 91MB while the other uses 93MB of space. The 91MB one only has a / of 200MB total, and is nearly half empty. Allows for rebuilding and installing a new kernel without running out of space. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [ HEADS UP ] Ports unstable for the next 10 days
Ion-Mihai Tetcu wrote: > Hi, > > > As announced before, a few big commits, that touch some thousands ports > are being done: png, curl, x11, gnome, kde4. The target ETA is 6-7 > April. > > The first one was done, update of graphics/png (including a shared lib > version bump), with about 5000 ports affected. > > We do _NOT_ recommend updating ports until this commits are all done, > and the problems are fixed, except if you want to help testing / fixing. > > Before reporting failures, please take a look at ports@ list, and > http://qat.tecnik93.com/index.php?action=failed_buildports&sort=last_built > to find out if the problem hasn't already been reported or even fixed. > We also have two incremental builds on Pointy to catch the problems. > > > Thank you, > > With hat: portmgr@ > Thank you very much for this notification. It surely is nice to know this. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Enough Is Enough
Programmer In Training wrote: [snip] > > When jpeg-x (not a typo) is built, the port needs to be automatically > looking forward to see what all depends on it (and if anything depends > on that) and possibly asking the user if they want to upgrade all those > programs to ensure they link to the proper version of jpeg at all times. > Or they could all statically compile in jpeg support (as I assume FF > does because I can still see jpegs in the file upload preview pane) so > this is never an issue at all. I am currently able to manipulate any > jpeg at all (and now unable to use an increasing number of apps) which > is crippling my ability to edit images for any use. > So man portupgrade and see what the -r and -R switches do. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mysql can't running
Michael Powell wrote: > m.anis wrote: > >> Please help, mysql can't running >> i had installed it and using phpmyadmin >> when i check /etc/rc.d/mysql-server status ^ This indicates to me that you just unzipped a tarball and did ./configure && make && make install. This is not how you install software on FreeBSD. Please read the pertinent sections of the Handbook to learn how to install software. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: delete directory
Aiza wrote: > This directory named empty has read/exec permissions. > How do I delete it? > > # /usr/jails/newjail/var >ls -l > total 2 > dr-xr-xr-x 2 root wheel 512 Nov 21 22:53 empty > # /usr/jails/newjail/var >cd empty > # /usr/jails/newjail/var/empty >ls -l > total 0 > # /usr/jails/newjail/var/empty >cd .. > # /usr/jails/newjail/var >rmdir empty > rmdir: empty: Operation not permitted > # /usr/jails/newjail/var >rm -rf empty > rm: empty: Operation not permitted > # /usr/jails/newjail/var >chmod 777 empty > chmod: empty: Operation not permitted Usually when I see this I think flags are set. See man chflags. Used to be it was something like chflags -R noschg , then you could do the usual rm -rf once the immutable flag was unset. Don't know if has changed. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mysql can't running
m.anis wrote: > Please help, mysql can't running > i had installed it and using phpmyadmin > when i check /etc/rc.d/mysql-server status > it says mysql is not running phpMyAdmin will not work until you have configured config.inc.php correctly. > when i tried /usr/local/bin/mysqld_safe & > startting mysqld daemon with database from /var/db/mysql > STOPPING server from pid file /var/db/mysql/.pid > 100323 22:09:46 mysqld ended This is not the correct method to start mysql. You will need to place mysql_enable="YES" into /etc/rc.conf for the startup scripts to work properly. It will also require typing the entire path to the startup script on the command line as well, such as: /usr/local/etc/rc.d/mysql-server start. Or stop, or restart, as you may need. This should occur automatically when booting the machine and this command line is only necessary should you desire to start, stop, or restart without a reboot. Since it said it was 'STOPPING' the server above, how do you know it wasn't running? Instead of phpMyAdmin why not simply do a ps -ax? If mysql is running you will see a couple of line such as: 725 v0- I 0:00.01 /bin/sh /usr/local/bin/mysqld_safe --defaults- extra-file=/var/db/mysql/my.cnf --user=my 858 v0- I 0:20.83 /usr/local/libexec/mysqld --defaults-extra- file=/var/db/mysql/my.cnf --basedir=/usr/loc Lines are cut and word-wrapped, but you get the idea. More information may be gleaned from /var/db/mysql/.err, this is the mysql error log. Determine properly first whether mysql is actually running, or not. The installation procedure (if done properly, and NOT just simply unzipping a tarball somewhere and doing ./configure && make && make install, e.g either using the ports building or package installing process) will also create a mysql user and group entry. The mysql subdirectory and all files under it should be owned by this user:group, e.g.: mysql:mysql. If you did NOT use the ports or package install process, just stop, back up the train and remove whatever you did. Start over and use the ports or package install procedure. The config file is named my.cnf and lives in /usr/local/etc. MySQL will ignore this file if it is world writable. It should fall back to using one located elsewhere if it can locate one. Not sure as I don't believe I've ever attempted starting MySQL with no my.cnf at all, but I believe it may start whether this file is present, or not. Could be wrong about that. If you should find that it is actually running but you are having difficulty communicating with it you may need to do an initial configuration to it to allow logins. Initially when first installed there is no root password and the first step involves setting a password and setting up some basic grant permissions. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Also have a dead box [ WAS: Re: OT: dead box ]
Corey John Bukolt wrote: > On Sun, 21 Mar 2010 11:23:34 + (06:23 CDT) Chris Whitehouse wrote: >> When you press the power button does the cpu fan or the power supply fan >> spin for a moment then stop? That's a sign that something on or plugged >> in to the motherboard has blown. Unplug things and test again. >> >> Chris > > Just a few days ago, I was helping a friend build a system (with all > brand new components, I might add) and we had this very problem. After > sticking in the CPU and RAM and hooking up and turning on the PSU, the > green LED on the motherboard turns on. However, the second the power > button is pressed, everything flashes for a second, then turns back off. > The green LED on the motherboard also remains on. The only way to get > it to flash again is to turn off the PSU, wait, then turn it back on. > We tried re-seating everything, to no avail. > > Reading this thread, someone else mentioned beep codes and that if there > were none, it's most likely a fried motherboard. > > Can anyone else confirm this? > Beep codes may be available, but the nature will depend upon the manufacturer and the BIOS. Different manufacturers will produce different products. In the bad old days the most common beep codes were designed to indicate a video BIOS did not initialize, and then the main area of codes indicated something wrong in the memory subsystem. Pretty much if they made it past these two points the board would boot. And, of course, you need a speaker hooked up which I commonly don't because I don't want any beeps. One thing to be aware of with regard to modern day motherboards and power supplies. I don't recall the exact standards nomenclature, but they are spelled out in a spec. Modern day motherboards will have a main power connector with either 20 or 24 pins. Some are wired so that a 20 pin power supply cable can only go into some of the pins of a 24 pin connector, leaving 4 open. Some power supplies have a split cable which has a 20 pin and a 4 pin that can be hooked together and will occupy all 24 pins of a 24 pin connector. In either case, there is also another second power connector which is usually fairly close nearby to the CPU socket. With slightly older boards this will be a 4 pin and newer boards it will be an 8 pin. On older power supplies there may be only one 4 pin cable designed to plug into this connector. Newer models will usually have a cable that splits into two 4 pin plugs, so as to be able to plug both into an 8 pin socket while retaining backwards compatibility with the older 4 pin boards. This second connector goes to a high current 12volt rail within the power supply and drives all those 'multi-phase' regulators near the CPU. One thing that is consistent is motherboards will not even attempt to boot if this second power cable is not connected or cannot supply sufficient amps. Some power supplies may even beep or have an LED that flashes red. Overlook this and the board will never boot. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ezjail
Mark Shroyer wrote: > On 3/21/2010 1:10 AM, Aiza wrote: >> I don't have sources installed on my system. Just use the binary >> Freebsd-update function. At new releases I do a clean install. >> I only have a single public IP address. >> >> Now I would like to play with jails. One for postfix, apache, and ftp. >> My reading of EZJAIL and the jails section of the handbook lead me to >> believe I need a unique IP address for each jail. Is that correct? > > Yes. But if you have only one public IP address, you can give the jail > a loopback interface with an address in 127.0.0/24 or one of the RFC > 1918 private blocks (there's some debate as to which is the more > "correct" type of address to use, but either will work), then use NAT if > you need your jail to be able to access the Internet. > > If it helps you to reason about this, keep in mind that your jail does > *not* have its own virtualized network stack, like with Solaris Zones > for instance. The best way to think about your jails is as a group of > processes running on the same operating system as the host, just with > the restriction that (among other things) they can only communicate with > the outside world using a limited subset of the IP addresses available > to non-jailed processes. > You might find the below interesting. Only just begun reading/studying it myself. http://www.freebsd.org/releases/8.0R/relnotes-detailed.html#KERNEL [snip] -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: How do I fix the broken python26 port in 7.2-RELEASE ?
George Sanders wrote: > > >> Virgin 7.2-RELEASE install. >> >> I run: >> >> csup -h cvsup4.freebsd.org -i ports/lang/python26 -g -L 2 >> /usr/share/examples/cvsup/ports-supfile > >> >> and now I have a /usr/ports/lang/python26/distinfo that looks like: >> >> MD5 (python/Python-2.6.4.tgz) = 17dcac33e4f3adb69a57c2607b6de246 >> SHA256 (python/Python-2.6.4.tgz) = >> 1a25a47506e4165704cfe2b07c0a064b0b5762a2d18b8fbdad5af688aeacd252 SIZE >> (python/Python-2.6.4.tgz) = 13322131 >> >> This looks like mine. >> >> Perfect. I'll just do a 'make install' and ... >> >> # make install >> ===> Vulnerability check disabled, database not found >> ===> Found saved configuration for python26-2.6.4 >> => Python-2.6.1.tgz is not in /usr/ports/lang/python26/distinfo. >> => Either /usr/ports/lang/python26/distinfo is out of date, or >> => Python-2.6.1.tgz is spelled incorrectly. >> *** Error code 1 >> >> This is the wrong distfile. > > > Ok, but as you can see from the paste above, I _do_ have the right > distfile in my /ports/lang/python26 directory. > > So where is it getting this wrong distfile from, and why is it using it ? > > I am NOT csup'ing and installing the port all in one operation - I am > doing two distinct things: > > 1. csup ONLY the python26 port And by doing this and not refreshing the entire ports tree you are trying to build with an out of date /usr/ports/Mk. With other ports which have dependencies this would become apparent much quicker. Since python26 does not, it would seem the bsd.python.mk thinks you should be trying to build python 2.6.1. > 2. make install the python26 port > > Why is this rocket science ? > Dunno - works for me. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NAT overflow
Anton wrote: > >Hello everyone, > >I'm kind of noob in FreeBSD particularily, and in Unix systems at all >:- ). But, I've already mastered an router on freebsd 7.2, which >worked fine u ntil I installed their MySQL with huge database. > >Now, once a day, I have a problem - users do not have internet on >their computers, and I could not connect to Microsoft Windows server >with RDP fro m outside, but I could login via ssh on router. After >rebbot - everything b ecome fine, everything works good and I have >no problems, until next overflow. > [snip] It is unclear whether or how MySQL is involved with NAT. If it is somehow being used to store NAT session data it might be a possibility. If such is the case all recent MySQL versions by default time out an idle connection, and unless the client detects this and reconnects automatically it is a problem. You can extend the idle delay window to its maximum by placing wait_timeout = 31536000 after the other contents of the global section (will have [mysqld] at the top) of your my.cnf. Even this will eventually drop a connection if idle for longer than this period, but it is as long as you can configure so you hope something pings the database before this expires. As far as the NAT is concerned itself, an overflow can happen from not enough memory in the pool to contain all the session data for the volume of traffic you experience through the router. This should result in dropped connections which then become automatically reestablished very soon after. It should not necessarily cause all traffic to cease once a day. The NAT pool and memory resources, as well as session time out values are tunable. However, it is not clear which NAT and firewall solution you are using, so it is difficult to provide any insight until we know the solution we are discussing. I have used all three over the years, but have used pf long enough now that what I recall from ipfw and ipfilter days is rusty. Others on this list are more informed than myself as well, so when we know specifically what NAT you are using and more details of the problem maybe more help will pop up. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: How do I fix the broken python26 port in 7.2-RELEASE ?
George Sanders wrote: > Virgin 7.2-RELEASE install. > > I run: > > csup -h cvsup4.freebsd.org -i ports/lang/python26 -g -L 2 > /usr/share/examples/cvsup/ports-supfile > and now I have a /usr/ports/lang/python26/distinfo that looks like: > > MD5 (python/Python-2.6.4.tgz) = 17dcac33e4f3adb69a57c2607b6de246 > SHA256 (python/Python-2.6.4.tgz) = > 1a25a47506e4165704cfe2b07c0a064b0b5762a2d18b8fbdad5af688aeacd252 SIZE > (python/Python-2.6.4.tgz) = 13322131 This looks like mine. > Perfect. I'll just do a 'make install' and ... > > # make install > ===> Vulnerability check disabled, database not found > ===> Found saved configuration for python26-2.6.4 > => Python-2.6.1.tgz is not in /usr/ports/lang/python26/distinfo. This is the wrong distfile. > => Either /usr/ports/lang/python26/distinfo is out of date, or > => Python-2.6.1.tgz is spelled incorrectly. > *** Error code 1 > > Stop in /usr/ports/lang/python26. > *** Error code 1 > > Stop in /usr/ports/lang/python26. > > > I have no idea how to make this work. I grepped everywhere for both > "Python-2.6.1.tgz" and "python26-2.6.4" in an attempt to change them by > hand, but I cannot find a single file in my filesystem that contains those > strings, so I have no idea where the ports tree is getting this > information. > > This was not an odd or non-standard operation - what am I doing wrong ? > I believe something in your juxtaposition of commands in your command line above [near beginning of post] has produced an out of order and munged path. I haven't built the python26 port anytime recently, but have several django related things running fine under it. What I do is csup the ports tree by itself (not trying to do it at the same time on the same command line as the build). I keep my csup housekeeping and supfiles in /usr/sup so I just cd /usr/sup and csup -L 2 ports where my 'ports' file simply contains: *default host=cvsup.nl.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix compress ports-all After the ports tree refresh is finished then I install software by changing to the appropriate port directory and do the usual make && make install && make clean dance. I also use portupgrade so there are additional embellishments for use in an update/upgrade scenario. Try separating the steps, ala do the ports tree refresh to completion first, then attempt to install the port. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD Support Cycle
mailinglist wrote: > I'm possibly considering building a FreeBSD based NAS to provide NFS > storage for vSphere in a production environment. I would use FreeBSD-8, > amd64 variety. What is the expected EOS & EOL dates (end of support/end > of life) for FreeBSD 8? I'm not sure if the EOL question matters for an > open source OS, but basically I'm just asking at what point in time would > there no longer be security updates and bug fixes made to the > OS? http://security.freebsd.org/#sup Of course, possibly subject to change or update. Usually any new additions of changes are reported in various @announce mailing lists. The security announce list will report on specifically the secure patch support question. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Hi - identifying cause of crash - a how to please
David Southwell wrote: > Hi > > I have a specific situation which causes a system crash on freebsd 7.2 p3 > amd64 on intel quad core. Can someone teach me how to trace the cause? > > The crash is repeatable in the following circumstances: > > > (a) User logs in > (b) % startx > (c) kde4 loads and works the session > (d) user logs out x session terminates. > (e) user attempts to start a new x session with: > (f) % startx > (g) system crashes immediately > > System requires rebooting to single user mode. Run fsck -y and then go > multiuser. Whereupon the cycle can be repeated. > > > This event did not occur until kde was upgraded to kde 4.3.5. > > The video card is a winfast PX7800GT providing openGL with dual DVI. The > crash problem was not present before upgrading to 3.4.5 so whilst not > ruling out the card I am not assuming it is the video card. > > It would be helpful if the procedure could be identified clearly. I will > post the results available on the web so someone who knows how to > interpret them could take a look. > > Finally should I be asking this question on another maillist? > This is a good place to start, and if someone knows a better spot it will probably be indicated. I can't give you an in depth response, but maybe something to start with. The Kernel Debugging section of the Developer's Handbook may serve as an introduction to a few basics: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ You can also start right away by examining the .xsession-errors file you will find in the users home directory. Also, in /var/log look for the Xorg.0.log and Xorg.0.log.old. After restarting from a crash, if you startx the first one will only contain info on that startup; the second one (.old) may contain some info on what happened at the time of the previous crash, if it is indeed the X server crashing. Sometimes any errors to stdout may appear in /var/log/messages. Sometimes there may be informative error messages present which can be Googled, and other times nothing useful. The same with the .xsession-errors file - it usually contains information relevant to the applications which were running on top of X. If you are running the nvidia driver and see some evidence that it may be responsible for the crash, you could try substituting the nv driver as a test. This might help isolate the problem to the nvidia driver. But where to go from here is a good question. Sometimes if there is some problem wrt the nvidia driver after some kind of upgrade doing a make, make deinstall, and make reinstall of the nvidia driver port occasionally fixes something, but this is a long shot. Nvidia also has a web forum you might hunt around in. Also, if you are doing startx to start KDE with a .xinitrc file in the users home dir (with startkde in here), try it without so the default TWM window manager comes up instead of KDE. Then do the restart test and see if it crashes. This is a good way to separate the problem from being X related and/or KDE related. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: left over restore file restoresymtable
Aiza wrote: > The man for restore says this. > > Note that restore leaves a file restoresymtable in the root > directory to pass information between incremental restore passes. > This file should be removed when the last incremental has been restored. > > What root directory is this talking about? > > If system is booted from cd or dvd then this file can not be written to > /root of the booted system. > > Does this message really mean its written to /root of the just restored > file system / > This file is written when a backup is restored. In order for restore to operate it must write. The root it is talking about is the root of whatever file system you are restoring. For example, let's say you backed up /usr (or even /dev/ad0s1d, etc). When you restore that /usr the restoresymtable file will be at the root of /usr. Same for any other partition. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Limiting Port
Alex Terente wrote: > Hi, > > I have a problem with my FreeBSD system, i have installed a gameserver on > it and after a period of time, the port 11002 (login port) is closed. What > i can do to resolve this? > Two things spring to mind at first, possibly a way to get started. First, establish that it is not the game server relinquishing the port. This is unlikely but it ought to get eliminated from consideration. sockstat -4l will tell you what is listening to which ports. Next time it gets "closed" take a quick look at this and ensure the game server is actually still listening to this port. If it is not it is most likely a configuration detail relevant to the game server. Second, this sounds a lot like a NAT session timing out from inactivity. If such a situation should be the case it is possible to design a rule specific so the ports' traffic can bypass NAT and run "straight-through". If the first thingy from above gets eliminated this is where I'd look next. As to exactly how you would go about tailoring such a rule would depend upon the syntax of whichever firewall you are using. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Should root partition be first partition?
b. f. wrote: > On 2/8/10, Jerry McAllister wrote: >> On Mon, Feb 08, 2010 at 02:37:30PM -0500, b. f. wrote: [snip] >>> If you're laying out a new disk, you may as well take a few minutes >>> and get the most out of it, even if you're not going to invest in a >>> lot of new hardware. >> >> The system nowdays does all that figuring for you and manages >> boundaries reasonably. >> >> jerry >> > > That does not seem to be the conclusion of those who contributed to > the thread I cited, although "reasonably" is open to interpretation. This will become more critical with the upcoming transition from 512K to 4K sector size. Indeed, I believe it was initial investigations for implementation of this and/with comparison against other OS methods. The large performance differences witnessed led to a deeper, more retrospective look at current approaches based on 512K sectors as well. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: amd64: Fatal Trap 12 in high load situations
ms80 wrote: [snip] > > Thank you for your reply. > I'm using two of this: OCZ3P1333LVAM4GK > (OCZ DDR3 AMD Edition, rated for 1333MHz at 1.65V). My Board is rated for > 1066 - 1600 MHz memory, and neither the website nor the manual say > anything about limitations with memory. Anyway: I didn't overclock cpu or > memory. I have stability and long life in mind, so I try to keep the > hardware cool. During testing I underclocked the memory with 1066 and 800 > MHz which didn't help: The machine crashes anyway. The only thing to note > is that by default the board tries to set 1.5V DDR3 Voltage which is > wrong, you have to set it to 1.65V manually. > > A faulty piece of hardware was the first thing I suspected and I tested > among other things the memory with memtest86+. This runs fine for 4 > passes, without any error. As far as I can tell, my memory subsystem is > ok. > Poking around in the OCZ forum for something I thought I recalled seeing somewhere before. I had seen reports that this board might be touchy about 1.65v memory. As far as the consensus goes with the small sampling I looked at, it seemed that 1.63 or 1.64 vdc was the sweet spot. Some claims are that it didn't want to work at anything either above or below this range. My RAM is OCZ3BE1600C8LV4GK (anything with BE or AM in the part number is designed specifically for AM3). I thought it was 1.5v, but since I didn't remember for certain I checked and it shows a spec for 1.65v. However, I rebooted so I could look at the CMOS/BIOS stuff and I have the System Voltage Control section set for "AUTO" for all. Then I looked in the "PC Health Status" page and on the "DDR3 1.5V" line it was only reading 1.600v. There seems to be a general feeling the newer AMD processors don't much care for higher memory voltages. Try lowering your voltages and see if it helps. I am successfully using this board with the CPU clock set at 240MHz, which with the x14 multiplier results in 3.36GHz operation. The Hypertransport and FSB bus speeds are 2400MHz and the memory is running at 1599MHz at the x6.66 multiplier. When I get the RAM up to 1680MHz is where I can get it to freeze. As long as I don't do that it is totally stable. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: amd64: Fatal Trap 12 in high load situations
ms80 wrote: > Hi > > I have a problem installing / upgrading FreeBSD 8.0-release on a new > machine. > > The computers specs are: > > cpu: AMD Phenom II X4 > board: Gigabyte MA790GPT-UD3H > ram: 4x2GBytes DDR3/1333 > hdd: 2xMaxtor STM31000528AS > nic: 4x Intel(R) PRO/1000 [snip] > > > So here are my questions: > 1. Are there any known caveats or quirks regarding my hardware? > 2. What can I do to further investigate this issue > 3. Not fully on topic but might be related: The buildsystem recognizes my > cpu as "686 class cpu" wich is wrong. Are there any switches I can set in > make.conf to have 'make' use the correct values? Currently I'm using a > blank make.conf, meaning it is not present (as it is by default on a fresh > installed system). > [snip] I am using this motherboard with an AMD x4 630 Propus cpu and 4G Ram (2x2GB). I have done a basic overclock to 3.36GHz with the ram running at 1600MHz. This is my KDE4 desktop machine running FreeBSD 8 and all ports currently up to date. When selecting the RAM to put on this motherboard you should have consulted the list from Gigabyte for approved memory and chosen very carefully. The memory I actually have was not an exact line item from the list, but it was something extremely close and which was designed and manufactured for use with an AM3 socket motherboard. You will notice that some RAM today is designed for Intel P55 chipsets and Lynnfield processors while other RAM is designed specifically for AM3/AM2 socket use. It is probably not a good idea to disregard this during selection, e.g. memory not specifically meant for AM3 socket mobos may not function correctly. I also seem to recall seeing somewhere that this motherboard acquires limitations in overclocking when all 4 sockets are filled and the best overclocking results when only 2 sockets are in use. I am only using 2 sockets in a 2x2GB arrangement for 4GB RAM total. If you are not overclocking and have all 4 sockets filled you may not be able to go above 1066MHz memory multiplier. With only 2 sockets populated 1333MHz should be attainable. I believe your problem centers around memory. It may not be designed for AM3 socket and/or may not be able to handle a higher memory multiplier. When I first put this motherboard in I attempted to boot from an already installed OS with the memory multiplier set too high and saw numerous examples similar to what you are describing. Since I had bought 1600MHz memory I mistakenly set the multiplier too high. When I set it back to 1333MHz everything was fine. Either the memory multiplier is set too high for your RAM or it is just the wrong RAM to begin with. As far as make.conf goes I use: CPUTYPE?= k8 -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: GCC broken?
Bernt Hansson wrote: > Hello listreaders! > > I'm trying to build qt4-webkit 4.6.1 > But it fails or i fail to build it. Is it GCC? > The machine is not overheating an has a low load, it's my desktop. > I just did this upgrade a few days to maybe a week ago with no problems. > > Stop in /usr/home/user/disk2/ports/www/qt4-webkit. Maybe it doesn't like your non-standard ports location? Maybe try /usr/ports? > ** Command failed [exit code 1]: /usr/bin/script -qa > /tmp/portupgrade20100202-28371-iomdra-0 env UPGRADE_TOOL=portupgrade > UPGRADE_PORT=qt4-webkit-4.5.2 UPGRADE_PORT_VER=4.5.2 make > ** Fix the problem and try again. > ---> Build of www/qt4-webkit ended at: Tue, 02 Feb 2010 09:51:56 +0100 > (consumed 00:11:53) > ---> Upgrade of www/qt4-webkit ended at: Tue, 02 Feb 2010 09:51:56 > +0100 (consumed 00:11:54) > ---> ** Upgrade tasks 5: 0 done, 0 ignored, 0 skipped and 3 failed > ---> Skipping 'devel/qt4-linguist' (qt4-linguist-4.5.3) because a > requisite package 'qt4-webkit-4.5.2' (www/qt4-webkit) failed (specify -k > to force) Since mine upgraded without problem I suspect there is nothing wrong with GCC, unless somehow it got broken on your machine. Make buildworld and make installworld will rebuild it. At any rate, I just ran a build on the www/qt4-webkit-4.6.1 port here as a test and it is building fine for me. Another possibility is hardware, with the front runner being memory. If the process stops at random locations each time it is most likely hardware related. A hardware problem causing such a thing would also most likely show itself during a make buildworld as well. If it stops at the same place with the same error every time it is probably software related. And I suspect your non-standard ports tree location. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mysql silently failing to start - suggestions?
John wrote: > If this isn't the right list - if I should try another let me know - > but since this is the mysql-server-5.4.2 package, and since you > folks have been so helpful, I thought I'd give it a go. > > Anyway, the system is 8.0-RELEASE and that package is installed, > and I can't start the server. Not only can I not start the server, > but it's not giving me a clue. I can't find anything anywhere. > Not in /var/log/messages, not anywhere. When I run > /usr/local/etc/rc.d/mysqlserver start > it says "Starting mysql.", pauses for several seconds (I don't see > anything go by in "top") and then the script exits. At that point, > one would expect, there's no /tmp/mysql.sock, there's nothing > in messages or anywhere else. With nothing to go on, well, I don't > know where to start. Any suggestions? First is there a mysql_enable="YES" line in /etc/rc.conf? The rc subr startup system requires it and also the complete path as you did type above. Although since it is mysql-server and you got a response I'll assume the above is just a typo here in this mail. If you have changed the location of the database files this variable will need setting in /etc/rc.conf as well. The default is /var/db/mysql. Notice this directory should be owned by the mysql:mysql user/group combo. This will allow for the writing of the .pid file. There will also be a .err file which is the log you need to look at. If these files are not present it is either not getting that far in the startup, or there is a permissions problem. The normal location of the socket is /tmp, which should be permissions 1777 (sticky bit set). You do have a line setting the hostname of the machine in /etc/rc.conf too, right? Such as hostname="testbed.test.zip" for my local dev server at home. This should be resolvable either by DNS or a hosts file. Also, be aware that the location of the my.cnf file is now /usr/local/etc, although should this be missing it should still look for it in /var/db/mysql as a fallback. If this file is world writable MySQL will ignore it. The establishment of the mysql user and group should have occurred as part of the port installation. I use ports and not packages, as well as the older version of 5.1.42 so I cannot speak to the efficacy of installing a package of 5.4.x. Perhaps a package problem? Try installing the 5.1.42 port using the ports system instead is one possibility if such may be the case. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Weird build errors only on 3rd core of quad core CPU
Pieter de Goeje wrote: > I am suspecting a broken CPU, but am not sure. > > These commands: > cd /usr/ports/sysutils/hal > cpuset -c -l 2 make > > Will always result in errors, for example this one: > > gmake: *** No rule to make target `...@maintainer_mode_true@', needed by > `config.h.in'. Stop. > *** Error code 1 > > Sometimes the error occurs in a different place. When I check the input > files, they are indeed broken. Gcc stops because of syntax errors for > example. > > The configure process always completes, but apparently it creates broken > files. When I run make on any other core, it always completes > successfully: cpuset -c -l 0,1,3 make > > I've checked with script that the output of the build process is exactly > the same, up until the error occurs. I've also tried to run cpuburn on > that core, but it didn't find any problem. It's really weird that system > is otherwise very stable. > > What do you guys think the problem is? > > CPU is AMD Athlon II X4 620. Running FreeBSD 8-STABLE/amd64. I've also > tried -CURRENT, but it didn't help. > As a test I just ran these two commands on my Athlon II 630 here, but running FreeBSD 8.0-RELEASE-p2 amd64 build. The make process ran directly to completion with no error. With overclocking too. Tried 4 runs, on each core. I'm not sure I recall all the details correctly without checking, but I thought there were some early samples or generations of these processors that were not the same as the final production releases. Something to do with being Phenom cores that had L3 cache disabled, being released as early engineering samples but the die of the final products is different with no L3 cache present from manufacturing. I'd check into the stepping and if it turns out not to be a final version get whoever you bought it from to replace it. It may not be the core itself, but bad L1/L2 cache. It's either that or the only other difference is you're running stable, and I'm not. But I'd suspect bad cache spots in L1/L2. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Unable to find device node for /dev/ad0s1b in /dev!
insecur...@malandrines.net wrote: > Unable to find device node for /dev/ad0s1b in /dev! > > help me please See my reply to message: "SunFire x2100 fails" -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: SunFire X2100 fails
Julian Fagir wrote: > Hello, > > I recently got a SunFire X2100 to play with (first version, not M2). > Linux (Debian) and 7.2-RELEASE works without problems, just installs > straight-away and runs fine (currently 31 days uptime). > But 8.0-RELEASE does not work, neither when being upgraded nor when > installing from CD or memstick. > > The problem is: The kernel does not recognize the slices and partitions. > When installing it, the installer shows me a single slice on each of the > two hard disks though there are more. It also shows a warning about a > GPT-label, no matter whether there is a GPT or MBR on it. > After reslicing and -partitioning them, the installer fails when creating > a filesystem on them, saying the devices (in this case the partitions) are > not configured. [snip] This sounds very familiar to something I just went through. A drive went up in smoke and the spare I pulled from the shelf had 6.2 on it. The 8 Release install would fail, something to do with either the partition table and/or labels from the earlier being invisible to the new and thus could not be written to. Boot a LiveFS CD, then at a root prompt do: sysctl kern.geom.debugflags=16 and: dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 where x equals your drive number. Probably should only do this before a fresh install and NOT on a system with data you want to keep. The exact error I received whilst trying to install 8 in sysinstall was this: "Unable to find device node for /dev/ad4s1b in /dev! The creation of filesystems will be aborted." Then pressing "OK" brings this: "Couldn't make filesystems properly. Aborting." -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Missing all ttyv* device nodes after upgrade 7.0 -> 7.2
Morgan Wesström wrote: >>> These dmesg lines are from another 7.2 machine and I am missing them >>> from the output of this newly upgraded machine: >>> >>> sc0: at flags 0x100 on isa0 >>> sc0: VGA <16 virtual consoles, flags=0x300> >>> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on >>> isa0 [snip] > > > Thanks for your answer Mike. The system is actually an old Celeron on an > Intel i865 based mainboard so the hardware should be pretty well > supported I guess and after all - it did work with 7.0. The machine is > only used as a router so the lack of virtual terminals aren't critical > but I still would like to solve it. I will have the owner look for a > more recent BIOS and then I'll reinstall the GENERIC kernel before > filing a bug report. Here's a more verbose dmesg snippet that might give > someone a clue: I have an Asus P5P800SE i865 motherboard here with a Pentium D 940 on it. It is currently running 8-Release and does not exhibit this problem. Right now there is still an AGP video card in it. > agp0: on hostb0 > agp0: allocating GATT for aperture of size 128M > vgapci0: mem > 0xf800-0xf8ff,0xe000-0xefff,0xf900-0xf9ff irq 3 > at device 0.0 on pci1 This is an odd IRQ for a video card to come up on, as this is usually reserved for one of the COMM ports. Maybe an IRQ conflict here. > isab0: at device 31.0 on pci0 > isa0: on isab0 > sc: sc0 already exists; skipping it > vga: vga0 already exists; skipping it > isa_probe_children: disabling PnP devices > isa_probe_children: probing non-PnP devices > pmtimer0 on isa0 > sc0: no video adapter found. > sc0: failed to probe on isa0 > vga0: failed to probe on isa0 > atkbdc0: at port 0x60,0x64 on isa0 > vt0: not probed (disabled) > isa_probe_children: probing PnP devices Below is a snippet from mine. You didn't remove device vga from the kernel by any chance? Switching back to GENERIC for a test is probably a good idea as it may remove a variable from the problem. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] The BIOS selection for PnP OS support should be "Off". Irregardless, this looks like botched PnP probing by the BIOS. Only idea comes to mind right away is if you are using a PCI video card instead of AGP there is a BIOS selection which chooses which is initialized first. There is usually also one somewhere about whether to assign an IRQ to the video card. IRQ 3 just looks wrong. Check the mobo manual for slot sharing. A lot of motherboards will do something like share IRQs between the AGP slot and the first PCI slot (and/or others as well), with the sharing usually involving the AGP, the PCI slot, and USB controller(s). There is usually a chart in the manual which shows what is shared and where. I have such a chart in mine. > What is that vt0 (disabled)? Is that related? pciconf reports this: > > pc...@pci0:0:1:0: class=0x060400 card=0x chip=0x25718086 > rev=0x02 hdr=0x01 > vendor = 'Intel Corporation' > device = '82865G/PE/P, 82848P PCI-to-AGP Bridge' > class = bridge > subclass = PCI-PCI > is...@pci0:0:31:0:class=0x060100 card=0x chip=0x24d08086 > rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801EB/ER (ICH5/ICH5R) LPC Interface Bridge' > class = bridge > subclass = PCI-ISA > vgap...@pci0:1:0:0: class=0x03 card=0x2034107d chip=0x022010de > rev=0xa1 hdr=0x00 > vendor = 'Nvidia Corp' > class = display > subclass = VGA This is mine (with AGP video card): vgap...@pci0:1:0:0: class=0x03 card=0x chip=0x00f110de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' device = 'GeForce 6600 GT AGP (NV43+BR02)' class = display subclass = VGA Notice in yours above the 'device' line is missing, > Googling on this turns up a lot of older posts with references to PnP > incompatibilities and ATA but I can't find any info that helps me with > syscons. Funny thing is it worked in 7.0 previously? At first glance this smells like BIOS PnP probing problems, but I think if it were it would have showed itself before. Try GENERIC and see what happens. If it goes away you know where to look. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Missing all ttyv* device nodes after upgrade 7.0 -> 7.2
Morgan Wesström wrote: > Morgan Wesström wrote: >> Morgan Wesström wrote: >>> I obviously did something wrong somewhere but I can't figure out what. >>> All console device nodes /dev/ttyv0 - /dev/ttyvf are missing after I >>> upgraded a machine from 7.0 to 7.2. The serial console node /dev/ttyd0 >>> is there though if that rings a bell. What controls the creation of the >>> console device nodes? Any hints on what I should check? I did deactivate >>> unneeded SCSI-drivers and the like in the GENERIC kernel but the tty >>> related stuff is still there, like: >>> >>> options COMPAT_43TTY# BSD 4.3 TTY compat >>> device sc >>> >> >> I'm also missing /dev/consolectl >> > > These dmesg lines are from another 7.2 machine and I am missing them > from the output of this newly upgraded machine: > > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > > Both devices are in the kernel. What could prevent them from binding? Is it maybe a newer system that has keyboard and mouse set to USB as a default which needs disabling in BIOS? I know a machine I just built I set the keyboard to "Legacy" to use the PS/2 port while the mouse stayed USB. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Errors on UFS Partitions
The-IRC FreeBSD wrote: > Hi, > > I am sorry if I am asking a question that might have been brought up > before I have attempted to research my issue but it has many angles it > might be listed under so please bare with me. > > We have had ongoing problems with UFS Errors on our root partition (and > any additional partition that did not have soft-updates enabled by > default) and we recently had a problem with a secondary drive that housed > home directories completely filled up and then everything locked up due-to > huge CPU and Memory usage because nothing was able to write to the drive > but when the server was rebooted it failed to bootup because of critical > errors on the root partition. A healthy system does not get UFS errors during normal operation. > We have /etc and /usr on the root partition and our home/var partitions > mistakenly do not have soft-updates flag set. > > ::dmesg:: > http://the-irc.com/dmesg > > ::mount:: > /dev/ad4s1a on / (ufs, local) > devfs on /dev (devfs, local, multilabel) > /dev/ad4s1d on /home (ufs, local, with quotas) > /dev/ad4s1e on /tmp (ufs, local, noexec, nosuid, soft-updates) > /dev/ad4s1f on /var (ufs, local) > devfs on /var/named/dev (devfs, local, multilabel) > procfs on /proc (procfs, local) > /dev/ad0s1e on /Backups (ufs, local, soft-updates) > /dev/ad0s1d on /root (ufs, local, soft-updates) [snip] > > To prevent letting these errors go out of control and not beable to fix > the root partition errors without going into singleuser mode and the other > partitions by mounting them with soft-updates flag, does anyone advise > removing everything from the root partition and only leaving the > bootloader and thus moving /etc and /usr (or most of all just /usr) to > it's own partition or do you guys have a better solution. No. Proceeding in directions such as this is a waste of time. > Every partition gets errors over time but if you are unable to correct > them without downtime how are you to correct them before they get out of > control? Probably by not looking for a software solution to a hardware problem. It is not normal for a file system to behave as you describe. Moving partitions around and other such avenues of approach are doomed to failure as they are not addressing the underlying problem. Real server hardware with sophisticated ECC subsystems usually have some BIOS counters which you can check for stats on memory errors. Hard drives fail the most often but either bad memory or drive controller can readily corrupt data. If you have a RAID controller with RAM cache the RAM could be defective. Hardware failure is going to mean downtime. But I'd be looking for a hardware problem, get it fixed, then worry about how to proceed. If you have decent backups from before the system was corrupted you can get back to where you need to be in relatively short order. Not fixing a hardware defect will result in you never getting your server back to normal operation. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: watching WebEx session on FreeBSD
> Matthias Apitz wrote: > >> >> Hello, >> >> Has someone had luck with watching a WebEx session on FreeBSD based >> desktop? As far as I understand, it is somehow Flash and RDP based, i.e. >> some tools like Firefox with flash and a RDP client are required. >> I'm always forced to launch a VM with XP to watch such sessions and it >> would be good for me to overcome this situation. >> OK - I signed up for another 14 day trial, and eventually at some point I always arrive at a page that says: "Support Not Available Meeting Center is not available for your computer's operating system. For information about system requirements, please refer to the FAQ support." I even tried using Konqueror's sending browser ID as IE7 on Win XP. Still ultimately ends up here. So FreeBSD is not a supported OS, also not on their list in the FAQ either. So it seems they have decided specifically to disallow participation by anyone using FreeBSD. I guess they don't consider anyone using FreeBSD to be commercially viable. This sucks, and I will make a complaint when I hunt down their "Feedback" area. As far as I can tell (IMHO) so far is I don't see any reason why it should not work. I have both functional Flash and Java. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: watching WebEx session on FreeBSD
Matthias Apitz wrote: > > Hello, > > Has someone had luck with watching a WebEx session on FreeBSD based > desktop? As far as I understand, it is somehow Flash and RDP based, i.e. > some tools like Firefox with flash and a RDP client are required. > I'm always forced to launch a VM with XP to watch such sessions and it > would be good for me to overcome this situation. > I recently returned to using FreeBSD as a KDE 4 desktop after experimenting with various Linux incantations for a couple of years. I finally got tired of it. I had used KDE for years on FreeBSD, but it was always "the hard way". There may be different rough edges, but I've always been convinced that KDE largely runs better on FreeBSD, especially wrt to 8.0. Instead of a regular install and subsequent lots of time installing stuff this time I wanted to check out PCBSD. There are some things I'm not crazy about but for some reason or another they got Flash 10 working in Firefox right out of the box. I chose not to use their PIB packaging system for installing additional software that is not part of the default. I rebuilt the OS with the make buildworld, etc, dance so my kernel is half the size of theirs and chose to use portupgrade to manage keeping ports in line. Have been steadily installing stuff with ports and so far so good. I installed the beta 3 DVD they have released because I was mainly interested in FreeBSD 8 and the previous non-Beta is 7.x based. I only used it as a launch pad and then took over my own maintenance from there. Now for some reason or another I thought that when I tried the free 14 day test account that it was Java based. I don't know why this stuck in my mind at all. However, I am able to look at their Flash demo just fine. So it is is achievable on FreeBSD. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Converting i386 to amd64
Matthew Seaman wrote: > Michael Powell wrote: >> Greetings everyone: [snip] >> >> Thanks in advance for the wielding of any clue sticks. :-) > > This sort of process /is/ possible, but it is a lot more involved than > you're anticipating. Unless you're the sort of person that likes doing > terribly complicated and risky procedures for the hell of it, you are > going to be better off just starting from scratch and reinstalling using > an AMD64 .iso. It's going to be quicker to reinstall anyhow. > > Cheers, > > Matthew OK, that's what I needed to know. It just didn't seem as if something as complex as a cross build could be handled with just one little "TARGET=xxx". Terrible and complicated for no real gain is not my style. I like KISS. I have done scratch reloads before and can handle it just fine, it's more a time management fork in the road issue. This tells me I can allocate amount of time for a scratch reload as opposed to time for 'terrible and complicated'. It just means more console time instead of coming by once an hour for a few minutes. I'll stick with what I know will work then, and budget my time accordingly. Thanks for the reply! -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Converting i386 to amd64
Greetings everyone: This is probably a pretty dumb question, but it's never really come up for me before. I am at a crossroads with regard to some hardware upgrades, and for a couple of them I have been putting off making the change to 64 bit. These are server boxen with no concerns for desktop use. Is it possible to change an i386 install to amd64 without needing to start from scratch? I was poking around reading some stuff, and ran across this in in /usr/src/Makefile: # If TARGET=machine (e.g. ia64, sparc64, ...) is specified you can # cross build world for other machine types using the buildworld target, # and once the world is built you can cross build a kernel using the # buildkernel target. Does this mean I can achieve the desired effect with "make buildworld TARGET=amd64", et al? It would be a tremendous time-saver for me. Of course I would follow with a portupgrade -fa and rebuild all ports afterward. Thanks in advance for the wielding of any clue sticks. :-) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: Clean PHP 5.2.12 Build Core Dumping
Don O'Neil wrote: > Ok... well, your idea is a good one, but it seems that the port is broken. > > I did a port update, which brought in the latest php build info from > December, but when I run 'make' (without even editing the Makefile to add > my own other modules I need) I get this: If installing with the ports system you shouldn't need to be editing any Makefiles. make config will give you list of options you may select from. Note there is an initial build/install of PHP itself and a second port called php5-extensions which you then install for all the modules. Again, a make config will list all options. No need to mess with Makefiles. > X11BASE is now deprecated. Unset X11BASE in make.conf and try again. > *** Error code 1 > > Not even sure where it's getting that error message from, since I can't > find any reference to X11BASE in any of the files in the package, or in my > env. > > Any ideas? > Try putting WITHOUT_X11=yes into /etc/make.conf. Some PHP modules such as GD try and pull in X dependencies; this will short circuit that. >> -Original Message- [snip] -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Setting root password on mysql 5.4
jaymax wrote: > > Does anyone know how to set root password on a new mysql installation from > the post? This is the very first thing performed on a brand new fresh install. The canonical procedure (and I haven't had to do it in a while so it is possible it may have changed) looks something like this: As root at a '#' prompt do: mysql --user=root mysql This brings up the mysql prompt: mysql>GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost'[press return or enter] at the -> prompt type in the following command: IDENTIFIED BY '' WITH GRANT OPTION; [press return or enter] The above should exit back the mysql> prompt if all went well. This will allow root to login with no password, but only on localhost. If you wish to expand this for the same from any host execute the steps again with the below differences. Otherwise type quit at the mysql> prompt to exit. The main reason the second step may be desirable is to admin from a different box using the MySQLAdminGUI for example. Be warned however!: If this box is accessible by anyone from anywhere it is a security hole as root has NOT yet been assigned a password! And this procedure does NOT assign any password, it only sets the access so you can. mysql>GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' [press return or enter] at the -> prompt type in the following command: IDENTIFIED BY '' WITH GRANT OPTION; [press return or enter] Next at mysql> prompt just type quit to exit. Restart mysql and now root can login with no password. Either use the command line to set the password, or the MySQLAdminGUI in the USERS section. The GUI is simple but I'll leave as an exercise for you to look up the CLI procedure in the MySQL docs should you get this far. You need to follow the above procedure first before you can log in as root in order to change the password. To reiterate: the above does NOT assign a password, it only allows root initial access so he can then set a password. Check out: http://dev.mysql.com/doc/refman/5.1/en/default-privileges.html http://dev.mysql.com/doc/refman/5.1/en/user-account-management.html > Can it be performed after starting the server with > /usr/local/bin/mysqld_safe & > > Or for that matter with > /usr/local/bin/mysql_secure_installation > Sorry but these two are not something I'm really familiar with. If the canonical approach doesn't work, maybe you can try to temporarily start it with neither of these in the mix, set the password, then restart it with these two active again. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: port-MESS with apache22
PJ wrote: > Thought I'd better get more specific: > I rebooted, apache is running. > I deleted the apache2 directories -- > but lo and behold, it is the php5 port that is stubborn and absolutely > insists on creating these directories. > What in Hades is going on? [snip] Don't know if this pertains to or will fix the PHP building problem, but you might try putting USE_APACHE=common22 in /etc/make.conf. There has been change(s) the build process and I have as of yet not taken the time to research them enough to be sure I understand. You can look at: /usr/ports/Mk/bsd.apache.mk for hints. Note the old styles of WITH_APACHE and the like is deprecated. Quote: # Note: Setting USE_APACHE to "yes" is deprecated. It will set # APACHE_PORT to www/apache13 and if WITH_APACHE2 (deprecated too) # is defined, APACHE_PORT will be set to www/apache20 # -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Possible mysql.sock problem | ERROR 2002 (HY000)
jaymax wrote: > > Thanks !!! > Got it resolved after adding > mysql_socket="/usr/tmp/mysql.sock" to the rc.conf file > Removing the /etc/my.cnf file as the aetting were redundant with those > used in the compilation > deinstalling and reinstalling both the server and the client > [snip] The "new" default location for my.cnf as installed by the ports system is now /usr/local/etc, although MySQL will still find it if it is in mysql_dbdir. MySQL startup will skip it if it has world write permissions on it, more specific info is in the docs. I just chmod mine 444 when I'm done with it as it is something I don't change once configured. But if you have two of them the permissions thingy can be the cause of why it skips over and ignores the one you think it should be using. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: geometry does not match label
Michael Powell wrote: [snip] > > You should know that the ad0/ad1 will result in a fairly drastic > performance hit. This is a master/slave arrangement on the same channel. > You really really should get another cable and do the ad0/ad2 arrangement. > And, of course, as soon as I hit the "Send" button it occurred to me this really only applies to a PATA drive set and is meaningless if both drives are SATA. Disregard if using SATA! :-) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: geometry does not match label
Robin Becker wrote: > I'm just setting up a software raid mirror using geom; everything seems to > be working fine and the mirror is slowly synchronizing. > > Because of cabling constraints this is a mirror rather than a duplex (I > haven't used mirror before) so the gm0 components are ad0/ad1 rather than > ad0/ad2. In dmesg I see > .. > GEOM_MIRROR: Device mirror/gm0 launched (1/2). > GEOM_MIRROR: Device gm0: rebuilding provider ad1. > GEOM: mirror/gm0s1: geometry does not match label (16h,63s != 255h,63s). > .. > Trying to mount root from ufs:/dev/mirror/gm0s1a > .. > > anyone know if I should worry about the "geometry does not match label" > message? >From what I understand, no. I've seen this on all my machines at boot up since the recent round of updating. Since the consensus seems to be that it is harmless I've ignored it and have experienced no problem of any kind to date. This is still a "YMMV" thing, but I'd bet you can ignore it too. You should know that the ad0/ad1 will result in a fairly drastic performance hit. This is a master/slave arrangement on the same channel. You really really should get another cable and do the ad0/ad2 arrangement. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: strange find process
Anh Ky Huynh wrote:
> Hi all,
>
> At 2:00 am today, I turned my laptop on and suddenly found a strange
> process:
>
> $ ps xauw | grep find
> ... find -sx ./bin -type f
> ( -perm -u+x -or -perm -g+x -or -perm -o+x )
>( -perm -u+s -or -perm -g+s ) -exec ls -liTd {} +
>
> What is the purpose of this process? If that is a system check then where
> is the log file?
There are some scripts called periodic which execute and perform various
different things depending upon whether it is a daily, weekly, or monthly.
The output will get emailed to root, or redirected to an alias of root.
The above looks strangely enough like a snippet of this activity. The daily
usually runs every morning here at 3AM, the weekly rebuilds the locate and
whatis database something like 4:15AM Saturday morning, and the monthly is
an end of the month count of login activity.
More info can be found in man periodic. There is a periodic.conf in
/etc/defaults, and the scripts themselves live in /etc/periodic and you can
take a look. My bet is you stumbled upon one of the periodic script runs.
-Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: location of discussion of lives
leeoliveshackelf...@surewest.net wrote: > Good morning, dear FreeBSD enthusiast. Can you help me to negotiate the > FreeBSD website? I am trying to find a general discussion about "livefs." > I have not been successful at entering the correct sequence of search > terms to find a general discussion about this topic. I would like to know > what this feature does, and the situation in which a user would wish to > install it. My question would refer to either release 7 or release 8. > Thanks for any and all enlightenment. Yours truly, Lee S. The LiveFS is a bootable CD with a very minimal set of utilities present. It is somewhat comparable to the minimal install, except booting from a CD. You would not necessarily "install it". It is primarily a system admin tool to aid in recovery of a damaged system, or can also be used to initially pre- configure a system in special ways which are not yet included in the standard sysinstall. Such things may be GPT partitioning, setting up drives for ZFS, and the like. It is more of a fixit/rescue tool, and for other advanced sysadmin functions. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: samba3.x - 3.0 won't compile, 3.2 and 3.3 can't be installed
Ewald Jenisch wrote: > Hi, > > For quite some time now I'm trying to get samba 3.x installed on my > FreeBSD 7.2 System. > > The symptoms in short: > > o) 3.0 - doesn't compile > > o) 3.2, 3.3 - can't be installed because of installation dependencies > to samba4-devel-4.0.0.a8_2, talloc-1.3.1 and tdb-1.1.5. > > System: > FreeBSD test.at 7.2-STABLE FreeBSD 7.2-STABLE #8: Mon Dec 7 12:21:59 CET > 2009 r...@test.at:/usr/obj/usr/src/sys/GENERIC amd64 > > > Ports tree is updated and all ports installed up2date. > > Now for the Samba-port(s): Depending on the version of Samba it either > can't be built at all or fails upon installation. > > In detail: > > 1) Samba3.0: > > Bails out during compilation with the following error: > > Compiling locking/locking.c > locking/locking.c: In function 'unparse_share_modes': > locking/locking.c:701: error: invalid operands to binary - > The following command failed: > cc -I. -I/usr/ports/net/samba3/work/samba-3.0.37/source -O -pipe > -DLDAP_DEPRECATED -D_SAMBA_BUILD_=3 -I/usr/local/include > -I/usr/ports/net/samba3/work/samba-3.0.37/source/iniparser/src -Iinclude > -I./include -I. -I. -I./lib/replace -I./lib/talloc -I./tdb/include > -I./libaddns -I./librpc -DHAVE_CONFIG_H -I/usr/local/include > -I/usr/local/include -DLDAP_DEPRECATED > -I/usr/ports/net/samba3/work/samba-3.0.37/source/lib -D_SAMBA_BUILD_=3 > -fPIC -DPIC -c locking/locking.c -o locking/locking.o *** Error code 1 > > Stop in /usr/ports/net/samba3/work/samba-3.0.37/source. > *** Error code 1 > > Stop in /usr/ports/net/samba3. > *** Error code 1 > > Stop in /usr/ports/net/samba3. > > > > 2) Samba3.2: > > $ make install > ===> Installing for samba-3.2.15 > > ===> samba-3.2.15 conflicts with installed package(s): > samba4-devel-4.0.0.a8_2 > talloc-1.3.1 > tdb-1.1.5 > > They install files into the same place. > Please remove them first with pkg_delete(1). > *** Error code 1 > > Stop in /usr/ports/net/samba32. > *** Error code 1 > > Stop in /usr/ports/net/samba32. > $ > > However samba4-devel is needed by (pkg_info -Rx) > evolution-mapi-0.28.1 > gnome2-2.28.1 > libmapi-0.8.2 > so de-installing them is a no-go since I need gnome2 > > > 3) Samba 3.3: > > Similar problems as with samba 3.2 above: > > $ make install > ===> Installing for samba-3.3.9 > > ===> samba-3.3.9 conflicts with installed package(s): > samba4-devel-4.0.0.a8_2 > talloc-1.3.1 > tdb-1.1.5 > > They install files into the same place. > Please remove them first with pkg_delete(1). > *** Error code 1 > > Stop in /usr/ports/net/samba33. > *** Error code 1 > > Stop in /usr/ports/net/samba33. > $ > > > > So, here are my questions: > > o) Anybody else seen this before? I still run 3.0.37, which has been portupgraded with each new rendition since 3.0 without any trouble. It began life on 7.2-Release and now runs on 8.0-Release after system upgrade. But it is a server and has no desktop software, e.g., Gnome, to cause problems. Has always run fine and never had any trouble compiling. > o) Anything that could be done against this problem? > This may seem dumb, but since you already have Samba4-devel ostensibly built and installed why not run that? Or, since you have these other requirements which you won't uninstall and if Samba4-devel doesn't run fix that so that it does. Either remove Gnome2 and it's MAPI stuff or fix Samba4-devel. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Re-compiling PHP changes server responsiveness
Matthew Seaman wrote: [snip] >> I get: "[warn] (2)No such file or directory: Failed to enable the >> 'httpready' Accept Filter, and no new errors in >> /var/log/httpd-error.log" four times >> >> Tried adding accf_http="YES" to /boot/loader.conf, and re-booting of >> course. > > This is just a warning message and doesn't stop apache working or not. > Enabling accf_http should give you a bit of a performance boost under > heavy load and help you withstand certain types of DoS attack, but it's > not required. > I found I needed both accf_data_load="YES" and accf_http_load="YES", but I am also running SSL too. I've also noticed that I tend to not receive this error when Apache starts after a fresh system boot. Have never tried to examine it further as I don't reboot or restart Apache very often. It just seemed happier when I added the http_load into the mix and only spews the error at non-reboot restarts. [snip] >> What else should I look at? >> > > Try restarting httpd from the command line: /usr/local/etc/rc.d/apache22 > restart > > This will run a configtest and then try and start up apache. Then check > that apache is still running: /usr/local/etc/rc.d/apache22 status > > If apache has mysteriously disappeared and there are no messages in log > files, then it means apache crashed during the startup process soon after > daemonising. That's pretty diagnostic for loading a dynamic module that > disagrees with it. > > At a guess, and given that you've reinstalled all your php modules, I > think you > may be being hit by the php module load order problem. In that case, > running > php from the command line will probably also segv on you. This is > something that has had quite a lot of attention on this list, but there > isn't a really good solution yet, other than manually reordering the > entries in /usr/local/etc/php/extensions.ini > > Also, if you're running eAccelerator, make sure you recompile it at the > same time you upgrade the main lang/php5 port: eAccelerator will cause > Apache to crash if you try and run it against a different version of PHP > than it was originally compiled for. > The same would apply whether it was xcache or the Zendoptimizer. The way to pin the problem down is to rename extensions.ini temporarily to extensions.ini.bak and comment out the #LoadModule php5_modulelibexec/apache22/libphp5.so line temporarily. Start/restart Apache and if it works OK with serving static content it confirms the problem is PHP. Then add the Loadmodule line again in httpd.conf and restart. If it restarts with no errors and again serves static pages fine the PHP module itself is OK. Trying to run something like a CMS will still be error prone as the various modules it needs aren't being loaded and found, as the extensions.ini file is still renamed. Note that if Apache is happy with mod_php while extensions.ini is still renamed it also confirms no major flaw in the php.ini file. If Apache runs fine with the mod_php module then the trouble is in the extensions. Rename the extensions.ini back to it's original state. There is a script that may be run to realize a close approximation of the extension loading order problem: fixphpextorder.sh which can be found here: http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround That is a stab at the reordering problem, but in my case was not enough to completely solve my problem. I also had to comment out extension=mhash.so with a ";". This was arrived at by commenting out line by line one at a time until I hit the one causing the breakage. This particular extension has been problematic for me for some time now. Some upgrades it works and for some it is broken. Remember that each change made requires an apachectl restart. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: is this booting info correct?
Fbsd1 wrote: [snip] > > The number of hard drive primary-partitions/slices is determined by the > motherboard BIOS (Basic input output system), not the operating system. > Standard motherboard BIOS limits hard-drives to 4 main divisions > [snip] Not quite true. The only thing contained within the BIOS is an instruction to jump to sector 0 of track 0 after a successful POST. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: black hole test
Jonathan McKeown wrote: > On Wednesday 16 December 2009 22:05:06 Peter Wemm wrote: >> Daignostic message to trace mailing list processing, please ignore. > > You have heard of freebsd-test@ , haven't you? Uhmm, he is the mail admin and this list was down; don't you think he should be able to test out the problem? Thanks Peter for fixing whatever it was... -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: disk with high frequency noise only on FreeBSD
James Phillips wrote: > >> Date: Fri, 11 Dec > 2009 23:52:50 +0200 > From: ly4uk Root >> Subject: disk with high frequency noise only on FreeBSD [snip] > > Now, this post is interesting. I'm sure many people with a software > background may be tempted to write this report off as completely > implausible. The truth is even "non-moving" parts such as inductors > and possibly capacitors can move in response to an applied signal. > For example, my ADSL modem with no moving parts makes an audible > hissing noise louder than the (80mm) fan noise of my BSD server. It is possible for one or more electronic components to emit a noise, even an integrated circuit. This is usually the result of an abnormal operating condition which has established a self sustaining oscillation, which requires some form of feedback loop to operate. The quintessential example is the horizontal output transistor in an analog television or CRT style monitor. These normally operate at about 15KHz but not audibly. When the components around them have altered value enough to change bias voltages they will oscillate and produce a loud high pitched whine. Failure is what eventually occurs in this situation. I had one machine that the memory would "sing" only when a make buildworld was run in FreeBSD. I have an old British Airways movie headphone set from back when their system was acoustic with air tubes. This works really well for examining where a sound is coming from. > I have no idea what would be causing this in 8.0-RC2, but I can > suggest what to look for: anything polling the drive in the audible > frequency range (20 to 20 thousand times per second). Another > possiblity is any action the repeats at that rate, but was not > present in ealier versions. The timer interrupt is in that range, but > other systems like GNU/Linux (before the tickless kernel) and Windows > use a similar timer. There are now 3 timers to choose from, and I think the default changed to the acpi fast timer. Interesting analysis, but very well could be related. > To the original poster: you say this is a laptop. How do you know the > noise is coming from the hard drive and not some other component like > the speakers/Network card/fan? > Regards, > Yes, the noise could be coming from elsewhere. And if it is indeed coming from a VLSI type of chip it does not bode well. This indicates some form of abnormal operation which is most often eventually destructive in nature. There is actually probably very little you can actually do about it, so just live with it and "if it ain't broke don't fix it". When it is broke hit repeatedly with progressively larger hammers until it's in pieces and you now need a new one. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: lynx failure....
Gary Kline wrote: > Guys, this is what I see both here on my desktop, and on a > remote server, magnesium.net. Using lynx: > > > Looking up www.thought.org > Unable to locate remote host www.thought.org. > Alert!: Unable to connect to remote host. > > lynx: Can't access startfile http://www.thought.org/ > p6 0:03 > [3] > > > Obviously, something is wrong with how my new DBS, mAil, and > web server, ethic, is configurated. Can anybody help me here? > A Dig output from my location: Your DNS is somewhat screwed up. ; <<>> DiG 9.6.1-P1 <<>> www.thought.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21126 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.thought.org. IN A ;; ANSWER SECTION: www.thought.org.38299 IN CNAME aristotle.thought.org. ;; AUTHORITY SECTION: thought.org.10700 IN SOA ethic.thought.org. hostmaster.thought.org. 2009120801 10800 3600 604800 38400 ;; Query time: 1 msec ;; SERVER: 192.168.10.1#53(192.168.10.1) ;; WHEN: Sat Dec 12 03:32:48 2009 ;; MSG SIZE rcvd: 110 I'm certainly no DNS expert. I also have no clue as to how you are configuring your DNS. So any comments will be along the lines of text editing zone files for BIND. Here is an example of a zone file for my internal LAN (a public zone will have different information, but the structure should be similar enough for example purposes. $TTL3600 test.zip. IN SOA server.test.zip. testu...@test.zip. ( 20090614; Serial 10800 ; Refresh 3600; Retry 604800 ; Expire 86400 ) ; Minimum ;DNS Servers IN NS server.test.zip. ;MX Records IN MX 1 server.test.zip. ;Hosts server IN A 192.168.10.1 workstation IN A 192.168.10.2 testbed IN A 192.168.10.3 ;nicknames static IN A 192.168.10.3 -- Notice the SOA starts with the domain, here it would be thought.org. See the "test.zip." in the above? Period included. Try and use an "A" record instead of CNAME. In any case, you will need an "A" record which contains the IP address of your server. In the Dig above there is nothing to indicate any IP address for the hostname you are trying to resolve. This is just a quickie to get you looking in maybe the right direction; there are others on the list who have much more smarts about DNS than myself. I'm just around at odd hours, so take a look and wait a bit for the smarter people. Also remember when you make changes update the Serial number so zone transfers will propagate, and remember the TTL, refresh, retry, etc parameters will mean any change will take time to propagate. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: use DD mode or not? and how to set up?
Tom Worster wrote: > options for setting up gmirror include DD or standard mode. i don't know > about others. > > i'm about to install 8.0-RELEASE on a system with two 750g sata disks that > i want to run as a mirrored pair. > > what are the pros/cons of the different options? > > and what about the installation process? set up the mirror before > installing from the CD or do it like the handbook says? > I believe DD mode is going away. Probably has something to do with adding features to loader for GPT support. A GPT places what's called a "protective" MBR in the place where the old DOS style MBR would normally occupy. I would avoid DD. Last question is easy if dealing with a true hardware RAID card, as you will create the array in the card's BIOS and FreeBSD will just see that as ar0 and install to that. As far as a perfect answer I'm not certain. There is one little tidbit that may assist though. The metadata gets stored in the last sector at the end of an empty disk. As long as there is free space at the end of the drive(s) it won't matter which way you do it. The Handbook is essentially reconfiguring an already virgin install existing on the first drive. When rebooted into this changed configuration, the second drive is then added to the mirror and replication will take place. The less amount of data present will speed this replication and get you to mirrored status quicker. I've done this a couple of times and it was pretty straightforward. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: geometry does not match label (255h,63s != 16h,63s)
J.D. Bronson wrote: > What if we tried a custom kernel and removed these lines: > > options GEOM_PART_GPT # GUID Partition Tables. > options GEOM_LABEL # Provides labelization > > I think that might remove these 'errors'. > My kernel already has these removed and yet I also only began getting these after upgrading from 7.2 to 8.0 on both servers at home. So far just ignored them. Normal csup source and make buildworld/etc dance followed with a portupgrade -af and make delete-old-libs. So, yes, another "Me Too". :-) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: WINE on 6.3
RW wrote: > On Sat, 05 Dec 2009 13:47:00 +0100 > Andrea Venturoli wrote: > >> Hello. >> Is WINE usable on 6.3/i386? >> I cannot seem to start any win32 program and before I spend time into >> it, I thought I just ask. >> >> My interest is almost limited to running a simple console app that >> does very litte beyond reading a text file, processing it, and >> outputting another text file. > > It's think it's possible that the p13 update "no zero mapping" might > have an affect on windows/dos programs. > [snip] Not sure this is present in 6.3, so check first. A quick sysctl security.bsd.map_at_zero will return a value of 0 if present. As RW indicated it may have been included in the p13 update. To elaborate a little, you may need to toggle the security.bsd.map_at_zero: 0 MIB. Change this to 1 to disable, not sure if loader.conf or sysctl.conf is the right place. Would be better not to have to do this because leaving it enabled is a security feature. However, WINE may not run without it. I'm also not sure if the following is related, I just recall reading about it at in the same time frame and mostly with regard to Samba. Possibly there is a need to place CONFIGURE_ARGS+= --disable-pie in make.conf and recompile WINE. This may not apply to WINE at all so if the MIB config mentioned above fixes the situation do not proceed with this. I suspect wrt to WINE this is irrelevant, but thought I'd mention it anyway. Should you discover --disable-pie is required leaving it present in make.conf is not a very satisfactory arrangement, as it would then apply to all ports. Workaround would be to place it just for WINE recompile if absolutely necessary and then comment it out when done. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: malformed man pages
Sagara Wijetunga wrote: [snip] > > We use /usr/bin/less from ftp://ftp.gnu.org/gnu/less, the > less-382.tar.gz, unpatched. Why? > Does the less need to be patched in FreeBSD? If so, is there such a > patch exist? > Uhmm, this may sound a little strange, but why not use the one included as part of the system? In other words, there was no need to 'install' less. Remove whatever you installed and use the right one. It even has a man page, e.g., man less and you will see a man page for the included one unless you've made a total mess of your man pages. I suspect there may be a possibility of bringing "Linuxisms" to your approach to FreeBSD. While there may be some amount of crossover, FreeBSD is not Linux. Learn FreeBSD as if it were new to you and leave the Linuxisms aside. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 2 processes reproducible read same file with different speed
cronfy wrote: > Hello. > > I've noticed a very weird behavior of 2 Apache processes that shold read > the same file to process a request (they configured to read it on every > request). One spends about 6ms to read the file, and second spends about > 114ms (I used ktrace to find this out). Every time, on every request, > the problem is reproducible. Apaches are the same, the only difference > between them that they are working from different users to serve > different sites. Same binary, same config. > > First Apache used to work in the same way some time ago - it spent > ~120ms to read the file. But once it changed and now it is working fast. > > Restarts of Apache do not look to affect on anything. > > The file that Apache should read is 315k long. Apache reads it by small > blocks of 4096 bytes each. May be FreeBSD has some memory about how > process is working with files and after some time enables some > optimization or caching? I just do not have any clue... :( > > Can anyone explain this please? > Caching is coming into play if the first read takes longer than subsequent reads. It may not be uniform as older objects move in and out of cache being replaced by newer. The OS will have some space for buffer caching and when Apache makes a 'hit' on this cache retrieval will happen faster. This buffer space is dynamic in nature, and will shrink as Apache fills up memory. As Apache needs more memory the OS will attempt to provide as much as it can within reason by shrinking the buffer allocation space. If this is a static file which needs to be read by all pages served, some other form of caching should be investigated. In the meantime you may want to try the following in httpd.conf if not already doing so: EnableMMAP on EnableSendfile on You may also want to see if you can set aside a little RAM and cache it there, ala: http://httpd.apache.org/docs/2.2/mod/mod_mem_cache.html Another approach is a reverse proxy such as Varnish in front of the web server. But the first most immediate thing you can try and measure is to turn on sendile() if you're not using it. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NO_PROFILE versus WITHOUT_PROFILING
Pieter de Goeje wrote: > On Friday 27 November 2009 12:45:54 Frank Staals wrote: >> When I was setting up my system for a complete rebuild I came across >> something unclear to me; I always used NO_PROFILE in my make.conf, >> however from what I've read specific make options to build the >> kernel/base system should be in /etc/src.config. The manpage of src.conf >> specifies the option WITHOUT_PROFILING, which seemed to be the flag that >> I was looking for. Just to be certain I always keep the 'Rebuilding >> World' chapter of the handbook close, however that still specifies to >> use NO_PROFILE in make.conf. >> >> So now my question: What is the desired way of turning of profiling: >> NO_PROFILE in make.conf or WITHOUT_PROFILING in src.conf ? >> >> Thanks in advance >> > WITHOUT_PROFILING in src.conf. The NO_xxx options are obsolete and should > not be used. > Yes - src.conf is used for the system. make.conf will contain options you want to apply to building ports. They were split to separate them. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mysql60-server??
Matthew Seaman wrote: > Gary Kline wrote: >> kwik one: >> >> in his build-server stuff [6.2], jon horne said to use >> mysql50-server. i see the latest is mysql60 >> >> should i go ahead and use the latest mysql database? or just do as the >> >> instruction say? [snip] > > Prior to that we have: > > mysql51 -- MySQL's current GA (generally available) release offering. It's >got a number of new features like stored procedures but >depending on your workloads it may or may not be faster than... > > mysql50 -- The previous GA version, and still the most widely deployed > version at >the moment. It is still being actively maintained even if it >is pretty >much down-played on MySQL's website. This is a version that >has been in all sorts of production use for years and pretty >thoroughly debugged, hence a very safe choice. > > In summary: choose either of mysql50 or mysql51 according to preference or > your particular requirements. > A lot of people are still using 50 and many consider it faster than 51. I think the main difference performance wise is 51 might have a tad heavier thread handling performance for the latest and greatest high end quad socket quad core boxen. 50 may offer better performance on older more down level commodity boxen. I've been running 51 for a quite a while now and haven't had any trouble with it, but I'm not hammering it either. If the hardware isn't quite up to snuff 50 may actually be a better choice, especially in the scenario where web and database are running on the same, albeit slower machine. Another factor in the decision might be to consider when EOL may be scheduled. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BTX Loader crashes -- Help wanted
Ronald F. Guilmette wrote: [snip] >>Try 8RC3 and see if any difference. I believe some work in this area may >>have occurred. > > I just tried it. Alas, same result. I follow the -CURRENT and -STABLE mail lists as well as this one. Though this particular problem does not pertain to me, I seem to recall some traffic off and on about this subject occasionally. So it is known. The place to get the developers to look is wrt to 8.0, so if the problem is well documented they may be more inclined to look into it. If the bootonly, install CD, or LiveFS CD for 8-RC3 can be used to reproduce the problem concentrate here. >>I don't believe you are the first to experience this. > Well, I'm just about to file a new PR on this, but I'll refrain if > someone else has alreadyt done so. Do you have an eisting PR number > on this? There are quite a number and a few of which are very similar in that they directly reference boot loader crashes. You could review the ones that seem to match the closest to your situation directly (e.g. hardware and crash- dump wise), particularly the BTX crash associated with booting from SATA CD/DVD. Eye them towards using as a template to get started. The more exacting and succinct the PR the more likely to stimulate interest. You can reference the handful that match the closest by number in your own PR. Be very exact to localize the trouble to specifically SATA CD/DVD hardware. If the box will boot and install fine from a PATA CD/DVD drive to a SATA hard drive be sure to include this. You have a VIA VT8237A controller on that board so that aspect should work. This will serve to isolate and confine the problem to be examined to a very specific issue. This increases the chances someone may look into it. [snip] > > Shsh! I literally _just_ bought this new SATA DVD drive, and I went > with SATA because I believed that (a) the world is slowly but surely > switching everything over to SATA and (b) SATA has been around long enough > now that FreeBSD related bugs should have all been shaken out by now. > > Please excuse my snarkiness, but... I guess I was wrong about the latter. > >>If 8 does the same thing file a PR in order to bring the attention of the >>developers. There may be one, or more, already on the subject. > > Well, I did a search on the PR database for "BTX" and I'm looking at all > those PRs... some of them going back to 2004, which doesn't exactly > inspire confidence about a possible timely fix... and I don't see anything > in the subjects that quite matched up to what I'm talking about. If you just need the box to work immediately use a PATA CD/DVD. If you have the time to deal with it, attract the attention of developer(s), and have the time to work with them it serves the interests of the larger community. Others have had and will have your problem and getting it fixed for you will just mean many others will not go through what you are currently experiencing. > And ah... while we are on the subject... > > If I do file a PR on this, then at long last I'll need to know the answers > to the two questions that have been in the back of my mind for ages, > regarding PRs... > >1) What do the various severity codes mean? >2) What do the various proirity codes mean? http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/ http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pr-guidelines/ Might be good reading. I should read them again myself. It's been a while. > > I've never filed a PR with severity "critical" or with priority "high" > because I've always figured that this may be a good way to get the > developers to view _all_ one's future (and past) PRs with a suspicious/ > jaundiced eye... you know... the-boy-who-cried-wolf syndrome. > > I don't want to be labeled as a nut case or an incessant complainer, but > for _this_ issue I'm thinking that severity==critical and/or > priority==high > may be appropriate. I mean jeezzz Louise! If one can't even install from > the distribution CDs/DVDs on perfectly good hardware... (And it's not > like the whole SATA interface standard is exactly ``new'' or anything > anymore.) > > So? Any advice? Should I stick my neck out and label this PR either > severity==critical or priority==high ? > There is always going to be a certain subjectivity present here. What is life and death important to one person may not be to another. I believe a commonly accepted dividing line can be found when you consider the usage of the system(s) in question. If you are a sysadmin or consultant who is being paid money to maintain mission critical servers then it warrants a higher level of concern than a single user at home with a desktop PC. If you are racking a hundred Dell 2950's and have a problem it is critical. If you are a single PC user at home with a desktop, not so much. I do understand your concern wrt to "the boy who cried wolf" and it does matter. You stand more of a c
Re: BTX Loader crashes -- Help wanted
Ronald F. Guilmette wrote: > > Who should I be talking to if the BTX loader is crashing on my > specific hardware configuration, and what specific info do I > need to be gathering for him/her in order to have hope of getting > the problem rectified? > > I'd pulled stuff out of the system in question until there's > practically nothing left and I'm at my wit's end with this problem. > > System: > AMD Athlon 64 1640B CPU > MSI K9VGM-V motherboard > 1GB 667 DDR (Kingston) > LG DVD Burner Black SATA Model GH22NS50 - OEM > floppy drive > > That's it. I've yanked out all the non-essential cards, _and_ I've > even taken out the hard drive, and I'm still having BTX crashes. > > The problem(s) occurs with FreeBSD 6.3-RELEASE/i386 disk1 (CD), > 7.0-RELEASE/i386 disk1 (CD), 7.2-RELEASE/i386 Live Filesystem (CD), and > 7.2-RELEASE/amd64 Live Filesystem (CD). Try 8RC3 and see if any difference. I believe some work in this area may have occurred. In any event, these RELEASE versions are static and will not change. The only hope in this area would be if a fix from the 8.0 work has been MFC'd back to 7 STABLE. > The symptoms are different depending on which of the above I'm trying to > boot from. In the case of the first two, the crash results in a bunch of > register values being displayed on my screen, after which the system is > dead. In the case of the last two above, it appears that the BTX loader > actually starts to load a kernel (well, anyway, the little twisty thing > starts turning), but then the screen goes completely black, after which > my monitor senses that the video signal has gone completely dead, and > at that point the system is just frozen, and needs a power-cycle or hard > reset to get going again. I don't believe you are the first to experience this. > Curiously, with the same motherboard (_and_ the same boot CDs), I have no > problems at all booting off of any of the above boot CDs, AS LONG AS I am > using a different (PATA) CD/DVD drive. But I have tried two different > recent vintage SATA CD/DVD drives (Optiarc & the LG mentioned above) and > both result in the booting failures described above. You can try disabling ACPI at boot, as well as toggling the BIOS between Enhanced and Legacy mode if this option is available. Probably your best approach will be to use a SATA hard drive while using a PATA CD-ROM. This is most likely what you will have to do if 8RC3 doesn't make any difference and you just want to get the box going. > I'm bumbed. I really had hoped to start moving my machines over to SATA, > but so far things are just not working out smoothly at all. If 8 does the same thing file a PR in order to bring the attention of the developers. There may be one, or more, already on the subject. Since the old releases are static the place to get the bits fixed is in the ongoing work. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: panic? i386 on dell duo
Gary Kline wrote: [snip] > > my network bud down in dallas is helping me get the dell as my > new server. my old hp kayak is from 1998 and on its death-bed. > > okay: i have 7.2-R, i386. installs fine. jon horne changed the > IP that the op sys | DHCP suite chose from 10.47.0.112 to > 10.47.0.230. i do not know why, but he change the ifconfig line in > /etc/rc.conf from ="DHCP" to ="inet 10.47.0.230 netmask 10.0.0.255" ^^ Can't speak to most of the post but this netmask certainly looks strange. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how to do a custom install?
Gary Kline wrote: > > due to strange disk problems i was down for around 30 hours. i am > currently wiping dos/win off in favor of 7.2-R and i have a question > about doing a "custom" install that would let me slice the drive into > more that four pieces. > > i am building, by default, > > /, > /var > SWAP, and > /usr > > it has been years since my custom install where [[*some*]] technique > let me slice something like, say, > > /, > /var, > /tmp, > /usr/local/ > SWAP, and > /usr > > anybody remember what keys to hit in the installation procedure? > > tia, > > gary > > Not sure about the terminology in use here. The old standard was to create one, or more, slice(s) and then partition with bsdlabel. In the sysinstall step for this it will run fdisk. Note that playing by the $MS standard the normal maximum number of slices would be 4, e.g. aka "primary partitions" in the Dos/Windows world. Fdisk makes "slices". An example of a slice on an IDE drive would be ad0s1. After the fdisk step would next come bsdlabel. This is the step that creates partitions within the "slice" previously made with fdisk. Note the difference in terminology: what Dos/Windows refers to as a "primary partition" in the Unix world this is a "slice". Partitions are created within a slice with bsdlabel. On the sysinstall Custom menu these two options are one above the other, e.g. Fdisk and Label. Select the Fdisk and create a slice, exit fdisk returning to sysinstall and proceed to select the Label menu option to bring up bsdlabel. (IIRC also called disklabel.) An example of a partition would be ad0s1a, ad0s1b for swap, ad0s1c is a reserved wrapper entity, ad0s1d, e, f, g. Usually ad0s1a will be your root, b will be swap, d might be /usr, e might be /var. etc. In the bsdlabel utility there is the option to choose both the partition type and size as well as it's mount point. It is actually possible to have more than 4 slices even when playing by the $MS Dos/Windows standard. Fdisk will allow for the creation of what on Dos are called "extended partitions". The numbering for these starts at 5. You won't be able to boot from them and from a *Nix point of view are semi useless except within the context of Dos/Win compatibility. If this is just going to be a FreeBSD machine no need for the so-called "extended partition" of the Dos/Win world. Just create a slice [fisk], and break that up into partitions [bsdlabel]. If everything goes according to plan after Fdisk, Label, Return to previous menu, etc, at some point later on (IIRC after choosing packaging distributions) sysinstall will later perform the actions you configure in these preparatory steps. For reference peruse the Handbook; it's probably written clearer than I can accomplish. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: networking won't come back up until reboot after ISP outage
umage wrote: [snip] >> In my case the router does get the renewed ip, as I described earlier. >> However, even after waiting 8+ hours, the system will not recover from >> the outage properly (reason unknown). That's what this thread is all >> about. > When I started the system today, I found that again it had no > connectivity. I did some checks and then found that 'natd' was not > running. But this is not happening that frequently, and seems to only > have started after the last system update. Could be some sort of race > condition. Is there a logfile that natd writes to, so that I may > investigate the reason why it is exiting? My first gut instinct about your problem was to blame dhclient first. But no NATD would definitely be a problem. I am assuming we are talking about IPFW and NATD here, and it has been many years since I've used it. I migrated to IPFILTER and then on to PF quite some time ago. Most logging related to IPFW is already present, but IIRC to log NATD you need to turn it on, and possibly configure it in syslog.conf should you desire the output somewhere other than /var/log/alias.log. Keep in mind there are two ways to pass options. You can use something like natd_flags="-l" in /etc/rc.conf. Man natd will provide a list. The second method is to place the options in a file such as natd.conf and pull them in like natd_flags="-f /etc/natd.conf". I looked in my notes and here is a snippet from an old /etc/rc.conf: natd_enable="YES" natd_interface="ppp0" natd_flags="-f /etc/natd.conf" My /etc/natd.conf: interface ppp0 use_sockets yes same_ports yes dynamic yes You could add a 'log yes' line here; it does the same as the -l described above. Note that you might need the 'dynamic yes' switch for an interface that changes. In my case I was using it for a ppp dial-up connection, change interface as needed. Sounds like you are narrowing down the culprit(s). Also note that it could possibly be a timing issue related to the order things start up. If the NATD is attempting to start before the interface has come up it will die. Shouldn't happen, but... YMMV -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: networking won't come back up until reboot after ISP outage
umage wrote: > On 7. 11. 2009 19:07, Jason wrote: >> Have you tried restarting routing? >> >> /etc/rc.d/routing restart >> >> I have found the same symptoms with other outages and not performing the >> above. >> >> I have done "/etc/rc.d/netif restart" and "/etc/rc.d/routing restart". >> [snip] >>> > Thank you for the hint, I will try it when this happens again. > Note: the output of netstat -r was identical to what it is currently... > FYI: I've been using freebsd 6.2 -> 7.2 until now, and I never had to > intervene - the system resumed networking as usual. It might have > something to do with migrating to 8rc1 (most likely not), or that I'm > now using DHCP and there's a glitch somewhere (maybe). My configuration is most likely different from yours in that my DSL modem- router is configured for split-bridge. This allows the DSL modem to handle the PPPoE connection and login but passes the WAN IP to my FreeBSD gateway box via DHCP. So the NIC on my gateway is getting it's lease from the DSL modem instead of directly from Verizon. Your DHCP lease is probably coming directly from the ISP I would presume. When the connection goes down and comes back up it will take 5 minutes before my FreeBSD gateway box checks the lease and decides if a renewal is in order. This is automatic. If I am sitting in front of my computer and I want to speed this up I issue /etc/rc.d/netif restart on the gateway and it will come up and be happy in about 10 seconds, rather than waiting out the 5 minute time out. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help understanding basic FreeBSD concepts (ports, updates, jails)
Roger wrote: > Hello all, > > I have another concept that I'm confused about, the source distribution. > Some ports, like "lsof" require the existence of /usr/src. > What I don't understand is which version to use to keep synchronized > with the production release. > When the installed was performed the release was 7.2 but after doing > "freebsd-update" the release is now > 7.2-p4. A RELEASE such as 7.2 has a maintenance period during which the security team will apply security patches to the OS. Only the patches are applied, the rest of the bulk of /usr/src is untouched. This is what the -p4 means. The security support period for different releases can be located on the web site. Some releases are designated "extended support", while others have shorter time frames. > According to the documentation, I can track CURRENT, STABLE plus > other. Which one is the recommended one for a production server. I have > not build that many > packages that need the sources present so now would be a good time to > find out which one > I should use. > I don't use the binary freebsd-update myself, but still use the old csup the source in /usr/src and the make buildworld/buildkernel/install dance. So I tend to think in terms of CVS tags. The tag RELENG_7_2_0_RELEASE would fetch the original release bits that never change. The tag RELENG_7_2 would fetch the /usr/src that has the security patches applied. The -p4 you observed means that freebsd-update used binaries built with security patches applied. If there exists any question as to whether your /usr/src is in sync you can simply csup your source with the RELENG_7_2 tag in the supfile. There is also another way to patch, and that is to apply patches manually. Let's say, for example, the built in bind had a file or two that got patched. You could rebuild just this one thing and after installing the bits simply restart the daemon. Sometimes this is preferred when one needs to prevent a security hole but doesn't want to reboot a server. A downside is when you do this it does not register the "-p4" like you noticed. For a production server I feel it is best to use production release. IMHO there is one possible cause to consider STABLE for a production server and that is if there is new code "Merged From Current" that addresses and corrects a very specific problem. Let's say you have a particular NIC in your server that is exhibiting an exact same (and reproducible) condition as described in a bug report. If code which fixes this exact problem becomes available it will be written in CURRENT, and after some testing if deemed to be of sufficient quality it will be merged back to STABLE. Upgrading to STABLE will then pull in this fix. IMHO I wouldn't normally consider this unless there is an exact match between problem and fix. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /etc/fstab + embedded spaces
carmel_ny wrote: > I was attempting to create this entry in the /etc/fstab file. It is to > a WinXP machine. > > //u...@bios/My Documents /laptop smbfs rw,noauto 0 0 > > It fails because 'fstab' does not allow embedded spaces in device > names, not does it allow enclosing the name in quotes. > > I did some Googling and discovered that I am not the only one annoyed > by this behavior. I discovered this patch that had been submitted awhile > ago. > > http://lists.freebsd.org/pipermail/freebsd-bugs/2007-October/026469.html > > Changing the share name is not really an option. Is there some way of > making this work in 'fstab'? I can use the name including spaces in > 'mount_smbfs' so that is how I am currently mounting the share. It just > seems strange that 'fstab' by not accepting the use of quoting is not in > step with how FreeBSD usually operates. > Don't know if this works for fstab, but the normal way to escape spaces is with a \, like this: //u...@bios/My\ Documents /laptop smbfs rw,noauto 0 0 May not work in fstab but you can try it and see. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why after packages update my 'startx' gives me a message: Protocol not supported by server.
Yuri wrote: > It keeps repeating this line in original terminal, putting line ".." in > between. So it looks like this: > Protocol not supported by server. > .. > Protocol not supported by server. > .. > Protocol not supported by server. > .. > > > Now I have to start just 'Xorg', it starts bare X. And from another > terminal I have to start kde: "DISPLAY=localhost:0.0 > /usr/local/kde4/bin/kde" > Then it works ok. > > My .xinitrc looks like this: > > export LANG=en_US.UTF-8 > export XMODIFIERS='@im=SCIM' > export GTK_IM_MODULE=scim > export QT_IM_MODULE=scim > export XIM=SCIM > export XIM_PROGRAM=SCIM > exec scim -d & > /usr/local/kde4/bin/startkde > My first wild guess would be take out all the scim lines in your .xinitrc and see if the messages disappear. I know xorg.conf isn't supposed to be 'needed' any longer, what with Xorg's supposed ability to auto configure, but you might want to look at the Xorg docs for configuring scim in Xorg. I don't use it myself but have seen something about it in the docs. Once the support has been added/configured then look in the KDE desktop config utility and set it up there too. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dhcpd related issue - not giving up
Dánielisz László wrote: > I don't give it up, doing some tcpdump on my BSD I can see the dhcp > request reaches the machine, the dhcpd is running, but why doesn't gives > any IP? > > # tcpdump -i rl1 -n port 67 or port 68 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on rl1, link-type EN10MB (Ethernet), capture size 96 bytes > 11:51:43.086597 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request > from 00:24:03:f1:bd:36, length 300 11:51:45.102260 IP 0.0.0.0.68 > > 255.255.255.255.67: BOOTP/DHCP, Request from 00:24:03:f1:bd:36, length 300 [snip] I only have a couple if ideas. First, is it possible to substitute some other non rl or re NIC for rl1? I seem to recall something about these cards having some sort of problem like this. This test would eliminate that idea. Also, right after a client machine requests a lease examine your arp tables on both machines. Maybe the dhcpd server is confused and sending the reply out the wrong interface? sockstat -4l can confirm which/what interface dhcpd is listening on, compare with arp results. Theoretically if dhcpd is bound to and listening on rl1 there shouldn't be any replies going out rl0. Check to eliminate. Wrt to a managed switch blocking ports, I think you probably ruled this out by connecting the machines to each other. Note that for GigE, or NICs that do MDI-X properly any cable will work. However, on many older 100baseTX cards this would need to be using a crossover cable to function correctly. You can also broaden your tcpdump to include arp traffic. When the output files become cumbersome to examine it's easier to look at them in Wireshark. I have a hunch if rl1 could be replaced with some old fxp or sk card lying around it might work. YMMV -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Bad sectors: how bad can it be
Michaël Grünewald wrote: [snip] > > I have backups of the data contained in the broken, so the data on this > disc are not a concern. I have however a question: How do I verify that > a hard-drive is accurately working if its firmware will hide the bad > sectors as long as possible? > [snip] As Polytropon indicated the smartctl commands for testing contained within the smartmontools port will extract the error logs from within the drive's firmware. There are two modes you can select from (basically a long and a short) that you can execute "now" at a command prompt. It can also be run as a daemon for continual monitoring. The data returned is somewhat arcane and can be semi difficult to interpret. There are various levels of usability which can vary by hardware. Some RAID controllers may get in the way of direct communication to some hard drives. Other controllers, as you go up the 'expensive high dollar' ladder will often do built-in SMART monitoring and will beep and/or send emails when it detects error conditions from a drive. Some even either contain, or have an external utility which provide a web based browser accessible view in real time. The purpose is to attempt to detect a drive that is about to fail. As far as the most basic level goes, you would look for numbers which indicate that the bad sector remap area has filled. Once this space gets filled any new bad sectors that develop can no longer be mapped out. This usually shows up in the operating system as some generic form of "unrecoverable read/write error" message and Bad Things begin to happen. I have not used Spinright in a very long time, but it may buy some life on such a drive. If it can clear the bad sector remap area after adjusting the remap table it can give new life to a drive. The same thing used to be possible on SCSI drives by running the low level format utility usually contained within the controller firmware. Such "fixes" should only be viewed as extremely temporary in nature, as the general pattern with regard to magnetic media failure is that once it starts to get bad spots it will keep on getting bad spots on a fairly regular basis afterwords. Interesting reading: http://www.usenix.org/publications/login/2008-06/openpdfs/bairavasundaram.pdf -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why is sendmail is part of the system and not a package?
Jerry McAllister wrote: > On Tue, Oct 27, 2009 at 05:03:12PM -0200, Gonzalo Nemmi wrote: > >> On Tuesday 27 October 2009 4:32:45 pm Erik Norgaard wrote: >> > Jonathan McKeown wrote: >> > > Just as a matter of interest, if you want to rip sendmail out of >> > > the base system, which MTA would you like to replace it with? Or >> > > are you suggesting the system ship with no way to handle mail? [snip] >> >> Dear Erik: >> >> Contrary to your belief the thread isn't moving of topic from OP, it's >> just taking the same default route it has been taking for ages: >> 1) telling the OP the OS needs an MTA >> 2) telling the OP he can replace the default MTA >> 3) telling the OP he can remove given MTA from base >> 4) telling the OP about "historical reason" >> 5) Not telling the OP why has FreeBSD has left so many historical reason >> behind to persuit new goals but retained Sendmail as the default >> MTA "for historical reasons". >> >> Sorry .. but that's the way it goes every time someone asks the same >> question. Sounds like FAQ material. > I will add one more that covers it best. > Sendmail works just fine and there is no ACTUAL CURRENT reason to > get rid of it.Years ago it had some weaknesses which have been > fixed. > > So, that leaves personal preference as the only real reason > for wanting to replace it. > In that case, if your personal preference is to replace it, go ahead. > There are several candidates and an earlier post described well how > to do it. > > As for putting it in ports and taking it out of base, well, some > message system is often needed before ports are installed. Sendmail > fills the bill.Some other could also, but since Sendmail works > just fine and is already there, then it is. > [snip] I'm no mail server guru, but I liked how one could fairly easily get a base configuration going of Sendmail by following the page in the Handbook. Once done Postfix could be installed from ports and it would Just Work, because it would adopt the Sendmail config. Tweaking can start from a known good configuration. This doesn't include addon complexities such as virtual domains and users, spam and anti-virus, etc., but I've always found it better to start with a functional base and add the additional stuff one thing at a time. Yes - I favor Postfix, but it may not be the right cup of tea for all situations. However, my own personal preference is to leave the Sendmail thingy the way it is. I still use Sendmail for some things. There's just too many other fish that need to be fried. It works, supplies basic necessary functionality as is, is largely trouble free these days, and easily replaced with some other personal preference should it be desired. The guy in charge also actively maintains the FreeBSD bits. Compare the way Sendmail works in FreeBSD with lets say, ahem, Adobe's Flash. Opposite ends of the spectrum. Just my $.02 for sure, but I like the "status quo" being what it is. Now returning to the painting of my bikeshed... :-) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: howto use https in favour of http
Scott Bennett wrote: >>> Alexander Best wrote: > Hi, >> i've added the following line to my /etc/hosts: >> permail.uni-muenster.de:25 permail.uni-muenster.de:443 >> so what i want is for freebsd to never use http, but https for that >> address. [snip] Perhaps the easiest direct solution is to bookmark https://permail.uni-muenster.de/ in the browser bookmarks instead of http://permail.uni-muenster.de/ -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: howto use https in favour of http
Steve Bertrand wrote: > Alexander Best wrote: >> Olivier Nicole schrieb am 2009-10-27: >>> Hi, >> i've added the following line to my /etc/hosts: >> permail.uni-muenster.de:25 permail.uni-muenster.de:443 >> so what i want is for freebsd to never use http, but https for that address. unfortunately hosts doesn't seem to support this syntax. >> [snip] >> >> i'm not using a webserver or anything. i'm just a regular user. the point >> is: i often forget to specify https://... for that specific address in >> apps like lynx or firefox. that's why the non-ssl version of that site is >> being loaded. i'd like freebsd to take care of this so even if the app is >> trying to access the non-ssl version it should in fact be redirected to >> the ssl version by freebsd. > > I thought that this is what you were originally after. > > FreeBSD, in itself, can't do this... much like Mac OS or Windows can't > do this. > > Most applications such as Firefox can't even do this (inherently). > > If you are trying to enforce this as a personal/company policy, you will > need to write a 'wrapper' around your application (lynx/firefox) to do > this. > > Note that your example was :25->:443, which implied SMTP over SSL... > > Nonetheless, FreeBSD can't make these decisions inherently (thankfully). > > Steve I think the OP does not have a clear grasp on how the various protocols operate. Evidenced by confusing http with mail services. Yes, I know there is 'web mail', but even web based mail is still a web server. It is up to the server operator to configure the services on the server end of things. Whether its SMTP with SSL/TLS, HTTP/HTTPS, pop3 or imap with SSL, etc., all of these things are made to work at the server end. True enough a client may need to be configured to talk on port 995 for pop3/SSL or port 993 for IMAP/SSL but for the web a client shouldn't need to do anything. The web server operator configures which locations in his URI space should be served up on port 443, and the client's browser should automatically switch to HTTPS based upon this. The OP doesn't seem to understand that he doesn't need to make this happen on his end, at least as far as HTTP/HTTPS goes. If he is actually trying to configure a mail client to talk TLS or SSL to an SMTP server, then he needs to tell the email client software this. E.g., "This connection requires encryption" and whether it is SSL or TLS. Mail servers on port 25 do not use HTTP or HTTPS, but rather SMTP. So it seems as if he is just very confused. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: incorrect info in mysql docs
Chris Whitehouse wrote: > hi, > > I just noticed this at > http://dev.mysql.com/doc/refman/5.1/en/automatic-start.html > > On FreeBSD, startup scripts generally should go in /usr/local/etc/rc.d/. > The rc(8) manual page states that scripts in this directory are executed > only if their basename matches the *.sh shell file name pattern. Any > other files or directories present within the directory are silently > ignored. In other words, on FreeBSD, you should install the mysql.server > script as /usr/local/etc/rc.d/mysql.server.sh to enable automatic startup. That was before the import of the rc.subr subsystem from NetBSD. Sounds like the docs may be a trifle stale. > That's not actually right is it? My mysql is started by > /usr/local/etc/rc.d/mysql-server. rc(8) says *.sh is for older style > startup scripts or for scripts that are to be read into the current shell. > The rc.subr start up system was imported from NetBSD quite some time ago, I think it might have been sometime around the 6.0 to 6.2 time frame. I know this bit me because I had mostly not bothered with executing mergemaster during updates and at some point only scripts with the .sh extension would run. When others told me they did not experience this I got to looking for the culprit and it was that I had failed to update the /etc/rc.d properly with mergemaster to bring in the newly imported rc.subr subsystem. Before the rc.subr import from NetBSD the .sh extension was correct; some other OS's call these "legacy" start up scripts. After the rc.subr import the .sh extension is no longer required for scripts that are written in compliance to the new spec. If you examine a very old start up script from the pre rc.subr days and what is currently in use you will see a slight difference in the way the scripts are constructed internally. The .sh extension "legacy" scripts may still run if marked as executable, but the difference is that they do not contain the rc.subr hooks, and therefore will require the .sh extension for operation, as per the man page you described above. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: PHP5 + fastcgi + apache2.2 ... how to for FreeBSD?
Marc G. Fournier wrote: > > Is there one somewhere? I'm finding *alot* of Debian ones dealing with > their whole apget stuff, but would like to find something that "speaks > normally" :) > [snip] Install your choice of flavor of Apache. Me, I'm using the event-mpm for testing to verify the way to use non-thread safe PHP with a threaded server is FastCGI. Install lang/php5 with various CLI options, as opposed to and instead of mod_php. This is set of options I used: # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for php5-5.2.11 _OPTIONS_READ=php5-5.2.11 WITH_CLI=true WITH_CGI=true WITHOUT_APACHE=true WITHOUT_DEBUG=true WITH_SUHOSIN=true WITH_MULTIBYTE=true WITHOUT_IPV6=true WITHOUT_MAILHEAD=true WITH_REDIRECT=true WITH_DISCARD=true WITH_FASTCGI=true WITH_PATHINFO=true Do not try and use MAILHEAD and SUHOSIN together; that combination is broken. Install the /lang/php5-extensions you require. Currently there seems to be a problem with extension=sqlite.so, and since I don't use/need it's commented out of my extensions.ini. Install www/mod_fcgid from ports. In httpd.conf use: LoadModule fcgid_module libexec/apache22/mod_fcgid.so instead of the usual: LoadModule php5_modulelibexec/apache22/libphp5.so Also, further down in httpd.conf: [...] # This should be changed to whatever you set DocumentRoot to. # [...] # added to enable mod_fcgid AddHandler fcgid-script .fcgi .php SocketPath /var/run/fcgidsock/ IPCConnectTimeout 10 IPCCommTimeout 20 OutputBufferSize 0 # # DirectoryIndex: sets the file that Apache will serve if a directory # is requested. # DirectoryIndex index.html index.php [...] If all went well you should be able to restart Apache and be in business. A phpinfo(); should execute and provide details. Any problems the quickest way to check PHP is to just execute php -v at a shell prompt. If it doesn't segfault it will print out a short descriptive output text. I believe this is better than the usual script based approach you will locate on the web. It starts/spawns PHP as a long running process when Apache starts instead of starting a new CGI each time PHP script is executed. The mod_fcgid is configurable: http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html I believe this project was fairly recently folded into the Apache.org umbrella, but when I began it was separate and standalone. The docs on the Apache site look like they are for the upcoming 2.3 update to 2.2, and there may be discrepancies present. I had originally used the docs from the old site and I don't know if they are even still available. -Mike P.S. - Also, if you need to use Alias they will look like this: Alias /xcache-admin "/usr/local/share/examples/xcache/admin/" #SetHandler None FCGIWrapper /usr/local/bin/php-cgi .php Options ExecCGI Order allow,deny Allow from 192.168.10.2 Deny from none ___ 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: I hate to bitch but bitch I must
PJ wrote: [snip] >> >> > I think you're trying to take the meaning of "should" a little too > far... to keep it simple, and without trying to intellectualize it, it > simply means (and this can change within certain contexts) "normally, it > should work" (in our context, here) but there is no implication of any > warnings or dangers ... the "normally" is implied, the rest you can do > with it as you wish, obviously at your rist... but even then the > interpretation goes too far. As I suggested to Polytropon, in this > particular case the instructions for the implementation of the procedure > are very clear: use on an inactive system or SUM... so where's the > bug... to suggest that it "should work" on an active system is confusing > - if the author thought it important that it wouldl not work on an > active system, perhaps he should have merely said "do not use on an > active system"... that would be consistent and very clear. ;-) Sorry, I'm not totally clear on everything either, but it is clearly contained within a section called 'BUGS'. This should set the context and will affect how the comment should be construed. If it were located anywhere else in the man page the context would be different, this altering the intended meaning or purpose. Content within any 'BUGS' section should not be considered for normal usage of a command, unless it is something you think you can/should try and it is warning you not to do so. It is more of a disclosure of 'gotcha' potential, aka 'here be dragons' or other potential method by which an admin may shoot him/herself in the foot. Just my meager $.02, fwiw -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: phpMyAdmin install stopped in dependency 'libXau-1.0.4'
Kikachi Kozumi wrote: > Hi, > > I tried installing phpMyAdmin in an ezjail created jail already > installed with apache22, mysql and php5 running FreeBSD 7.1-RELEASE > i386 with no X11 (headless). > The port install failed when dependency 'libXau-1.0.4' configure > couldn't find gnome-config: > > ... > checking for XAU... gnome-config: not found > configure: error: Package requirements (xproto) were not met. > ... > > I'm not sure if this issue is specific to my system or is it a ports > issue but I found that libXau-1.0.4 was in the ports tree since > January 2009 so it's less likely to be an issue with the port itself. > > Right now I'm not sure if the required gnome-config is lost from my > system or was never there in the 1st place. What can I do to continue > with phpMyAdmin installation? > > I'm also curious why the phpMyAdmin port requires libX11 libraries to > build while the phpMyAdmin website states that php, mysql and apache > are the requirements for running phpMyAdmin? > [snip] Try placing WITHOUT_X11=yes into /etc/make.conf so it will build without the X related nonsense. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
