Re: Browser
On Wed, 4 Jan 2012 22:18:33 +, RW wrote: On Wed, 4 Jan 2012 12:56:38 -0500 ill...@gmail.com wrote: If you have a few hours, lots of RAM, you'd like to stress- test your system: cd /usr/ports/www/chromium make install Unless things have changed radically that sounds like a bit of an exaggeration. Until about 9 months ago I was building it on a 7 year old single core athlon in 1.5GB with the work-directory on tmpfs. It was still perfectly usable as a desktop. Well, last time I tried to compile one of Firefox's recent versions from ports, it demanded to have access to X during the make stage. That was the point I decided _not_ to continue (as the system in question didn't have X). Maybe I did something wrong, maybe I should have dealt with building options more carefully. But anyway, you type make and the intended web browser wants to access X? From within a UID=0 session? Hmmm... On the other hand, installing google's Chromium browser went through without that kind of annoying trouble. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Browser
On Thu, 5 Jan 2012 12:29:28 +0100
Polytropon wrote:
Well, last time I tried to compile one of Firefox's
recent versions from ports, it demanded to have
access to X during the make stage. That was the
point I decided _not_ to continue (as the system
in question didn't have X). Maybe I did something
wrong, maybe I should have dealt with building
options more carefully.
You turned-on Profile-Guided Optimization, which is off by default.
But anyway, you type make
and the intended web browser wants to access X?
From within a UID=0 session? Hmmm...
pre-extract:
.if defined(WITH_PGO)
@${ECHO} *
@${ECHO} attention **
@${ECHO} *
@${ECHO} To build Firefox with PGO support you need a running X server and
@${ECHO}build this port with an user who could access the X server!
@${ECHO}
@${ECHO} During the build a Firefox instance will start and run some test.
@${ECHO} Do not interrupt or close Firefox during this tests!
@${ECHO} *
@sleep 10
.endif
___
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
Shared Memory allocation in jail
Hi, I am trying to run both postgres and zabbix in the same jail and I am only able to start postgres or zabbix not both of them. I have tuned my sysctl on master host as follow : kern.ipc.shmmax=268435456 kern.ipc.shmall=409600 kern.ipc.semmap=256 security.jail.allow_raw_sockets=1 security.jail.sysvipc_allowed=1 security.jail.enforce_statfs=1 No special tunning on jail host. I have also tunned in rc.conf jail_sysvipc_allow=YES I am still not able to start both at the same time. Any idea ? –– - Grégory Bernard Director - --- www.osnet.eu --- -- Your provider of OpenSource appliances -- –– OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO ___ 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
how to convert bibliography from latex/bibtex to troff/refer?
I've a large bibtex style (.bib) bibliography file. I'd like to convert it to refer(1) format. Are there any tools readily available for this? Many thanks Anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: Shared Memory allocation in jail
Le 5 janv. 2012 à 14:56, bsd a écrit : Hi, I am trying to run both postgres and zabbix in the same jail and I am only able to start postgres or zabbix not both of them. I have tuned my sysctl on master host as follow : kern.ipc.shmmax=268435456 kern.ipc.shmall=409600 kern.ipc.semmap=256 security.jail.allow_raw_sockets=1 security.jail.sysvipc_allowed=1 security.jail.enforce_statfs=1 No special tunning on jail host. I have also tunned in rc.conf jail_sysvipc_allow=YES I am still not able to start both at the same time. Any idea ? Infos here were helpful : http://www.freebsddiary.org/jail-multiple.php I have • re-configure /boot/loader.conf • configured sysctl.conf with various options # rebooted and the issue was solved. –– - Grégory Bernard Director - --- www.osnet.eu --- -- Your provider of OpenSource appliances -- –– OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO ___ 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 –– - Grégory Bernard Director - --- www.osnet.eu --- -- Your provider of OpenSource appliances -- –– OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO ___ 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: Shared Memory allocation in jail
On Thu, Jan 5, 2012 at 8:56 AM, bsd b...@todoo.biz wrote: Hi, I am trying to run both postgres and zabbix in the same jail and I am only able to start postgres or zabbix not both of them. Yeah bro, it bit me in the ass as well ;-) the SysV IPC is common for the whole system. So anything that uses IPC in jails will have to go through this process You have to change the Pg user's id and the chown the Pg files. I use a nomeclature for this and is the last 3 digits of the jail's IP and the original uid. Example The jail on 192.168.101.124 has a Pg user of 70124 for port NATing I use the contrary nomenclature like 12480 is the network port 80 of the same jail in th public IP as 12480. Anyway here is my recipe: pw usermod pgsql -u 70124 pw groupmod pgsql -g 70124 chown -R pgsql /usr/local/pgsql/ chgrp -R pgsql /usr/local/pgsql/ When you run ipcs from the jail You should the see something like the example below, where there is still one Pg on uid 70 but from the jail's perspective it's the pgsql user who now has uid of 70124 Message Queues: T ID KEY MODEOWNERGROUP Shared Memory: T ID KEY MODEOWNERGROUP m 1179648 5432001 --rw--- 70 70 m 1310730 --rw--- 70 70 m 1572866 5432002 --rw--- pgsqlpgsql Semaphores: T ID KEY MODEOWNERGROUP s 1703936 5432001 --rw--- 70 70 s 1703937 5432002 --rw--- 70 70 s 1703938 5432003 --rw--- 70 70 s 1572867 5432004 --rw--- 70 70 s 1572868 5432005 --rw--- 70 70 s 1572869 5432006 --rw--- 70 70 s 1572870 5432007 --rw--- 70 70 s 1179655 5432008 --rw--- pgsqlpgsql s 1179656 5432009 --rw--- pgsqlpgsql s 1179657 5432010 --rw--- pgsqlpgsql s 1179658 5432011 --rw--- pgsqlpgsql s 1179659 5432012 --rw--- pgsqlpgsql s 1179660 5432013 --rw--- pgsqlpgsql s 1179661 5432014 --rw--- pgsqlpgsql Cheers, -- Alejandro Imass ___ 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
portaudit report against web app since updated (by web app itself)
I originally installed WordPress as a port because it was convenient to way to make sure I had all the PHP dependencies. However, I've since updated WordPress internally a number of times, and am now getting portaudit advisories against the original port that was installed. I'd prefer not to get portaudit advisories in this situation. Any recommendations? Thanks, Dale - Transparency with Trust http://www.dalescott.net ___ 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: FBSD-9.0-RC3 Disk 1 ISO Bootable?
Chris wrote: Can't speak for the 64 bit but the I386 does. As for a DVD, look for that at the release. Chris Sent from my HTC. - Reply message - From: Drew Tomlinson d...@mykitchentable.net Date: Wed, Jan 4, 2012 9:23 pm Subject: FBSD-9.0-RC3 Disk 1 ISO Bootable? To: FreeBSD Questions freebsd-questions@freebsd.org I downloaded FreeBSD-9.0-RC3-amd64-disc1.iso ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso and burned the image to CD. However the CD does not boot. Just wanted to confirm that it is supposed to be bootable. Also, is there a DVD version? I don't have many CDs around my house but plenty of DVDs. :) Thanks, Drew ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions Aloha Drew, I made a DVD of i386 10.0 and it works fine too. Haven't tried the 64. Even the new install screen worked the first time for me. Amazing. Da guys did a good job. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ 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: FBSD-9.0-RC3 Disk 1 ISO Bootable?
Drew Tomlinson wrote: On 1/4/2012 8:01 PM, R Skinner wrote: On 01/05/12 13:23, Drew Tomlinson wrote: I downloaded FreeBSD-9.0-RC3-amd64-disc1.iso ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso and burned the image to CD. However the CD does not boot. Just wanted to confirm that it is supposed to be bootable. Also, is there a DVD version? I don't have many CDs around my house but plenty of DVDs. :) Hi Drew, and welcome to FreeBSD. How did you 'burn' the disc? As an iso image (in Windows) you can open any burning program and tell it to burn it as is; you don't need to extract any contents. This is the usual problem if it won't boot. I used the Windows image burning tool on the one that didn't work. However I tried on another PC that had Nero Burning ROM. That one worked. Now I just wish the boot disk had an apparent way to enable ssh so I could install from another PC while browsing the web. [snip] Thanks, Drew I accessed the sshd from the new install screen as an option when I loaded it on the test box. I had to set up the lan manually to first get it up. Then you should be able to use ssh. -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ 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
Apparently conflicting smartctl output
Hello Everyone, I was trying to set up a new gmirror with components ad4 and ad6 in a machine which already has one, but the new gmirror doesn't finish syncing: Jan 4 20:21:27 0.2 isolde kernel: GEOM_MIRROR: Device mirror/gm1 launched (1/1). Jan 4 21:22:32 0.2 isolde kernel: GEOM_MIRROR: Device gm1: rebuilding provider ad6. Jan 4 23:43:50 0.2 isolde kernel: GEOM_MIRROR: Request failed (error=5). ad4[READ(offset=657053450240, length=131072)] Jan 4 23:43:50 0.2 isolde kernel: GEOM_MIRROR: Synchronization request failed (error=5). mirror/gm1[READ(offset=657053450240, length=131072)] I then ran smartctl short and long tests on both ad4 and ad6: # smartctl -l error /dev/ad4 smartctl 5.41 2011-06-09 r3365 [FreeBSD 8.2-STABLE amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Error Log Version: 1 No Errors Logged No errors logged... but then: # smartctl -a /dev/ad4 smartctl 5.41 2011-06-09 r3365 [FreeBSD 8.2-STABLE amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Black Device Model: WDC WD2002FAEX-007BA0 Serial Number:WD-WMAY03714307 LU WWN Device Id: 5 0014ee 0ad99b304 Firmware Version: 05.01D05 User Capacity:2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Device is:In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is:Thu Jan 5 14:34:13 2012 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled [...] SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 1863 1283307620 # 2 Short offline Completed: read failure 90% 1860 1283307620 # 3 Extended offlineCompleted: read failure 90% 1742 1283307620 So, my questions are: - Do I have a bad hard drive (apparently, I do...) - Why are there No Errors Logged by smartctl? -- Janos Dohanics ___ 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: Apparently conflicting smartctl output
On Jan 5, 2012, at 11:42 AM, Janos Dohanics wrote: - Do I have a bad hard drive (apparently, I do...) - Why are there No Errors Logged by smartctl? You've probably got a bad sector on the drive, anyway. The SMART error log is a funny thing governed by various drive's firmware which have quirks. Some of 'em only have a self-test log, but don't store the error log at all; others will only record an error after they've given up trying to remap a failing sector. You snipped too much of the smartctl output to see what the Error logging capability section says-- the full output would be more informative. You almost certainly want to do a full read-scan of the drive via dd if=/dev/ad4 of=/dev/null bs=64k, which will help the drive notice any other failing sectors. Repeat dd if it aborts early with an error (or add conv=noerror, maybe). Regards, -- -Chuck ___ 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]: high load system do not take all CPU time
I get it!!
When one of netisr take 100% of CPU other netisr threads did not get
free CPU time.
http://piccy.info/view3/2444937/25e978a34d1da6b62e4e4602dee53d8b/
In this case network works without any problem
last pid: 23632; load averages: 5.53, 5.76, 5.72up
6+00:09:50 20:37:43
292 processes: 12 running, 265 sleeping, 15 waiting
CPU 0: 9.4% user, 0.0% nice, 18.4% system, 36.1% interrupt, 36.1% idle
CPU 1: 2.4% user, 0.0% nice, 12.2% system, 62.4% interrupt, 23.1% idle
CPU 2: 1.6% user, 0.0% nice, 4.3% system, 85.1% interrupt, 9.0% idle
CPU 3: 1.6% user, 0.0% nice, 3.9% system, 86.3% interrupt, 8.2% idle
Mem: 613M Active, 2788M Inact, 315M Wired, 122M Cache, 112M Buf, 59M Free
Swap: 4096M Total, 30M Used, 4065M Free
PID USERNAME PRI NICE SIZERES STATE C TIME WCPU COMMAND
12 root -72- 0K 160K CPU33 43.4H 100.00% {swi1: netisr
3}
12 root -72- 0K 160K CPU22 28.6H 93.60% {swi1: netisr 1}
12 root -72- 0K 160K CPU11 954:56 50.68% {swi1: netisr 2}
11 root 155 ki31 0K32K RUN 0 96.7H 36.91% {idle: cpu0}
12 root -72- 0K 160K RUN 0 757:29 31.10% {swi1: netisr 0}
11 root 155 ki31 0K32K RUN 1 98.4H 21.44% {idle: cpu1}
12 root -92- 0K 160K WAIT0 17.8H 12.94% {irq256: re0}
11 root 155 ki31 0K32K RUN 2 97.7H 11.08% {idle: cpu2}
11 root 155 ki31 0K32K RUN 3 98.6H 10.16% {idle: cpu3}
13 root -16- 0K32K sleep 0 411:30 4.25% {ng_queue0}
13 root -16- 0K32K sleep 0 411:54 4.20% {ng_queue3}
13 root -16- 0K32K RUN 0 411:05 4.10% {ng_queue1}
13 root -16- 0K32K RUN 2 411:16 3.81% {ng_queue2}
5588 root210 222M 106M select 0 116:59 0.93% {mpd5}
5588 root210 222M 106M select 1 0:00 0.93% {mpd5}
5588 root210 222M 106M select 3 0:00 0.83% {mpd5}
5588 root210 222M 106M select 0 0:00 0.83% {mpd5}
5588 root210 222M 106M select 3 0:00 0.83% {mpd5}
5588 root210 222M 106M select 3 0:00 0.83% {mpd5}
5588 root210 222M 106M select 3 0:00 0.83% {mpd5}
32882 root210 15392K 5492K select 1 313:35 0.63% snmpd
5588 root210 222M 106M select 3 0:00 0.54% {mpd5}
5588 root200 222M 106M select 0 0:00 0.15% {mpd5}
5588 root200 222M 106M select 2 0:00 0.15% {mpd5}
5588 root200 222M 106M select 3 0:00 0.15% {mpd5}
# netstat -W 1 re0
input(Total) output
packets errs idrops bytespackets errs bytes colls
96245 0 0 65271414 115828 0 80031246 0
104903 0 0 70367758 121943 0 85634456 0
102693 0 0 69663018 118800 0 83847075 0
108654 0 0 73776089 125368 0 88487518 0
100216 0 0 68186983 118522 0 80985757 0
94819 0 0 63001720 107334 0 73020011 0
108428 0 0 73849974 127976 0 88674709 0
# vmstat -i
interrupt total rate
irq14: ata0 13841687 26
irq16: ehci0 782489 1
irq23: ehci1 1046847 2
cpu0:timer2140530447 4122
irq256: re0374422787721
cpu1:timer2132118859 4106
cpu3:timer2108526888 4061
cpu2:timer2131292574 4105
Total 8902562578 17147
1 usersLoad 5.87 5.62 5.65 Jan 5 20:41
Mem:KBREALVIRTUAL VN PAGER SWAP PAGER
Tot Share TotShareFree in out in out
Act 737696 12284 315494038552 186192 count
All 946508 19628 540325288672 pages
Proc:Interrupts
r p d s w Csw Trp Sys Int Sof Flt760 cow 38031 total
227 128k 7771 14k 21k 13k 3996 1624 zfod 18 ata0 14
189 ozfod 1 ehci0 16
7.8%Sys 68.3%Intr 4.2%User 0.0%Nice 19.7%Idle 11%ozfod 2 ehci1 23
||||||||||| daefr 4123 cpu0:timer
++ 1439 prcfr 21603 re0 256
184 dtbuf 3275 totfr 4102 cpu1:timer
Namei Name-cache Dir-cache142271 desvn react 4083 cpu3:timer
Callshits %hits % 46214 numvn pdwak 4099 cpu2:timer
26140 24882 95
Re: Realtek RTL8191SEvB Linux driver?
Thursday, 5 January 2012 at 9:04:40 +1000, Da Rock said: On 01/05/12 07:01, Peter Harrison wrote: On 4 Jan 2012, at 01:08, Da Rock wrote: On 01/04/12 10:38, Daniel Feenberg wrote: On Wed, 4 Jan 2012, Da Rock wrote: On 01/04/12 02:10, Daniel Feenberg wrote: On Wed, 4 Jan 2012, Da Rock wrote: On 01/03/12 22:10, Jerry wrote: On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: Don't ndis(4) ndiscvt and ndisgen(8) essentially accomplish what the OP is requesting? See the handbook section 12.8.1.1: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html or the man page for ndiscvt: http://www.gsp.com/cgi-bin/man.cgi?section=8topic=ndiscvt While doing the conversion looks a bit beyond what we would expect of an end-user, it does seem to offer a path for using hardware whose manufacturer does not support FreeBSD. Is there anything beyond licensing issues preventing such drivers from being included in the distribution, or made downloadable in FreeBSD form? Oh yes, it is possible, just not probable :) At http://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=Category:USB almost 800 compatible devices are listed. Not everything, but I have found that a willingness to spend a few dollars on a different card helps immensely in enjoying FreeBSD and Linux. For me at least it is easier to find a compatible card than to write a compatible driver. Indeed :) I did notice that the card in question wasn't on that list. But my own experience with ndiswrapper and wifi cards were far less than satisfactory- the firmware always got in the road. But I may have just been too stupid at the time :) I would also observe that most people involved with computers, whether as users or developers, have little symphathy for people with different needs from the device. This is a great impediment to progress. It is a mistake to assume that because you don't need something, another person's desire for it is illegitimate. In this case, I fully agree that it is an injustice that hardware vendors do not supply FreeBSD drivers, but that does not mean that users requiring such drivers are immoral or of poor character, and therefore to be ignored or insulted. There is little that FreeBSD coders and users can do about that injustice directly, however it is within their power to mitigate it with the NDIS wrapper. If that wrapper allows another user to enter the FOSS world, that will (in the fullness of time) contribute to reforming the vendor. No they are absolutely not of poor character, I agree. Some messages can be misconstrued, though, in that the replies can be terse and more logical than sympathetic. Sometimes it is easier to replace with a different card than flog a dead horse, although a user may take offense for emotional or financial reasons more than logical. Mitigation is a difficult path as I have found personally, although NDIS helps immensely with wired nics (not so much of a problem these days), and I believe Luigi Rizzo's work with the linuxulator and drivers is to be applauded ten fold. It takes a great deal of time though- I put forward the idea when I was still a BSD pup not entirely realising the challenges :) Luigi (and his colleagues) has been working hard ever since to facilitate the more challenging aspects of multimedia drivers (whether or not that had to do with my comments or not, I don't know). Da Rock, I've been using ndis drivers successfully with a Broadcom chip in my Lenovo s10-e since I bought it some years ago - to the extent that I've not yet switched over to the native drivers now available. I didn't find using ndisgen too problematic. Just a case of finding the right driver files and following the manpage. I'd strongly recommend trying it in preference to a usb stick (been there, done that) or buying new hardware - although I'd agree that depending on the model changing a mini-PCI card isn't necessarily that difficult (I changed it t an Intel card in my other Dell laptop some time ago - remember to attach the internal aerial cable!). Make no mistake I'm not being facetious. How did you do it? The biggest problem I had was that there are multiple firmware for different scenarios that are loaded. One for base station mode, one for adhoc, and one more I think... They got in the way of using it correctly. Da Rock, The short answer is, I'm not honestly sure. It was a couple of years ago and it's given absolutely no trouble since - a genuine fit and forget solution. I remember it as being a question of finding and unpacking the right file then using the .sys and .inf files to create a kernel module using ndisgen. Don't recall having any problems with firmware. The only issue I recall was I think to do with converting the .inf file to unicode, but I might have
NFSv4 stronger authentication required error
I've run into a strange problem while trying to mount from FreeBSD 9.0-RC3 to anything I can find using NFSv4. The command I'm using is: #mount -v gorkon:/dustbin /tmp/test This returns the following immediate information on a Debian 6 Linux box: mount: no type was given - I'll assume nfs because of the colon mount.nfs: timeout set for Thu Jan 5 17:37:40 2012 mount.nfs: trying text-based options 'vers=4,addr=[serverip],clientaddr=[cllientaddr]' mount.nfs: mount(2): Permission denied mount.nfs: access denied by server while mounting gorkon:/dustbin There's no log entry that I can find on the server (gorkon), and the following log entry is in my syslog for the debian box: [30082.224612] RPC: server gorkon requires stronger authentication. The NFS server has nfsuserd running, rpcbind running. I've tried to set the share in /etc/exports to use sec=sys (and connect the same way). I don't have Kerberos set up on this network, and I'm not about to start. The Debian NFSv4 servers do connect to a Solaris 10 NFSv4 server, and the FreeBSD box can't mount its own shares over NFS if I force use of nfsv4 (error is mount_nfs: /tmp/test, : Permission denied). A FreeBSD 8.2-RELEASE box won't mount either, same error. The Solaris 10 box also cannot mount the FreeBSD box's mount. The error for this machine is : genunix: [ID 664466 kern.notice] NFS compound failed for server gorkon: error 7 genunix: [ID 532867 kern.warning] WARNING: NFS server initial call to gorkon failed: permission denied. NFSv3 mounts work fine. Anyone know what's going on? ___ 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
ISC-DHCP Web GUIs?
I'm looking for a tool to allow junior admins to lookup and manage an ISC-DHCP server via a web interface. Any recommendations? Basically, they should be able to view lease information, create scopes, make reservations, etc. Thanks, Drew ___ 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: ISC-DHCP Web GUIs?
On Thu, Jan 5, 2012 at 7:52 PM, Drew Tomlinson d...@mykitchentable.netwrote: I'm looking for a tool to allow junior admins to lookup and manage an ISC-DHCP server via a web interface. Any recommendations? Basically, they should be able to view lease information, create scopes, make reservations, etc. I used to use sysutils/webmin for that. Not sure anymore what all features it has on DHCP, but if nothing else you can use it to edit config files from a browser. -- Adam Vande More ___ 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: FBSD-9.0-RC3 Disk 1 ISO Bootable?
Al Plant n...@hdk5.net wrote: I accessed the sshd from the new install screen as an option when I loaded it on the test box. I had to set up the lan manually to first get it up. Then you should be able to use ssh. I take it you either arranged for ssh to accept a direct root login, or added a non-root username. Does the new installer do one of these automatically, or is there more manual configuration involved? ___ 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
9.0-RELEASE amd64 Bricked My Hard Drive
Today I encountered a problem which has me stumped. I downloaded and burned the ISO image for 9.0-RELEASE for amd64. I installed an older IDE hard drive to test the new OS with and did the install. I was very surprised at the (1) the dvd is actually a live CD if you wanted it to be and (2) the installers screens have all been revamped. I can't say for sure if the partitioning part was where it went south on me because I was attempting to setup some additional partitions but the input screens had me confused and I pressed Auto so it took off and made the default paritions. I thought cool, I'll let the install finish and check things out then reinstall later with the partition setup I wanted. Well the install finished and then I attempted to reboot the system but nothing happened. And by that I mean the computer's flash screen would come up and give me the choice to enter the Bios Setup or Boot Menu and that's all. I could not enter the bios setup or the Boot menu. The keyboard was still responding as I could press the CapLock key and toggle the light on and off, but outside of that the computer would not boot. On the advice of some of the techs in #FreeBSD channel I moved the drive over to another computer which was working fine, and the same thing happened. The computer would start up, show me the flash screen to do the Bios setup and then nothing. I put the other drive back in and it worked fine. I tried another computer and the results were the same. Now it gets really wierd. I thought that I could just make this IDE drive a slave and boot with another drive and cleanup the mess. But no matter which computer I chose, and no matter how I setup the Slave/Master drive, as long as this drive which I had installed FreeBSD-9.0-amd64 was in the loop, the computer would lockup at the bios screen. I could not get anything to boot if this drive was in the loop. If I removed it everything was fine. So basically, FreeBSD-9.0-RELEASE bricked an otherwise good 80GB hard drive and I can't seem to recover it. Any suggestions would be appreciated. ___ 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: 9.0-RELEASE amd64 Bricked My Hard Drive
On Jan 5, 2012, at 7:16 PM, Bill Tillman wrote: Today I encountered a problem which has me stumped. I downloaded and burned the ISO image for 9.0-RELEASE for amd64. I installed an older IDE hard drive to test the new OS with and did the install. I was very surprised at the (1) the dvd is actually a live CD if you wanted it to be and (2) the installers screens have all been revamped. I can't say for sure if the partitioning part was where it went south on me because I was attempting to setup some additional partitions but the input screens had me confused and I pressed Auto so it took off and made the default paritions. I thought cool, I'll let the install finish and check things out then reinstall later with the partition setup I wanted. Well the install finished and then I attempted to reboot the system but nothing happened. And by that I mean the computer's flash screen would come up and give me the choice to enter the Bios Setup or Boot Menu and that's all. I could not enter the bios setup or the Boot menu. The keyboard was still responding as I could press the CapLock key and toggle the light on and off, but outside of that the computer would not boot. On the advice of some of the techs in #FreeBSD channel I moved the drive over to another computer which was working fine, and the same thing happened. The computer would start up, show me the flash screen to do the Bios setup and then nothing. I put the other drive back in and it worked fine. I tried another computer and the results were the same. Now it gets really wierd. I thought that I could just make this IDE drive a slave and boot with another drive and cleanup the mess. But no matter which computer I chose, and no matter how I setup the Slave/Master drive, as long as this drive which I had installed FreeBSD-9.0-amd64 was in the loop, the computer would lockup at the bios screen. I could not get anything to boot if this drive was in the loop. If I removed it everything was fine. So basically, FreeBSD-9.0-RELEASE bricked an otherwise good 80GB hard drive and I can't seem to recover it. Any suggestions would be appreciated. Can you get into the BIOS of the original machine *while the bad drive is disconnected* ? If so, I'd try changing the boot options in the BIOS to boot from something like external USB but not from IDE. You'll want to find settings that are geared towards totally eliminating the possibility that the BIOS will scan the drive as a boot device. Depending on your BIOS settings, this may involve changing the Boot Order to not include IDE (or ATA), or if you find it as a numbered boot device, disabling that numbered device (e.g. you see Boot Device 2 and it says IDE, see if it offers Disabled as an option). If you can successfully change your boot options in the BIOS to not scan the IDE channels, ... remember, the drive is still not connected at this point ... then you should be able to connect the drive and get the same result -- the BIOS will tell you there's no bootable devices attached (as you've, hopefully, been able to disable that source of devices from the list of those probed/scanned). At this point, you now need to find something other than IDE to boot from (as you've now disabled that type of device -- including CD/ROM). Hopefully your system is new enough to boot from USB media. Grab DruidBSD Tools disk on another (working) machine ... http://sourceforge.net/projects/druidbsd/files/Druid-0.0.iso/download Descriptions here: http://sourceforge.net/projects/druidbsd/files/ Get yourself a USB thumb drive. NOTE: Say goodbye to what's currently on your thumb drive -- make backups to another machine before you do this. 1. Execute before you attach your thumb drive: sysctl kern.disks 2. Insert thumb drive 3. Execute after you've attached the thumb drive: sysctl kern.disks 4. Identify the newly-available da# device 5. Execute (replacing da# with the appropriate device name) as root (or sudo(8)): dd if=Druid-0.0.iso of=/dev/da# bs=512k conv=sync HINT: You can press Ctrl-T while it's writing the ISO file to the thumb drive to get a (somewhat) helpful progress indication. When finished, you can use your USB thumb drive to do all sorts of rescue-work, including wiping the bad drive with Darik's Boot and Nuke (lol) -- used for secure government wipes -- or Active (R) Kill Disk Free Edition, both on the disk linked-to above. There's also Seagate Disk Utilities, which some of our field engineers found useful (I think it-too has a disk-wiper). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons
Re: 9.0-RELEASE amd64 Bricked My Hard Drive
Bill Tillman btillma...@yahoo.com wrote: ... no matter which computer I chose, and no matter how I setup the Slave/Master drive, as long as this drive which I had installed FreeBSD-9.0-amd64 was in the loop, the computer would lockup at the bios screen. I could not get anything to boot if this drive was in the loop. If you have an oldish machine with a spare PCI slot, you could try plugging in a PCI-IDE controller card and connect the drive to that. Many of the older BIOS won't look for drives on add-in controllers. ___ 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: Apparently conflicting smartctl output
On 01/05/2012 08:56 PM, Chuck Swiger wrote: On Jan 5, 2012, at 11:42 AM, Janos Dohanics wrote: - Do I have a bad hard drive (apparently, I do...) - Why are there No Errors Logged by smartctl? You've probably got a bad sector on the drive, anyway. The SMART error log is a funny thing governed by various drive's firmware which have quirks. Some of 'em only have a self-test log, but don't store the error log at all; others will only record an error after they've given up trying to remap a failing sector. You snipped too much of the smartctl output to see what the Error logging capability section says-- the full output would be more informative. You almost certainly want to do a full read-scan of the drive via dd if=/dev/ad4 of=/dev/null bs=64k, which will help the drive notice any other failing sectors. Repeat dd if it aborts early with an error (or add conv=noerror, maybe). Regards, Hi, I have had this with a drive and multiple read errors would not remap the sector. With write errors the sector would be remapped. This was a new Samsung laptop drive though, not a Western Digital. To get the sector remapped I had to fully write the drive and it was ok after that. For now no bad sectors have been showing up Disclaimer: http://www.ose.nl/email ___ 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
