Re: why is this script failing?
On Wed, 2008-07-16 at 11:42 +1000, Norberto Meijome wrote:
> you can always do
>
> find /tmp/kde-*/ -iname "*wav" -print0 | xargs -0 rm -vf
>
> the advantage over doing using rm * or for * in ... is that if you
> have LOTS of files, the expanded list of files may be too much. find |
> xargs will deal with each file in turn. ( -print0 and -0 is to use
> NULL char as a list delimiter instead of space... ).
>
Note that - as highlighted in previous discussions on the fbsd lists re
the use of xargs with find - find is eminently capable of handling large
argument lists and filenames_with_spaces with its own -exec primary:
find /tmp/kde-*/ -iname "*wav" -exec rm -vf {} \;
to exec rm for each file individually, or:
find /tmp/kde-*/ -iname "*wav" -exec rm -vf {} \+
to exec rm for multiple files at once.
Piping to xargs in this case is unnecessary.
Wayne
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Repeating Mail
Hi guys, Some of my mail users receive repeating mail. I am using sendmail and my user uses MS Outlook to send/receive. Is there any way to solve this problem? Thank you. Best regards, alyd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
need help with boot forth
Colleagues, I am setting up a jumpstart server for networked FreeBSD installation (tftp only). My /tftpboot/boot/loader.rc is rather simple: load /boot/kernel load /boot/acpi.ko load -t mfs_root /boot/mfsroot set vfs.root.mountfrom="ufs:/dev/md0c" boot It works fine with a custom kernel (with statically compiled in device hints). However, I would like to use a stock kernel, so I need to tftp download device.hints and set the kernel environment accordingly. Could you please help me with the loader.rc code that will do that? Thank you in advance. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: why is this script failing?
On Jul 15, 2008, at 4:50 PM, Gary Kline wrote: On Tue, Jul 15, 2008 at 02:02:24PM -0500, David Kelly wrote: Is probably best to postpone wildcard expansion until the last moment because if any of the filenames contain spaces the space will probably cause a break between arguments. The first time the wildcard expands to a filename with a space the space will be escaped. But the second time you use it that escape is lost. So its best to expand it in the place its needed. thanks for this clarification! until yesterday, whe you mmentioned blanks[whitespace], as id a song title, i hadn't tought about songs like "Not Ready to Make Nice.ogg" e.g. I am not sure why these players store the song in wav format without deleting the files, but when my limited /tmp is full, certain aps fail mysteriously. with a fwdozen more line of code they could at least fail more gracefully. You might consider adding something like setenv TMPDIR /home/dkelly/tmp setenv TMP /home/dkelly/tmp to your ~/.cshrc (or whatever appropriate for the shell you are using). This moves "/tmp" for cooperative applications into private space where you might have more room. Of course KDE is probably starting via a different route. Or maybe not. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: why is this script failing?
On Tue, 15 Jul 2008 14:50:24 -0700
Gary Kline <[EMAIL PROTECTED]> wrote:
> thanks for this clarification! until yesterday, whe you
> mmentioned blanks[whitespace], as id a song title, i hadn't
> tought about songs like "Not Ready to Make Nice.ogg" e.g.
> I am not sure why these players store the song in wav format
> without deleting the files, but when my limited /tmp is full,
> certain aps fail mysteriously. with a fwdozen more line of code
> they could at least fail more gracefully.
you can always do
find /tmp/kde-*/ -iname "*wav" -print0 | xargs -0 rm -vf
the advantage over doing using rm * or for * in ... is that if you have LOTS of
files, the expanded list of files may be too much. find | xargs will deal with
each file in turn. ( -print0 and -0 is to use NULL char as a list delimiter
instead of space... ).
_
{Beto|Norberto|Numard} Meijome
"A problem cannot be solved with the same type of thinking that created it."
Albert Einstein
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm whacked?
That's it! I have an ATI Radion on this box. The screen res is 1280x800 which is not supported by vesa. I dug up my old backup xorg.conf file and realized I had set "ati" as the driver and was full of good experiences with it. I had just forgotten. Also, for the record, this fix also fixed my linux-firefox/linux-flashplugin issue. much appreciation. == If not us, who? And if not now, when? Ronald Reagan --- On Sun, 7/13/08, Luke Dean <[EMAIL PROTECTED]> wrote: > From: Luke Dean <[EMAIL PROTECTED]> > Subject: Re: aterm whacked? > To: "Neil Short" <[EMAIL PROTECTED]> > Cc: freebsd-questions@freebsd.org > Date: Sunday, July 13, 2008, 11:56 AM > On Sat, 12 Jul 2008, Neil Short wrote: > > > I just mem-wiped my laptop and am in the process of > installing > > everything after. > > > > I have several issues (linux-firefox with linux-flash > plugin crashes on > > sites with flash), not the least of which is aterm > doesn't seem to > > behave very well. > > > > When I run aterm I get: > > > > $ aterm > > aterm has encountered the following problem > interacting with X Windows : > > Request: 64,Error: 8(BadMatch (invalid > parameter attributes)) > > in resource: 0x14D > > aterm has encountered the following problem > interacting with X Windows : > > Request: 64,Error: 8(BadMatch (invalid > parameter attributes)) > > in resource: 0x14D > > aterm has encountered the following problem > interacting with X Windows : > > Request: 64,Error: 8(BadMatch (invalid > parameter attributes)) > > in resource: 0x14D > > > > etc. > > > > Transparency doesn't work right either - which I > see is the greatest > > attraction to aterm. > > > > Any ideas? > > I had this problem with an old Sony Vaio about a year ago. > Xorg detected that the correct video driver to use was > "neomagic". > Whatever automatic configuration method I was using at the > time decided > that I should be running with 32-bit color depth in > xorg.conf. > It turns out that the neomagic driver doesn't support > color depth greater > than 24-bits... > > This misconfiguration worked well enough until something > like aterm tried > to use transparency, then it would complain about the > "BadMatch", > referring to the color depth that the driver supported > versus the color > depth that X was configured for, presumably. > > I found two solutions. One was to edit the > "Screen" section of xorg.conf > to remove the entry with DefaultDepth 32. The other was to > edit xorg.conf > to use the vesa driver instead of the neomagic driver. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't run WindowMaker. Fatal server error:
> I have recompiled the kernel and no change what so ever. > I have also upgraded windowmaker to windowmaker-0.92.0_4. > Current Xorg is xorg-7.3_2 > > > On 06-juil.-08, at 21:31, Luke Dean wrote: > >> >> >> On Sun, 6 Jul 2008, Pedro Alves wrote: >> >>> Hello >>> >>> I have a serious problem with windowmaker. >>> Every time I configure .xinitrc to launch wmaker, the server aborts >>> >>> here what I get: >>> >>> Fatal server error: >>> Caught signal 11. Server aborting >>> >>> xnit: connection to X server lost. >>> wmaker warning: got signal1-exiting... >>> >>> >>> >>> >>> So... What to do, as I don't find any information concerning this >>> problem. >>> >>> I am running FreeBSD 7.0 >>> One week old cvs ports upgrade. >> >> You may find clues in the Xorg log. >> /var/log/Xorg.0.log >> >> When I have this problem, or just about any X-related problem, it >> means I need to go rebuild my video driver. > > -- It is very important to say that if instead of windowmaker I define in .xnitrc to execute for instance icewm as window manager I have not problems at all except that I can't run gnustep applications. That another issue I face. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic
David Gurvich wrote: Can you disable smp? I see reports on the same issue with 6.3 that imply it may be related to smp. You are spreading FUD :-) There is no information provided upon which to base that conclusion. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: why is this script failing?
On Tue, Jul 15, 2008 at 02:02:24PM -0500, David Kelly wrote:
> On Tue, Jul 15, 2008 at 11:35:00AM -0700, Gary Kline wrote:
> > On Tue, Jul 15, 2008 at 07:37:02AM +0200, Wojciech Puchar wrote:
> > > >
> > > > why is this script not finding them?
> > > >
> > > >
> > > >wav=/tmp/kde-kline/\*wav\*
> > >
> > > why you put \ before *
> >
> > to allow the shell to catch various formsof strings with "wav"
> > embedded.
>
> I questioned that escape earlier.
>
> Without the \ escape the variable ${wav} will contain all the files
> matching the pattern. But with the escape it will literally be
> "/tmp/kde-kline/*wav*". Wildcard expansion doesn't occur until later
> when Gary does something like this:
>
> rm ${wav}
>
> which is processed as if he had just now typed:
>
> rm /tmp/kde-kline/*wav*
>
> while without the escape it might appear like this:
>
> rm /tmp/kde-kline/file1.wav /tmp/kde-kline/file2.wav
>
> Is probably best to postpone wildcard expansion until the last moment
> because if any of the filenames contain spaces the space will probably
> cause a break between arguments. The first time the wildcard expands to
> a filename with a space the space will be escaped. But the second time
> you use it that escape is lost. So its best to expand it in the place
> its needed.
>
thanks for this clarification! until yesterday, whe you
mmentioned blanks[whitespace], as id a song title, i hadn't
tought about songs like "Not Ready to Make Nice.ogg" e.g.
I am not sure why these players store the song in wav format
without deleting the files, but when my limited /tmp is full,
certain aps fail mysteriously. with a fwdozen more line of code
they could at least fail more gracefully.
-g
> --
> David Kelly N4HHE, [EMAIL PROTECTED]
>
> Whom computers would destroy, they must first drive mad.
--
Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Wireless network with wpa
On Tuesday 15 July 2008 19:41:29 David Gurvich wrote: > Hello, > I would like to know what might be happening with a particular network > configuration. Wireless router using wpa, wired router provides dhcp > and connects to DSL modem. The wireless card involved is a mini-pci > intel 2100 using the if_ipw driver. I could not get this card working > at all with 6.3, though it seems to work with 7. > > From time to time, the ability to resolve the address of the wired > router disappears along with DNS resolution. If I 'wpa_cli reassociate' > it comes back. DHCP is done after associating, which is the only thing that comes to mind that could cause this "reappearance of DNS", since ping goes through ok. How are you doing DNS? Is there a local named running or is /etc/resolv.conf pointing directly to the nameserver? Where is that nameserver? On the wired network? Can you ping the nameserver or anything else on the wired network when this happens? Is there any change in /etc/resolv.conf after reassociation? -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Connection Problems After Upgrade
I upgraded 5 servers yesterday from FreeBSD 7.0 p1 to p3. Now I'm having connection problems on them. I see log entries like: Jul 15 11:24:27 hostname ntpd[49394]: sendto(192.168.0.1): Network is unreachable Jul 15 12:02:56 hostname ntpd[49394]: sendto(192.168.0.1): Network is unreachable Jul 15 13:28:17 hostname ntpd[49394]: sendto(192.168.0.1): Network is unreachable Jul 15 13:45:21 hostname ntpd[49394]: sendto(192.168.0.1): Network is unreachable If I leave an ssh session idle, I get: Read from remote host hostname.more.net: Connection reset by peer I didn't have any problems before upgrading to p3. Any ideas? Thanks, Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic
Can you disable smp? I see reports on the same issue with 6.3 that imply it may be related to smp. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic
Michael Grant wrote: I have been having panics on one of my machines, roughly every week or so. I was running 6.3 pre-release and then I updated to 6.3 p2 and I still have the panic, here's the message that appears on the console: panic: kmem_kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 06 fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x20:0xc06c5a5a stack pointer = 0x28:0xe6ea49ec frame pointer = 0x28:0xe6ea4a00 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 14 (swi1: net) trap number = 12 Is this possibly a hardware problem? Yes, but who can say? :) To complete your bug report please submit a backtrace. See the developers handbook for details. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panic
I have been having panics on one of my machines, roughly every week or so. I was running 6.3 pre-release and then I updated to 6.3 p2 and I still have the panic, here's the message that appears on the console: panic: kmem_kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 06 fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x20:0xc06c5a5a stack pointer = 0x28:0xe6ea49ec frame pointer = 0x28:0xe6ea4a00 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 14 (swi1: net) trap number = 12 Is this possibly a hardware problem? Michael Grant ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic: spin lock held too long when booting
Mike Clarke wrote: On Tuesday 15 July 2008, Kris Kennaway wrote: Mike Clarke wrote: I'm getting frequent panics due to spin lock held too long when booting my recently built 6.3 system with an Athlon 4850e dual core processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and nForce 430 chipsets). [snip] You should add options WITNESS also and this will probably generate additional debugging and/or a panic before the error occurs. OK, done that. The first reboot came up OK, sods law being what it is the next few boots will be clean and I'll have to wait a while for results from the next panic but in the meantime here's the messages generated by WITNESS for the clean boot: curlew:/home/mike% grep WITNESS /var/run/dmesg.boot WARNING: WITNESS option enabled, expect reduced performance. WITNESS: spin lock scrlock not in order list WITNESS: spin lock intrcnt not in order list WITNESS: spin lock ctl.rm_mtx not in order list WITNESS: spin lock dev.rm_mtx not in order list ... do they give any clues? Not really, they are basically just advisory in this context (and fixed in later releases AFAIK). Unfortunately WITNESS can drastically change timing of events which can mask this kind of problem. If you can afford it, keep trying with it enabled for a while. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: options WITNESS and locks
Yony Yossef wrote: Problem solved :-) Thank you very much for your patience Kris.. Glad to help! Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: options WITNESS and locks
Problem solved :-) Thank you very much for your patience Kris.. On Tue, Jul 15, 2008 at 5:14 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote: > Yony Yossef wrote: > >> >>Something is still unclear. All my locks are MTX_DEF type, which >>means >>sleepable, including the one specified in the crash report >>(MTNIC state >>semaphore). >>This crash happens when I try to call bus_resource_alloc_any for >>a SYS_REQ >>which is trying to obtain the second lock (ACPI root bus). How >>come my >>MTX_DEF lock is being treated as as non-sleepable? >> >> >>MTX_DEF locks *are* non-sleepable :-) >> >>Kris >> >> Good news :-) >> Yet the documentation is confusing me: >> man pages say: >> MTX_DEFDefault mutexes will always allow the current thread to be >>suspended to avoid deadlock conditions against >> interrupt >>threads. The implementation of this lock type may spin >>for a while before suspending the current thread. >> and in mutex.h: >> /* >> * Mutex types and options passed to mtx_init(). MTX_QUIET and MTX_DUPOK >> * can also be passed in. >> */ >> #define MTX_DEF 0x /* DEFAULT (sleep) lock */ >> #define MTX_SPIN 0x0001 /* Spin lock (disables interrupts) */ >> #define MTX_RECURSE 0x0004 /* Option: lock allowed to recurse */ >> #define MTX_NOWITNESS 0x0008 /* Don't do any witness checking. */ >> #define MTX_NOPROFILE 0x0020 /* Don't profile this lock */ >> What does the "DEFAULT (sleep) lock" comment near MTX_DEF means? >> And which ones are sleepable?.. I guess I'm missing something here. >> > > "sleep mutex" means that the mutex holder may be put to sleep by the kernel > while the mutex is held by another process (if the lock holder is running > then it will spin, though). It is in contrast to "spin" mutexes that always > spin forever while the lock is held, even when it might be inefficient for > them to do so because the lock holder is no longer running after the CPU > context switched to another process before it released the lock. > > This describes the behaviour of the mutex while it is waiting to acquire a > lock. > > "sleepable" vs "non-sleepable" locks means what it is legal for your code > to do while holding a mutex and doesn't relate to the internal > implementation of the lock. > > This describes what it is legal for your code to do once it has acquired > the lock. > > Kris > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic: spin lock held too long when booting
On Tuesday 15 July 2008, Kris Kennaway wrote: > Mike Clarke wrote: > > I'm getting frequent panics due to spin lock held too long when > > booting my recently built 6.3 system with an Athlon 4850e dual core > > processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and > > nForce 430 chipsets). [snip] > You should add options WITNESS also and this will probably generate > additional debugging and/or a panic before the error occurs. OK, done that. The first reboot came up OK, sods law being what it is the next few boots will be clean and I'll have to wait a while for results from the next panic but in the meantime here's the messages generated by WITNESS for the clean boot: curlew:/home/mike% grep WITNESS /var/run/dmesg.boot WARNING: WITNESS option enabled, expect reduced performance. WITNESS: spin lock scrlock not in order list WITNESS: spin lock intrcnt not in order list WITNESS: spin lock ctl.rm_mtx not in order list WITNESS: spin lock dev.rm_mtx not in order list ... do they give any clues? -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ADSL & Lease Lines
Unfortunately one of my offices is located in a real nasty location as far as internet connectivity is concerned, up until now I've been using a standard ADSL connection but an upload of 512Kbs is now a huge problem for my remote users. With this in mind (and budgetary issues) I have no option but to go for an E1 carrier (2048Kbit) BTW E1 is 2000Kbit/s (=2048000bits/second) Well, this fixes my real _slow_ upload but reduces my download by about 5Mbit. Initially I was planning on having the lease line purely for my how do you download 5Mbit/s through 2Mbit/s E1? Would it be possible to employ some FreeBSD wizardry to affectively bond the lease line with the ADSL connection? I know this can be done you can't "bond" two different links with 2 different IP addresses. you can do bonding only if your provider can do (like to do) the same. but you can simply make somehow smart firewall rules with "forward" command. it's how it's called in ipfw (fwd IP number), no idea about pf. for example - make proxy server with squid, set tcp_outgoing_address to your ADSL's IP, and make firewall rules to forward all going from ADSL's IP through ADSL modem, while having default route through E1, and all other services on E1. that's exactly what i do for 300 people LAN - use expensive symmetric connections for everything except WWW browsing - which goes through ADSL ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: why is this script failing?
On Tue, Jul 15, 2008 at 11:35:00AM -0700, Gary Kline wrote:
> On Tue, Jul 15, 2008 at 07:37:02AM +0200, Wojciech Puchar wrote:
> > >
> > > why is this script not finding them?
> > >
> > >
> > >wav=/tmp/kde-kline/\*wav\*
> >
> > why you put \ before *
>
> to allow the shell to catch various formsof strings with "wav"
> embedded.
I questioned that escape earlier.
Without the \ escape the variable ${wav} will contain all the files
matching the pattern. But with the escape it will literally be
"/tmp/kde-kline/*wav*". Wildcard expansion doesn't occur until later
when Gary does something like this:
rm ${wav}
which is processed as if he had just now typed:
rm /tmp/kde-kline/*wav*
while without the escape it might appear like this:
rm /tmp/kde-kline/file1.wav /tmp/kde-kline/file2.wav
Is probably best to postpone wildcard expansion until the last moment
because if any of the filenames contain spaces the space will probably
cause a break between arguments. The first time the wildcard expands to
a filename with a space the space will be escaped. But the second time
you use it that escape is lost. So its best to expand it in the place
its needed.
--
David Kelly N4HHE, [EMAIL PROTECTED]
Whom computers would destroy, they must first drive mad.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mounting WD external USB disk
On Tue, 15 Jul 2008 12:42:13 -0500, Sam Fourman Jr. <[EMAIL PROTECTED]> wrote: I have access to a WD MyBook, and I also can not get it to work. the error is the same da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 152627MB (312581808 512 byte sectors: 255H 63S/T 19457C) SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ata0 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present GEOM_LABEL: Label for provider da0s1 is msdosfs/My Book. --^^^ http://www.freebsd.org/gnome/docs/halfaq.html#q3 -- CAVEAT: If you are using glabel (GEOM labels), volume labels MUST NOT contain spaces. This will break hal's volume parsing code, and could lead to crashes. -- Cheers, Mezz Trying to mount root from ufs:/dev/ad4s1a bridge0: Ethernet address: 52:2a:c4:5a:c0:d0 tap0: Ethernet address: 00:bd:7d:42:00:00 tap0: promiscuous mode enabled fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 pid 1418 (hald), uid 560: exited on signal 11 has anyone ever used a larger mybook on FreeBSD Sam Fourman Jr. -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
freebsd dvbusb
Hi, I recently bought a Gigabyte U7000 usb 2.0 dvb-t dongle. According to linuxtv.org it should work under linux (I know it is not freebsd...) with the dib0700 firmware (http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices#DiB0700_USB2.0_DVB-T_devices). But under fbsd it doesn't... I'm running : bsdaddict# uname -a FreeBSD bsdaddict 7.0-STABLE FreeBSD 7.0-STABLE #3: Thu May 29 20:47:26 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BENI-DBSD i386 Following the instructions on http://raaf.atspace.org/dvbusb/ I downloaded, compiled and kldload'ed the sources .ko with no problem : bsdaddict# kldstat | grep dvb 181 0xc7fe4000 7000 dvbusb.ko But then checking dmesg : ugen0: on uhub4 This is all I get. No dvbusb0 is coming up. When I try to download the firmware (I tried 2 of them, the dibusb and dib0700) I get (result is the same when doing it as root or as user member of the operator-group) : bsdaddict# dd if=/boot/modules/dvb-usb-dibusb-6.0.0.8.fw of=/dev/ugen0 bs=1m dd: /dev/ugen0: Operation not supported by device 0+1 records in 0+0 records out 0 bytes transferred in 0.000126 secs (0 bytes/sec) bsdaddict# bsdaddict# dd if=/boot/modules/dvb-usb-dib0700-03-pre1.fw of=/dev/ugen0 bs=1m dd: /dev/ugen0: Operation not supported by device 0+1 records in 0+0 records out 0 bytes transferred in 0.000184 secs (0 bytes/sec) bsdaddict# Any pointers on how to get this dvb-t stick working under freebsd 7.0 ? Thanks a lot for any help ! -- Beni. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: why is this script failing?
On Tue, Jul 15, 2008 at 07:37:02AM +0200, Wojciech Puchar wrote: > > > > why is this script not finding them? > > > > > >wav=/tmp/kde-kline/\*wav\* > > why you put \ before * > to allow the shell to catch various formsof strings with "wav" embedded. -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mounting WD external USB disk
I have access to a WD MyBook, and I also can not get it to work. the error is the same da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 152627MB (312581808 512 byte sectors: 255H 63S/T 19457C) SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ata0 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present GEOM_LABEL: Label for provider da0s1 is msdosfs/My Book. Trying to mount root from ufs:/dev/ad4s1a bridge0: Ethernet address: 52:2a:c4:5a:c0:d0 tap0: Ethernet address: 00:bd:7d:42:00:00 tap0: promiscuous mode enabled fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 pid 1418 (hald), uid 560: exited on signal 11 has anyone ever used a larger mybook on FreeBSD Sam Fourman Jr. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Wireless network with wpa
Hello, I would like to know what might be happening with a particular network configuration. Wireless router using wpa, wired router provides dhcp and connects to DSL modem. The wireless card involved is a mini-pci intel 2100 using the if_ipw driver. I could not get this card working at all with 6.3, though it seems to work with 7. From time to time, the ability to resolve the address of the wired router disappears along with DNS resolution. If I 'wpa_cli reassociate' it comes back. The most confusing issue is that the connection to the wireless router is never lost. I can always ping the wireless router and access the control panel with a web browser. A computer connected directly to the wired router had issues with the ethernet using FreeBSD and Linux, but not Solaris. An apple computer using Gentoo/OSX had no issues with either wired or wireless. I cannot replicate the issue, it simply recurs through use. OSX had no problem with either wpa or wired connection. Solaris only had issues with unsupported hardware. Linux on the x86 box had problems with wired connections, but none on the powermac. I suspect the 3c905b card in the x86 card may be a problem, though there have been no issues since Solaris had been installed. Any ideas on the problem are welcome. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: df shows negative free percentage
Jeff Dickens wrote: I just noticed one of my FreeBSD 6.2 systems showing "-0%" free in /tmp. If I copy a file to it, it shows a sensible percentage free, but then reverts to "-0%" when I delete that file. Any idea what's going on here? FreeBSD 6.2-RELEASE (GENERIC) #0: Fri Jan 12 10:40:27 UTC 2007 Loon loon# df Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/da0s1a507630 38436 428584 8%/ devfs 1 1 0 100%/dev /dev/da0s1e507630 -20 467040-0%/tmp /dev/da0s1f 5366090 1573304 336350032%/usr /dev/da0s1d 1255886 356994 79842231%/var loon# loon# cp /usr/local/kits/vmware-freebsd-tools.tar.gz /tmp loon# df Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/da0s1a507630 38446 428574 8%/ devfs 1 1 0 100%/dev /dev/da0s1e507630 10444 456576 2%/tmp /dev/da0s1f 5366090 1573304 336350032%/usr /dev/da0s1d 1255886 356994 79842231%/var loon# rm /tmp/vmware-freebsd-tools.tar.gz loon# df Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/da0s1a507630 38446 428574 8%/ devfs 1 1 0 100%/dev /dev/da0s1e507630 -20 467040-0%/tmp /dev/da0s1f 5366090 1573304 336350032%/usr /dev/da0s1d 1255886 356994 79842231%/var loon# umount and fsck -f the filesystem Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
df shows negative free percentage
I just noticed one of my FreeBSD 6.2 systems showing "-0%" free in /tmp. If I copy a file to it, it shows a sensible percentage free, but then reverts to "-0%" when I delete that file. Any idea what's going on here? FreeBSD 6.2-RELEASE (GENERIC) #0: Fri Jan 12 10:40:27 UTC 2007 Loon loon# df Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/da0s1a507630 38436 428584 8%/ devfs 1 1 0 100%/dev /dev/da0s1e507630 -20 467040-0%/tmp /dev/da0s1f 5366090 1573304 336350032%/usr /dev/da0s1d 1255886 356994 79842231%/var loon# loon# cp /usr/local/kits/vmware-freebsd-tools.tar.gz /tmp loon# df Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/da0s1a507630 38446 428574 8%/ devfs 1 1 0 100%/dev /dev/da0s1e507630 10444 456576 2%/tmp /dev/da0s1f 5366090 1573304 336350032%/usr /dev/da0s1d 1255886 356994 79842231%/var loon# rm /tmp/vmware-freebsd-tools.tar.gz loon# df Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/da0s1a507630 38446 428574 8%/ devfs 1 1 0 100%/dev /dev/da0s1e507630 -20 467040-0%/tmp /dev/da0s1f 5366090 1573304 336350032%/usr /dev/da0s1d 1255886 356994 79842231%/var loon# ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ADSL & Lease Lines
> Date: Tue, 15 Jul 2008 17:08:24 +0100> From: [EMAIL PROTECTED]> To: > freebsd-questions@freebsd.org> Subject: ADSL & Lease Lines> QUESTION> > > > > Would it be possible to employ some FreeBSD wizardry to affectively bond> the > lease line with the ADSL connection? I know this can be done> through Cisco > routers but again budgetary issues are the limiting> factor. > > Any help > will be gratefully received. > > TIA> > Nikki> take a look at pfSense.com. its based on FreeBSD and most users find it as reliable as an enterprise level router. -Sean___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OT-ish: fedora->crash->single user fsck; FreeBSD->crash->smooth recovery
>> Ok, I'll quit ranting and actually ask a question: The real big thing >> that suprised me (about Fedora), is that every damn time it crashes, I >> have to sit through 20 minutes of fsck when it boots, then it cries, >> gags, and throws me into a root console to run fsck again, manually, >> for 20 more minutes. I'm thinking about symlinking fsck to a rather >> dirtier word on the Fedora box. > > yes it is normal. > > linux filesystem works like in -o async mode, is just caches what it have to > write and write whenever it likes at whatever sequence. > > in linux it is always presented as feature not bug. > > > another very stupid thing is TOO delayed writes, i mean linux simply caches > things as long as there are free memory then just starts lots of writes at > once efectively halting the system for a while. > Ok, so you are saying the write caching is radically different on FreeBSD than what I know of Win/Lin? Or is the timeout to flush just some really small period like 100mS? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ADSL & Lease Lines
Hello everybody I've been using FreeBSD servers to power my DMZ security zones for years; the security zones generally includes things like PF firewalls, SMTP servers, DNS and NAT gateways etc. From a security standpoint BSD is the BEST! Anyway, onto my question: OUTLINE Unfortunately one of my offices is located in a real nasty location as far as internet connectivity is concerned, up until now I've been using a standard ADSL connection but an upload of 512Kbs is now a huge problem for my remote users. With this in mind (and budgetary issues) I have no option but to go for an E1 carrier (2048Kbit) Well, this fixes my real _slow_ upload but reduces my download by about 5Mbit. Initially I was planning on having the lease line purely for my servers and remote users and having all desktop users browse the net using an ADSL connection but this would give me two independent connections to manage. QUESTION Would it be possible to employ some FreeBSD wizardry to affectively bond the lease line with the ADSL connection? I know this can be done through Cisco routers but again budgetary issues are the limiting factor. Any help will be gratefully received. TIA Nikki ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Core(TM)2 Quad and TOP output
#cd /usr/src/sys/i386/config/GENERIC
#cp -Rp GENERIC mykernelname
edit my kernel
#vim mykernelname
ident GENERIC
change
ident mykernelname
and add
# To make an SMP kernel, the next two lines are needed
options SMP # Symmetric MultiProcessor Kernel
device apic# I/O APIC
secondly
[EMAIL PROTECTED] /usr/src/sys/i386/conf]# config mykernelname
[EMAIL PROTECTED] /usr/src/sys/i386/compile/mykernelname]# make depend && make
&& make install
finnally
mergemaster
and reboot
On Tue, Jul 15, 2008 at 11:23 AM, Jos Chrispijn <[EMAIL PROTECTED]> wrote:
> Scott Bennett wrote:
>
>> That is not necessary either. Take a look in /sys/i386/conf or
>> /sys/amd64/conf, depending upon which you are using. Then do:
>>
>> # config SMP
>> # cd ../compile/SMP
>> # make cleandepend && make depend && make && make install
>> # shutdown -r now
>>
>> That should take care of it for you. /sys/{i386,amd64}/conf/SMP adds
>> "options SMP" and then includes GENERIC.
>>
>>
> Thanks for sharing; will put this in my FreeBSD user bible!
>
> -- Jos
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> [EMAIL PROTECTED]"
>
--
Share now a pigeon's flight
Bluebound along the ancient skies,
Its women forever hair and mammal,
A Mediterranean town may arise
If you rip apart a pigeon's heart.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7 , Rebooting....
On Tue, Jul 15, 2008 at 10:13 AM, Marcel Grandemange <[EMAIL PROTECTED]> wrote: > I have just setup a FreeBSD server one a machine. > > What happens is the machine seems to suddenly reboot during compiling > ports.. Which ports, or are you having problems with all the ports you are trying to build? <...snip...> It would also be helpful if you can reliably reproduce this panic, and then produce a backtrace. Read the Handbook for the how-to on that. Sorry to hear that your box is panicking, SC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: difference between loading kernel module during boot and after boot manually?
On Tuesday 15 July 2008 15:20:19 Vincent Barus wrote: > On Mon, Jul 14, 2008 at 10:58 PM, Mel > > <[EMAIL PROTECTED]> wrote: > > On Monday 14 July 2008 20:29:07 Vincent Barus wrote: > >> On Tue, Jul 8, 2008 at 8:11 PM, Mel > >> <[EMAIL PROTECTED]> > > > > wrote: > >> > On Tuesday 08 July 2008 16:48:26 Vincent Barus wrote: > >> >> does anyone have an idea what's the difference or what _could_ be the > >> >> difference on loading a kernel module during boot or manually? > >> > > >> > There's one major difference. File systems aren't mounted at loader > >> > stage, so any reference to modules/libraries that exist on a different > >> > partition, will fail. > >> > >> Right now i have only one partition and the same problem occurs. Other > >> modules e.g. for sound or the nvidia module work as a charm. > >> So I think that's not the only difference. > >> I can live with a module loaded at the end of the boot process/after > >> login but I don't think that's the real solution. > > > > Hmm, I can only guess here. Is the machine booting to xorg? As in, is the > > nvidia card actually initialized, not just in VGA mode? If so, does it > > work when it stays in console mode and/or when nvidia.ko is removed from > > the loaded modules? > > > > -- > > Mel > > > > Problem with today's modular software: they start with the modules > >and never get to the software part. > > I start X manually after login. Which comes first? Your own script that loads if_re or Xorg being loaded. The possibility I'm trying to rule out, is that the nvidia module loading it's agp driver and nvidiactl module, fixes your if_re issues, because they take up that memory space. So, to (dis)prove this: * in /boot/loader.conf and/or kernel config, no mention of if_re * in /boot/loader.conf load nvidia.ko * wait till machine boots * do not start X, instead from root console kldload if_re * Expected result: failing to load * start X * kldload if_re * Expected result: successful load -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7 , Rebooting....
On Tue, 15 Jul 2008 16:13:22 +0200
"Marcel Grandemange" <[EMAIL PROTECTED]> wrote:
> Any input?
- check / swap your memory (memtest86 )
- bad power ( unstable / not enough )
- not enough cooling.
_
{Beto|Norberto|Numard} Meijome
"Any intelligent fool can make things bigger and more complex...
It takes a touch of genius - and a lot of courage to move in the opposite
direction."
Albert Einstein
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: options WITNESS and locks
Yony Yossef wrote: Something is still unclear. All my locks are MTX_DEF type, which means sleepable, including the one specified in the crash report (MTNIC state semaphore). This crash happens when I try to call bus_resource_alloc_any for a SYS_REQ which is trying to obtain the second lock (ACPI root bus). How come my MTX_DEF lock is being treated as as non-sleepable? MTX_DEF locks *are* non-sleepable :-) Kris Good news :-) Yet the documentation is confusing me: man pages say: MTX_DEFDefault mutexes will always allow the current thread to be suspended to avoid deadlock conditions against interrupt threads. The implementation of this lock type may spin for a while before suspending the current thread. and in mutex.h: /* * Mutex types and options passed to mtx_init(). MTX_QUIET and MTX_DUPOK * can also be passed in. */ #define MTX_DEF 0x /* DEFAULT (sleep) lock */ #define MTX_SPIN 0x0001 /* Spin lock (disables interrupts) */ #define MTX_RECURSE 0x0004 /* Option: lock allowed to recurse */ #define MTX_NOWITNESS 0x0008 /* Don't do any witness checking. */ #define MTX_NOPROFILE 0x0020 /* Don't profile this lock */ What does the "DEFAULT (sleep) lock" comment near MTX_DEF means? And which ones are sleepable?.. I guess I'm missing something here. "sleep mutex" means that the mutex holder may be put to sleep by the kernel while the mutex is held by another process (if the lock holder is running then it will spin, though). It is in contrast to "spin" mutexes that always spin forever while the lock is held, even when it might be inefficient for them to do so because the lock holder is no longer running after the CPU context switched to another process before it released the lock. This describes the behaviour of the mutex while it is waiting to acquire a lock. "sleepable" vs "non-sleepable" locks means what it is legal for your code to do while holding a mutex and doesn't relate to the internal implementation of the lock. This describes what it is legal for your code to do once it has acquired the lock. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 7 , Rebooting....
I have just setup a FreeBSD server one a machine. What happens is the machine seems to suddenly reboot during compiling ports.. Did a cat of /var/log/messages Jul 15 15:34:30 LAMACS kernel: Fatal trap 12: page fault while in kernel mode Jul 15 15:34:30 LAMACS kernel: cpuid = 1; apic id = 01 Jul 15 15:34:30 LAMACS kernel: fault virtual address= 0x0 Jul 15 15:34:30 LAMACS kernel: fault code = supervisor write data, page not present Jul 15 15:34:30 LAMACS kernel: instruction pointer = 0x8:0x807242d7 Jul 15 15:34:30 LAMACS kernel: stack pointer= 0x10:0xaf6a3a00 Jul 15 15:34:30 LAMACS kernel: frame pointer= 0x10:0x0 Jul 15 15:34:30 LAMACS kernel: code segment = base 0x0, limit 0xf, type 0x1b Jul 15 15:34:30 LAMACS kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Jul 15 15:34:30 LAMACS kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jul 15 15:34:30 LAMACS kernel: current process = 50223 (sh) Jul 15 15:34:30 LAMACS kernel: trap number = 12 Jul 15 15:34:30 LAMACS kernel: panic: page fault Jul 15 15:34:30 LAMACS kernel: cpuid = 1 Jul 15 15:34:30 LAMACS kernel: Uptime: 2h19m6s Jul 15 15:34:30 LAMACS kernel: Physical memory: 2033 MB Jul 15 15:34:30 LAMACS kernel: Dumping 297 MB: 282 266 250 234 218 202 186 170 154 138 122 106 90 74 58 42 26 10 Jul 15 15:34:30 LAMACS kernel: Dump complete Jul 15 15:34:30 LAMACS kernel: Automatic reboot in 15 seconds - press a key on the console to abort Jul 15 15:34:30 LAMACS kernel: Rebooting... Jul 15 15:34:30 LAMACS kernel: cpu_reset: Stopping other CPUs That's the NB part in it.. Any input? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: options WITNESS and locks
> > > Something is still unclear. All my locks are MTX_DEF type, which means >> sleepable, including the one specified in the crash report (MTNIC state >> semaphore). >> This crash happens when I try to call bus_resource_alloc_any for a SYS_REQ >> which is trying to obtain the second lock (ACPI root bus). How come my >> MTX_DEF lock is being treated as as non-sleepable? >> > > MTX_DEF locks *are* non-sleepable :-) > > Kris > Good news :-) Yet the documentation is confusing me: man pages say: MTX_DEFDefault mutexes will always allow the current thread to be suspended to avoid deadlock conditions against interrupt threads. The implementation of this lock type may spin for a while before suspending the current thread. and in mutex.h: /* * Mutex types and options passed to mtx_init(). MTX_QUIET and MTX_DUPOK * can also be passed in. */ #define MTX_DEF 0x /* DEFAULT (sleep) lock */ #define MTX_SPIN 0x0001 /* Spin lock (disables interrupts) */ #define MTX_RECURSE 0x0004 /* Option: lock allowed to recurse */ #define MTX_NOWITNESS 0x0008 /* Don't do any witness checking. */ #define MTX_NOPROFILE 0x0020 /* Don't profile this lock */ What does the "DEFAULT (sleep) lock" comment near MTX_DEF means? And which ones are sleepable?.. I guess I'm missing something here. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic: spin lock held too long when booting
Mike Clarke wrote: I'm getting frequent panics due to spin lock held too long when booting my recently built 6.3 system with an Athlon 4850e dual core processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and nForce 430 chipsets). FreeBSD curlew.lan 6.3-STABLE FreeBSD 6.3-STABLE #2: Sat Jul 12 09:43:21 BST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CURLEW i386 I'd welcome any advice on how to understand and fix this. The panics usually happen immediately after the "Mounting local filesystem" message, but sometimes just before the end of the boot process. The system goes through the motions of producing a crash dump with a visible count down on the screen followed with... Dump complete Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset: Stopping other CPUs ... then it just hangs until I do a hard reset. The odd thing is that when I reboot there doesn't appear to be any crash dump - I see the following messages: Checking for core dump on /dev/ad4s1b... savecore: no dumps found Is the lack of a dump due to some config error of mine, or an effect of the spin lock problem? Here's the head of my kernel file ... include GENERIC nocpu I486_CPU nocpu I586_CPU ident CURLEW nooptions COMPAT_FREEBSD4 # Compatible with FreeBSD4 nooptions COMPAT_FREEBSD5 # Compatible with FreeBSD5 options DDB options KDB options KDB_UNATTENDED You should add options WITNESS also and this will probably generate additional debugging and/or a panic before the error occurs. But I'm still a bit dubious as to whether I've really managed to create a debugging kernel. I was under the impression that there should be some *.symbols files in the /boot/kernel directory but there aren't any (or is this just a rev. 7 thing?) and the kernel directory is only 24 MB. I also noticed when building the kernel there were lines like ... objcopy --strip-debug kernel.debug kernel ... though I do still have /usr/obj/usr/src/sys/CURLEW/kernel.debug. should I be doing something with this? You can just use it post-mortem with kgdb. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: options WITNESS and locks
Yony Yossef wrote: Something is still unclear. All my locks are MTX_DEF type, which means sleepable, including the one specified in the crash report (MTNIC state semaphore). This crash happens when I try to call bus_resource_alloc_any for a SYS_REQ which is trying to obtain the second lock (ACPI root bus). How come my MTX_DEF lock is being treated as as non-sleepable? MTX_DEF locks *are* non-sleepable :-) Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Panic: spin lock held too long when booting
I'm getting frequent panics due to spin lock held too long when booting my recently built 6.3 system with an Athlon 4850e dual core processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and nForce 430 chipsets). FreeBSD curlew.lan 6.3-STABLE FreeBSD 6.3-STABLE #2: Sat Jul 12 09:43:21 BST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CURLEW i386 I'd welcome any advice on how to understand and fix this. The panics usually happen immediately after the "Mounting local filesystem" message, but sometimes just before the end of the boot process. The system goes through the motions of producing a crash dump with a visible count down on the screen followed with... Dump complete Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset: Stopping other CPUs ... then it just hangs until I do a hard reset. The odd thing is that when I reboot there doesn't appear to be any crash dump - I see the following messages: Checking for core dump on /dev/ad4s1b... savecore: no dumps found Is the lack of a dump due to some config error of mine, or an effect of the spin lock problem? Here's the head of my kernel file ... include GENERIC nocpu I486_CPU nocpu I586_CPU ident CURLEW nooptions COMPAT_FREEBSD4 # Compatible with FreeBSD4 nooptions COMPAT_FREEBSD5 # Compatible with FreeBSD5 options DDB options KDB options KDB_UNATTENDED ... the rest of the file is just "nodevice" lines for various devices I don't have. And from /etc/rc.conf ... dumpdir="/usr/crash" dumpdev="/dev/ad4s1b" Messages on the console while booting imply debugging is enabled... KDB: debugger backends: ddb KDB: current backend: ddb ... kernel dumps on /dev/ad4s1b ... But I'm still a bit dubious as to whether I've really managed to create a debugging kernel. I was under the impression that there should be some *.symbols files in the /boot/kernel directory but there aren't any (or is this just a rev. 7 thing?) and the kernel directory is only 24 MB. I also noticed when building the kernel there were lines like ... objcopy --strip-debug kernel.debug kernel ... though I do still have /usr/obj/usr/src/sys/CURLEW/kernel.debug. should I be doing something with this? -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: difference between loading kernel module during boot and after boot manually?
On Mon, Jul 14, 2008 at 10:58 PM, Mel <[EMAIL PROTECTED]> wrote: > On Monday 14 July 2008 20:29:07 Vincent Barus wrote: >> On Tue, Jul 8, 2008 at 8:11 PM, Mel <[EMAIL PROTECTED]> > wrote: >> > On Tuesday 08 July 2008 16:48:26 Vincent Barus wrote: >> >> does anyone have an idea what's the difference or what _could_ be the >> >> difference on loading a kernel module during boot or manually? >> > >> > There's one major difference. File systems aren't mounted at loader >> > stage, so any reference to modules/libraries that exist on a different >> > partition, will fail. > >> Right now i have only one partition and the same problem occurs. Other >> modules e.g. for sound or the nvidia module work as a charm. >> So I think that's not the only difference. >> I can live with a module loaded at the end of the boot process/after >> login but I don't think that's the real solution. > > Hmm, I can only guess here. Is the machine booting to xorg? As in, is the > nvidia card actually initialized, not just in VGA mode? If so, does it work > when it stays in console mode and/or when nvidia.ko is removed from the > loaded modules? > > -- > Mel > > Problem with today's modular software: they start with the modules >and never get to the software part. > I start X manually after login. You want me to unload nvidia.ko while on console? I never tried it --> have to try it. The card gets initialized during boot as it should instead of the nic which causes: re0: port 0xd800-0xd8ff mem 0xfebff000-0xfebf irq 17 at device 0.0 on pci4 re0: couldn't map ports/memory device_attach: re0 attach returned 6 as described in kern/123563 How do I track down mapping problems on boot time? Regards, Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: options WITNESS and locks
Hi Kris, Please see below > Hi all. >> >> I'm trying to debug a "spinlock held too long" error. >> Therefore I thought compiling my kernel with "options WITNESS" would be a >> good idea. >> >> Using the WITNESS kernel I cannot load my driver with any MTX_SPIN mutex. >> I had to change it all to MTX_DEF since every MTX_SPIN got me this error: >> >> panic: lock (network driver) spin mutex does not match earlier (sleep >> mutex) >> lock >> > > It means that somewhere you are treating a mutex with that name as a sleep > mutex and in other places as a spin mutex. WITNESS works on the lock name > so this may or may not be a bug. > > However, default mutexes should be used in most cases anyway (bear in mind > that default mutexes will also spin when it makes sense for them to do so). > > So I changed it all to MTX_DEF, just to see if things will work. >> Now I can load my driver, but calling ifconfig shows a new crash: >> >> mtnic0: Activating port:1 >> mtnic0: Ethernet address: 00:00:00:00:08:88 >> mtnic0: Activating port:2 >> mtnic1: Ethernet address: 00:00:00:00:08:89 >> lock order reversal: (sleepable after non-sleepable) >> 1st 0x81379010 MTNIC state semaphore (MTNIC state semaphore) @ >> mtnic_netdev.c:1855 >> 2nd 0x809eee00 ACPI root bus (ACPI root bus) @ >> /usr/src/sys/dev/acpica/acpi.c:1022 >> > > You are acquiring a lock that is "sleepable" (i.e. legal for consumers to > sleep while holding it), after first acquiring another lock that is not > sleepable. The danger is that if some code sleeps while holding both the > first and second lock, then other code that tries to acquire the first lock > will deadlock indefinitely. > > This is often due to a programming or design error. > > Kris Something is still unclear. All my locks are MTX_DEF type, which means sleepable, including the one specified in the crash report (MTNIC state semaphore). This crash happens when I try to call bus_resource_alloc_any for a SYS_REQ which is trying to obtain the second lock (ACPI root bus). How come my MTX_DEF lock is being treated as as non-sleepable? > > > KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a >> witness_checkorder() at witness_checkorder+0x559 >> _sx_xlock() at _sx_xlock+0x32 >> acpi_alloc_resource() at acpi_alloc_resource+0x9a >> pci_alloc_resource() at pci_alloc_resource+0x81 >> resource_list_alloc() at resource_list_alloc+0x17a >> pci_alloc_resource() at pci_alloc_resource+0x81 >> bus_alloc_resource() at bus_alloc_resource+0x89 >> mtnic_start_port() at mtnic_start_port+0x4f1 >> mtnic_open() at mtnic_open+0xb2 >> ether_ioctl() at ether_ioctl+0xb5 >> mtnic_ioctl() at mtnic_ioctl+0x3e >> in_ifinit() at in_ifinit+0x8d >> in_control() at in_control+0xc66 >> ifioctl() at ifioctl+0xea >> kern_ioctl() at kern_ioctl+0xa3 >> ioctl() at ioctl+0xf9 >> syscall() at syscall+0x1b5 >> Xfast_syscall() at Xfast_syscall+0xab >> --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800824cfc, rsp = >> 0x7fffe3b8, rbp = 0x7fffee10 --- >> KDB: enter: witness_checkorder >> [thread pid 1051 tid 100069 ] >> Stopped at kdb_enter+0x31: leave >> db> >> >> >> Can anybody please tell me what is going on here? >> >> -Yony >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to " >> [EMAIL PROTECTED]" >> >> >> > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named and its hourly reports
On Tue, 15 Jul 2008, jonathan michaels wrote:
> On Tue, Jul 15, 2008 at 08:27:33PM +1000, Ian Smith wrote:
> > On Tue, 15 Jul 2008 12:22:06 +1000 jonathan michaels <[EMAIL PROTECTED]>
> > wrote:
> >
> > > named now reports hourly
> > >
> > > Jul 15 06:55:10 hid named[617]: could not listen on UDP socket:
> > permission denied
> > > Jul 15 06:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> > interface ignored
> > > Jul 15 07:55:10 hid named[617]: could not listen on UDP socket:
> > permission denied
> > > Jul 15 07:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> > interface ignored
> > > Jul 15 08:55:10 hid named[617]: could not listen on UDP socket:
> > permission denied
> > > Jul 15 08:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> > interface ignored
> > > Jul 15 09:55:10 hid named[617]: could not listen on UDP socket:
> > permission denied
> > > Jul 15 09:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> > interface ignored
> > >
> > > i've tried teh hand book, even muddled my way through google, teh only
> > > reference that has surfaced is a pointer to the fact the this error
> > > message is because named is running in a sandbox ??? d'ont know when
> > > that happened but freebsd now runs named from a sandbox ..
> >
> > By default .. you don't have to, but it's a very good idea these days.
> >
> > > this machine is a router/gateway and old 486 with a small scsi hdd that
> > > is rapidly filling up from this and others, to my mind silly error
> > > messages.
> > >
> > > is there some way to fix thins, is it a hard error, can i run named not
> > > in a sandbox, i'm also seeing other errors that seem (to my mind) to be
> > > related to this, but i am not sure so i'm keeping my mouth shut untill
> > > i can work it out and find teh real culprit ..
> >
> > Jonathan, I don't think not running named in a sandbox would help here.
>
> after i got yuri post earlier i started to do some reading and
> it all making sence now and so does the sandbox stuff .. si it
> is staying.
Good.
> > As Yuri pointed out, named is scanning all interfaces, default hourly.
>
> this is teh thing i'm having trouble with, why is named scaning
> anything ??
By default it listens on all interfaces on the box, so it tries to
discover new ones, stop listening on any that have disappeared etc.
> i've got two secondaries (my isp and a friend) for
> caamora.com.au, it was easy in bind v4, but not so with the new
> v8/9 config .. everything and teh kitchen sink gets defined. i
> am working my way through it, its a bit of hard going for me.
Yes there are a zillion options, but you can just allow defaults for
most. The installed named.conf, plus your zone/s, does for many people,
but interfaces that can come and go, like tuns, need special attention.
In this case, you will want to override the default listen-on { * }; To
quote from my ever-handy http://localhost/bind9ref/Bv9ARM.ch06.html ..
"the listen-on option will cause the server to not accept queries on any
of the machine's addresses which do not match the list." and "If no
listen-on is specified, the server will listen on port 53 on all
interfaces."
> > I had a related problem on this laptop, with the same error messages -
> > after a suspend/resume the (pccard) interface wasn't coming up quickly
> > enough to beat named's (then overdue) interface scan, so named wouldn't
> > bind to that interface. I fixed that by running the following script
[..]
> thanks, but i don't think this will help here, the machine is a
> permanently connected dialup ppp (now userland ppp, formerly
> kernel pppd). so it just sits there doing its thing untill teh
> ocasion thunderstorm or freebsd fallover, stuff happens.
Even with a static IP address, tun0 may not be UP when 'stuff happens'.
Anyway, you probably don't want to answer queries directed to your ppp
interface address .. 139.130.something I expect .. but only to your
listed nameserver address on this box, gw.caamora.com.au I guess?
> > However there are perhaps better ways to tackle this, depending on which
> > interface/s you *need* to have named listening on. If you need named to
> > listen on the adddress of tun0 (pppoe, I suppose?) then you may need to
>
> this is teh bit i am failing to understand, why is named
> scaning tun0, what is it looking for .. it should be obvious,
> but sorry i am not making sence of this.
It's just looking for existence, likely UP-ness, so it can be 'helpful'
by answering DNS queries coming in on any connected interface. In this
case, you probably want it to listen on the listed IP address of your
nameserver, on localhost, and perhaps to any internal network address to
boxes you're routing for, with or without NAT ..
> i read teh 'listen-on' bit in dns&bind ed5 (after yuri tip off)
> and trying to workout if bind is using this 'liste
Re: named and its hourly reports
ian,
long time no scribble .. thanks much appreciated
On Tue, Jul 15, 2008 at 08:27:33PM +1000, Ian Smith wrote:
> On Tue, 15 Jul 2008 12:22:06 +1000 jonathan michaels <[EMAIL PROTECTED]>
> wrote:
>
> > named now reports hourly
> >
> > Jul 15 06:55:10 hid named[617]: could not listen on UDP socket: permission
> denied
> > Jul 15 06:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> interface ignored
> > Jul 15 07:55:10 hid named[617]: could not listen on UDP socket: permission
> denied
> > Jul 15 07:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> interface ignored
> > Jul 15 08:55:10 hid named[617]: could not listen on UDP socket: permission
> denied
> > Jul 15 08:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> interface ignored
> > Jul 15 09:55:10 hid named[617]: could not listen on UDP socket: permission
> denied
> > Jul 15 09:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> interface ignored
> >
> > i've tried teh hand book, even muddled my way through google, teh only
> > reference that has surfaced is a pointer to the fact the this error
> > message is because named is running in a sandbox ??? d'ont know when
> > that happened but freebsd now runs named from a sandbox ..
>
> By default .. you don't have to, but it's a very good idea these days.
>
> > this machine is a router/gateway and old 486 with a small scsi hdd that
> > is rapidly filling up from this and others, to my mind silly error
> > messages.
> >
> > is there some way to fix thins, is it a hard error, can i run named not
> > in a sandbox, i'm also seeing other errors that seem (to my mind) to be
> > related to this, but i am not sure so i'm keeping my mouth shut untill
> > i can work it out and find teh real culprit ..
>
> Jonathan, I don't think not running named in a sandbox would help here.
after i got yuri post earlier i started to do some reading and
it all making sence now and so does the sandbox stuff .. si it
is staying.
> As Yuri pointed out, named is scanning all interfaces, default hourly.
this is teh thing i'm having trouble with, why is named scaning
anything ??
i've got two secondaries (my isp and a friend) for
caamora.com.au, it was easy in bind v4, but not so with the new
v8/9 config .. everything and teh kitchen sink gets defined. i
am working my way through it, its a bit of hard going for me.
> I had a related problem on this laptop, with the same error messages -
> after a suspend/resume the (pccard) interface wasn't coming up quickly
> enough to beat named's (then overdue) interface scan, so named wouldn't
> bind to that interface. I fixed that by running the following script
> from /etc/rc.resume:
>
> #!/bin/sh
> # 28/12/6 called by rc.resume; wait for pccard resume to reattach xe0 ..
> doit() {
> sleep $1
> # logger -p user.notice stopping named
> /etc/rc.d/named stop
> # + 31/12/6 missed restart once .. try:
> sleep 1
> # logger -p user.notice restarting named
> /etc/rc.d/named start
> }
> delay=5; [ "$1" ] && delay=$1
> doit $delay &
> exit 0 # finish rc.resume so pccard resume can get on with it ..
>
> Note that /etc/rc.d/named restart didn't work for me, nor rndc restart.
thanks, but i don't think this will help here, the machine is a
permanently connected dialup ppp (now userland ppp, formerly
kernel pppd). so it just sits there doing its thing untill teh
ocasion thunderstorm or freebsd fallover, stuff happens.
> However there are perhaps better ways to tackle this, depending on which
> interface/s you *need* to have named listening on. If you need named to
> listen on the adddress of tun0 (pppoe, I suppose?) then you may need to
this is teh bit i am failing to understand, why is named
scaning tun0, what is it looking for .. it should be obvious,
but sorry i am not making sence of this.
i read teh 'listen-on' bit in dns&bind ed5 (after yuri tip off)
and trying to workout if bind is using this 'listen-on' is it
looking for internal dns queries or looking for stuff coming in
from teh outside for the getting of domain transfer infromation
for teh secondaries, umm slave servers out there, as mentioned
earlier teh isp dns server and teh 'friend dns server' i am not
quite clear on where that information goes in teh new scheme of
things ??
> do something like the above whenever ppp connects, or reconnects, from a
> suitable up-script for ppp. The disadvantage is clearing named's cache.
> If on the other hand you only need named listening on other interface/s
> than tun0, use the 'listen on { $address; };' option/s to specify the
> address/es to listen on. The default is '*', the addresses associated
> with each interface, as 'sockstat -4 | grep named' will show. Don't
> forget to include a 'listen on { 127.0.0.1; }' if you want localhost.
>
> > some pointers would be most appreciated .. i've been struggling with
> > this for aover a year now and do not know where else
Re: Continuing problems with Xorg 7.3
On Tuesday 15 July 2008 05:32:28 Arthur Barlow wrote: > The only error I notice in Xorg.0.log is the following: > > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is -1, (No such file or directory) > drmOpenDevice: open result is -1, (No such file or directory) > drmOpenDevice: Open failed > [drm] failed to load kernel module "1810" > (EE) [drm] drmOpen failed. > > There is no "dri" device in my /dev directory, but I don't know if > that matters. I've tried to comment out the "load dri" option, but > no luck, it tries to load it anyway. DRI is loaded by default now, so you need to explicitly disable it. Replace 'Load "dri"' with 'Disable "dri"' in the Module section. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named and its hourly reports
On Tue, 15 Jul 2008 12:22:06 +1000 jonathan michaels <[EMAIL PROTECTED]> wrote:
> named now reports hourly
>
> Jul 15 06:55:10 hid named[617]: could not listen on UDP socket: permission
> denied
> Jul 15 06:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> interface ignored
> Jul 15 07:55:10 hid named[617]: could not listen on UDP socket: permission
> denied
> Jul 15 07:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> interface ignored
> Jul 15 08:55:10 hid named[617]: could not listen on UDP socket: permission
> denied
> Jul 15 08:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> interface ignored
> Jul 15 09:55:10 hid named[617]: could not listen on UDP socket: permission
> denied
> Jul 15 09:55:10 hid named[617]: creating IPv4 interface tun0 failed;
> interface ignored
>
> i've tried teh hand book, even muddled my way through google, teh only
> reference that has surfaced is a pointer to the fact the this error
> message is because named is running in a sandbox ??? d'ont know when
> that happened but freebsd now runs named from a sandbox ..
By default .. you don't have to, but it's a very good idea these days.
> this machine is a router/gateway and old 486 with a small scsi hdd that
> is rapidly filling up from this and others, to my mind silly error
> messages.
>
> is there some way to fix thins, is it a hard error, can i run named not
> in a sandbox, i'm also seeing other errors that seem (to my mind) to be
> related to this, but i am not sure so i'm keeping my mouth shut untill
> i can work it out and find teh real culprit ..
Jonathan, I don't think not running named in a sandbox would help here.
As Yuri pointed out, named is scanning all interfaces, default hourly.
I had a related problem on this laptop, with the same error messages -
after a suspend/resume the (pccard) interface wasn't coming up quickly
enough to beat named's (then overdue) interface scan, so named wouldn't
bind to that interface. I fixed that by running the following script
from /etc/rc.resume:
#!/bin/sh
# 28/12/6 called by rc.resume; wait for pccard resume to reattach xe0 ..
doit() {
sleep $1
# logger -p user.notice stopping named
/etc/rc.d/named stop
# + 31/12/6 missed restart once .. try:
sleep 1
# logger -p user.notice restarting named
/etc/rc.d/named start
}
delay=5; [ "$1" ] && delay=$1
doit $delay &
exit 0 # finish rc.resume so pccard resume can get on with it ..
Note that /etc/rc.d/named restart didn't work for me, nor rndc restart.
However there are perhaps better ways to tackle this, depending on which
interface/s you *need* to have named listening on. If you need named to
listen on the adddress of tun0 (pppoe, I suppose?) then you may need to
do something like the above whenever ppp connects, or reconnects, from a
suitable up-script for ppp. The disadvantage is clearing named's cache.
If on the other hand you only need named listening on other interface/s
than tun0, use the 'listen on { $address; };' option/s to specify the
address/es to listen on. The default is '*', the addresses associated
with each interface, as 'sockstat -4 | grep named' will show. Don't
forget to include a 'listen on { 127.0.0.1; }' if you want localhost.
> some pointers would be most appreciated .. i've been struggling with
> this for aover a year now and do not know where else to go ??
You could have come here a year ago :)
cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Change email header .....
2008/7/14 Bill Campbell <[EMAIL PROTECTED]>: > On Mon, Jul 14, 2008, Agus wrote: > >Hi guys, > > > >All i wanna do this time is change the mail from: header to another > >address...As my system is named after an internal network name and doesnt > >resolv from outside my LAN..when i send an email, for instance when a user > >registers, they received it with the systems internal address and they > cant > >reply it cause of course it will get bouncedSo i wanna change the from > >header to an address where i have a mail redirection accountI know how > >to do it from telnet for instance..its simple..but as i send emails from a > >script using the mail program.. > > > >I basically do cat welcome_msg|mail -s "Welcome..." [EMAIL PROTECTED] > > > >So i was wondering if there is a way to send this automated emails > changing > >the header from: > >Perhaps theres another program or way...Im open to suggestions... > > Mutt allows one to specify any headers you like, even being able > to tailor them to the recipient. > > One could also contruct your own headers, and feed it through > sendmail: > > cat << DONE > From: [EMAIL PROTECTED] > Subject: anything you like > Reply-To: [EMAIL PROTECTED] > > There is a blank line separating this message body from the > headers above. > > Bill > DONE || /usr/lib/sendmail [EMAIL PROTECTED] > > Substitute the appropriate path for sendmail if necessary. > > Bill > -- > INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC > URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way > Voice: (206) 236-1676 Mercer Island, WA 98040-0820 > Fax:(206) 232-9186 > > Government spending? I don't know what it's all about. I don't know > any more about this thing than an economist does, and, God knows, he > doesn't know much. -- Will Rogers > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > [EMAIL PROTECTED]" > Hi guys...thankss...it seems thats exactly what i need...i ll try it now... Yes..sorry..i am using Sendmailforgot that.. Thank u very much guys C ya... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: httpd could not be started
At 2008-07-15T11:01:40+03:00, Тарас wrote:
> /usr/local/sbin/apachectl start: httpd could not be started
>
> httpd-error.log
> [Tue Jul 15 10:35:46 2008] [alert] mod_unique_id: unable to gethostbyname("")
If there's no entry for your hostname in `/etc/hosts', adding one may
help:
127.0.0.1 localhost localhost.example.net
192.168.8.10foo.example.net foo
Raghavendra.
--
N. Raghavendra <[EMAIL PROTECTED]> | http://www.retrotexts.net/
Harish-Chandra Research Institute | http://www.mri.ernet.in/
See message headers for contact and OpenPGP information.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Core(TM)2 Quad and TOP output
Jos Chrispijn пишет:
Scott Bennett wrote:
That is not necessary either. Take a look in /sys/i386/conf or
/sys/amd64/conf, depending upon which you are using. Then do:
# config SMP
# cd ../compile/SMP
# make cleandepend && make depend && make && make install
# shutdown -r now
That should take care of it for you. /sys/{i386,amd64}/conf/SMP adds
"options SMP" and then includes GENERIC.
Thanks for sharing; will put this in my FreeBSD user bible!
Not for too long, GENERIC in 7.0-RELEASE includes SMP
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Core(TM)2 Quad and TOP output
Scott Bennett wrote:
That is not necessary either. Take a look in /sys/i386/conf or
/sys/amd64/conf, depending upon which you are using. Then do:
# config SMP
# cd ../compile/SMP
# make cleandepend && make depend && make && make install
# shutdown -r now
That should take care of it for you. /sys/{i386,amd64}/conf/SMP adds
"options SMP" and then includes GENERIC.
Thanks for sharing; will put this in my FreeBSD user bible!
-- Jos
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: httpd could not be started
Тарас wrote:
Hi!
When I run Apache:
/usr/local/sbin/apachectl start: httpd could not be started
httpd-error.log
[Tue Jul 15 10:35:46 2008] [alert] mod_unique_id: unable to gethostbyname("")
httpd.pid don't exist.
What is your question again?
-- Jos
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
httpd could not be started
Hi!
When I run Apache:
/usr/local/sbin/apachectl start: httpd could not be started
httpd-error.log
[Tue Jul 15 10:35:46 2008] [alert] mod_unique_id: unable to gethostbyname("")
httpd.pid don't exist.
С уважением. Тарас Голуб
-- реклама ---
Домен БЕСПЛАТНО!
С хостинг-планом на http://www.hostpro.ua
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OT-ish: fedora->crash->single user fsck; FreeBSD->crash->smooth recovery
On Tue, 15 Jul 2008 07:36:17 +0200 (CEST)
Wojciech Puchar <[EMAIL PROTECTED]> wrote:
> > Is ext2/3 really that bad?
> >
> i don't know ext3, it in theory does journalling, are you using ext3 or
> ext2?
>
> hint: ext3 is actually ext2 with extra file created, there is no need to
> convert, just run fsck_ext3 to convert to ext3, and delete that file to
> convert to ext2.
( my apologies for pursuing the OT)
I can't speak for Fedora, i haven't bothered using it. I can tell you , though,
that ext3's journal is prey to memory hungry processes (like VMWare server) -
user level app uses lots of memory, the fs doesn't have enough to cache/journal
and you hit the ground very fast and very hard. There are some sysctl you can
use to postpone this (at the expense of usable memory).
Other than that, i can't say ext3 is that bad.
But yeah, I still haven't found enough reasons to move back to Linux from FBSD.
B
_
{Beto|Norberto|Numard} Meijome
If you were supposed to understand it, we wouldn't call it 'code'.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Core(TM)2 Quad and TOP output
On Mon, 14 Jul 2008 19:25:26 +0300 "tethys ocean" <[EMAIL PROTECTED]>
top-posted:
>Pufz I ve check all my server and I ve realize all my server is running
>only one CPU :( all is 6.3 stable
>
>How must I add another CPU on running server.
>
See further below.
>
>and 7.0 will have to be stable heyoo :D
>
>* 7.0-STABLE FreeBSD 7.0-STABLE #0: Mon Jul 14 21:59:07 EEST 2008*
>
>
>On Mon, Jul 14, 2008 at 6:38 PM, Jos Chrispijn <[EMAIL PROTECTED]> wrote:
>
>> Josh Carroll wrote:
>>
>>> Is SMP in GENERIC now in 6.3-STABLE then?
>>>
>>>
>> Nope, you have to add that line to it b4 you compile your Kernel again...
>>
That is not necessary either. Take a look in /sys/i386/conf or
/sys/amd64/conf, depending upon which you are using. Then do:
# config SMP
# cd ../compile/SMP
# make cleandepend && make depend && make && make install
# shutdown -r now
That should take care of it for you. /sys/{i386,amd64}/conf/SMP adds
"options SMP" and then includes GENERIC.
Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet: bennett at cs.niu.edu *
**
* "A well regulated and disciplined militia, is at all times a good *
* objection to the introduction of that bane of all free governments *
* -- a standing army." *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
