Re: Every 12-hrs -- ad0: TIMEOUT - WRITE DMA
[...] First of all: The disk is *not* dying. SMART won't reveal anything. The behaviour is perfectly normal for IBM-DJNA-3* type disks. When those disks are used in continuous operation (24/7), they will go into automatic maintenance mode after 6 days. This is kind of a short self-test and recalibration to ensure reliable continous operation. It will be repeated after another 6 days ad infinitum. It's been over 3.5 years since my original post -- imagine my surprise! The drive's still running (24/7) and still reporting the same retries. Because of the pattern of the retries, I never really thought that the drive was bad. But, until now, I never knew why it was happening. Thanks *very* much for the info! ___ 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: Changing /var/mail to a symlink
-Original Message- From: Tino Engel [mailto:[EMAIL PROTECTED] Sent: Saturday, December 15, 2007 12:58 PM To: 'V.I.Victor' Cc: freebsd-questions@freebsd.org Subject: Re: Changing /var/mail to a symlink V.I.Victor schrieb: Because of /var size considerations, I'd like to use a symlinked /usr directory for email instead of /var/mail. Based on today's research, I think the following will work. With mail delivery off, I 'su' and: mkdir /usr/var.mail cd /var cp -p mail/* /usr/var.mail/ mv mail mail.bak ln -s /usr/var.mail mail Since 'ls -l /var' shows: drwxrwxrwt 2 root mail 512 Dec 14 14:24 mail I should then: cd /usr chmod 1777 var.mail chown root:mail var.mail No changes are made to the /var/mail symlink. Then, if everything works, I just delete /usr/mail.bak. Does this seem OK? Sorry to bother everyone with what's probably a trivial question, but I *really* want to avoid screwing-up. The machine is remote; accessed via ssh. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Sounds reasonable to me. I'd just check afterwards if the permissions are like you want them to be, i.e. as they have been before... And you might send one or another testmail to the an account on the system to see if everything works as before, before you delete the mail.mak directory... Rg, Tino Thanks for the reply! I was pretty sure that the symlinking was right, but was not sure how the permissions carried thru -- as you also mentioned. I probably should have asked differently... Also, a suggestion was made off-list that moving /var/mail was better-done via mounting a nullfs. I'm reading up on that now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Changing /var/mail to a symlink
Because of /var size considerations, I'd like to use a symlinked /usr directory for email instead of /var/mail. Based on today's research, I think the following will work. With mail delivery off, I 'su' and: mkdir /usr/var.mail cd /var cp -p mail/* /usr/var.mail/ mv mail mail.bak ln -s /usr/var.mail mail Since 'ls -l /var' shows: drwxrwxrwt 2 root mail 512 Dec 14 14:24 mail I should then: cd /usr chmod 1777 var.mail chown root:mail var.mail No changes are made to the /var/mail symlink. Then, if everything works, I just delete /usr/mail.bak. Does this seem OK? Sorry to bother everyone with what's probably a trivial question, but I *really* want to avoid screwing-up. The machine is remote; accessed via ssh. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Utility to change a byte in a binary file?
It sure seems that this should be simple, but my searches have only turned up inter-active hex/disk editors. I'm probably asking wrong. I have a large binary file (700 meg) and I know that there is a single wrong byte. I also know it's exact location in the file. Is there a command-line utility to write a byte at a specified offset into a file? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI slowing CPU... or something else
On Wed, 25 Jul 2007 [EMAIL PROTECTED] wrote:
On Wed, 25 Jul 2007, V.I.Victor wrote:
On Wed, 25 Jul 2007 [EMAIL PROTECTED] wrote:
On Wed, 25 Jul 2007, V.I.Victor wrote:
On Wed, 25 Jul 2007, Garrett Cooper wrote:
V.I.Victor wrote:
I've two 5.4 desktop boxes. Pretty much the same installation; both
from the same CD, same apps, no monitor/keyboard, 1-user logged-on via
ssh (command-line only w/no gui) and otherwise lightly loaded.
Box_A: CPU: AMD-K7(tm) Processor (598.84-MHz 686-class CPU)
avail memory = 121630720 (115 MB)
ACPI disabled by blacklist.
Box_B: CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1794.19-MHz 686-class
CPU)
avail memory = 252186624 (240 MB)
cpu0: ACPI CPU on acpi0
acpi_throttle0: ACPI CPU Throttling on cpu0
...
Yes. On my virtual machine with ACPI:
dev.cpu.0.freq: 2653
dev.cpu.0.freq_levels: 2653/-1 2321/-1 1989/-1 1658/-1 1326/-1 994/-1
663/-1
331/-1
[EMAIL PROTECTED] ~]# dmesg | grep 26
FreeBSD 7.0-CURRENT #5: Tue Jul 17 08:22:26 UTC 2007
CPU: Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz (2666.79-MHz K8-class
CPU)
Timecounter TSC frequency 2666794890 Hz quality 800
What are the following sysctls set to?
kern.clockrate
hw.acpi.cpu.cx_lowest
dev.cpu.0.cx_lowest
dev.cpu.0.cx_usage
Thanks for the reply! I don't seem to have the last 2 you've asked about.
'sysctl -a | egrep clockrate|cpu' reported the following:
kern.clockrate: { hz = 100, tick = 1, profhz = 1024, stathz = 128 }
kern.threads.virtual_cpu: 1
kern.ccpu: 1948
kern.smp.maxcpus: 1
kern.smp.cpus: 1
hw.ncpu: 1
hw.clockrate: 1794
hw.acpi.cpu.cx_supported: C1/0
hw.acpi.cpu.cx_lowest: C1
hw.acpi.cpu.cx_usage: 100.00%
machdep.cpu_idle_hlt: 1
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1796
dev.cpu.0.freq_levels: 1796/-1 1571/-1 1347/-1 1122/-1 898/-1 673/-1
449/-1 224/-1
dev.acpi_throttle.0.%parent: cpu0
dev.cpufreq.0.%driver: cpufreq
dev.cpufreq.0.%parent: cpu0
Do you have SMP enabled?
No. Both boxes have pretty minimal, basic installations.
You also might be able to tune the kernel clock rate to obtain better
performance; I forget what the values were for sysctl, but if you search
around the current@ archives a bit, there was a discussion involving VMware
and clock tuning approximately 2-3 months ago which details this issue, and
possible solutions.
Perhaps tuning could help. I'll check the archives.
However, it just seems to me that the 1.8 GHz box ought to perform the
simple prog (orig post) at least as fast as the 6 MHz box.
Depends on:
1. What you're trying to do.
2. What your programs are optimized for.
3. Additional factors (I/O, load, etc).
4. Hardware attached to each machine. Some examples...
a. Comparing a SCSI disk vs a PATA disk.
b. Clockspeed applied to the RAM on one machine isn't equal to the other.
c. Motherboard manufacturers -- some manufacturers have done a shoddy job
with memory handling, BIOS manufacturing, and other critical stats in the
past.
Try disabling ACPI on the P4 though and see what happens. I will say though,
the Willamette (1st gen P4) chips weren't Intel's finest desktop chip; some
people went far enough to complain that the Willamette series was nothing
more than overclocked Coppermines, i.e. P3's. I haven't taken a look at the
architectures and compared them, so those may be empty claims.
I was wondering about the truth-of-clockspeed. Perhaps the 1800-MHz only
applies to CPU internal cache, etc. while the external bus-clocking is down at
500-MHz or so. Sounds like a typical marketing ploy!
About disabling the ACPI... Can I do it *safely* via the remote-ssh
connection? Or do I need to be at the box w/ keyboard and monitor? What I've
read makes it seem that the ACPI is set at boot-time.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI slowing CPU... or something else
On Thu, 26 Jul 2007, Manolis Kiagias wrote: V.I.Victor wrote: I was wondering about the truth-of-clockspeed. Perhaps the 1800-MHz only applies to CPU internal cache, etc. while the external bus-clocking is down at 500-MHz or so. Sounds like a typical marketing ploy! About disabling the ACPI... Can I do it *safely* via the remote-ssh connection? Or do I need to be at the box w/ keyboard and monitor? What I've read makes it seem that the ACPI is set at boot-time. If you don't mind rebooting the remote machine, add: hint.acpi.0.disabled=1 to /boot/device.hints and reboot Although I've re-booted remotely, I've never done it after a boot modification. It's probably prudent to wait 'til the weekend to try this -- mistakes are easier to deal with! Thanks for the info. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI slowing CPU... or something else
On Wed, 25 Jul 2007, Garrett Cooper wrote:
V.I.Victor wrote:
I've two 5.4 desktop boxes. Pretty much the same installation; both
from the same CD, same apps, no monitor/keyboard, 1-user logged-on via
ssh (command-line only w/no gui) and otherwise lightly loaded.
Box_A: CPU: AMD-K7(tm) Processor (598.84-MHz 686-class CPU)
avail memory = 121630720 (115 MB)
ACPI disabled by blacklist.
Box_B: CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1794.19-MHz 686-class CPU)
avail memory = 252186624 (240 MB)
cpu0: ACPI CPU on acpi0
acpi_throttle0: ACPI CPU Throttling on cpu0
...
Yes. On my virtual machine with ACPI:
dev.cpu.0.freq: 2653
dev.cpu.0.freq_levels: 2653/-1 2321/-1 1989/-1 1658/-1 1326/-1 994/-1 663/-1
331/-1
[EMAIL PROTECTED] ~]# dmesg | grep 26
FreeBSD 7.0-CURRENT #5: Tue Jul 17 08:22:26 UTC 2007
CPU: Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz (2666.79-MHz K8-class
CPU)
Timecounter TSC frequency 2666794890 Hz quality 800
What are the following sysctls set to?
kern.clockrate
hw.acpi.cpu.cx_lowest
dev.cpu.0.cx_lowest
dev.cpu.0.cx_usage
Thanks for the reply! I don't seem to have the last 2 you've asked about.
'sysctl -a | egrep clockrate|cpu' reported the following:
kern.clockrate: { hz = 100, tick = 1, profhz = 1024, stathz = 128 }
kern.threads.virtual_cpu: 1
kern.ccpu: 1948
kern.smp.maxcpus: 1
kern.smp.cpus: 1
hw.ncpu: 1
hw.clockrate: 1794
hw.acpi.cpu.cx_supported: C1/0
hw.acpi.cpu.cx_lowest: C1
hw.acpi.cpu.cx_usage: 100.00%
machdep.cpu_idle_hlt: 1
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1796
dev.cpu.0.freq_levels: 1796/-1 1571/-1 1347/-1 1122/-1 898/-1 673/-1 449/-1
224/-1
dev.acpi_throttle.0.%parent: cpu0
dev.cpufreq.0.%driver: cpufreq
dev.cpufreq.0.%parent: cpu0
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI slowing CPU... or something else
On Wed, 25 Jul 2007 [EMAIL PROTECTED] wrote:
On Wed, 25 Jul 2007, V.I.Victor wrote:
On Wed, 25 Jul 2007, Garrett Cooper wrote:
V.I.Victor wrote:
I've two 5.4 desktop boxes. Pretty much the same installation; both
from the same CD, same apps, no monitor/keyboard, 1-user logged-on via
ssh (command-line only w/no gui) and otherwise lightly loaded.
Box_A: CPU: AMD-K7(tm) Processor (598.84-MHz 686-class CPU)
avail memory = 121630720 (115 MB)
ACPI disabled by blacklist.
Box_B: CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1794.19-MHz 686-class CPU)
avail memory = 252186624 (240 MB)
cpu0: ACPI CPU on acpi0
acpi_throttle0: ACPI CPU Throttling on cpu0
...
Yes. On my virtual machine with ACPI:
dev.cpu.0.freq: 2653
dev.cpu.0.freq_levels: 2653/-1 2321/-1 1989/-1 1658/-1 1326/-1 994/-1 663/-1
331/-1
[EMAIL PROTECTED] ~]# dmesg | grep 26
FreeBSD 7.0-CURRENT #5: Tue Jul 17 08:22:26 UTC 2007
CPU: Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz (2666.79-MHz K8-class
CPU)
Timecounter TSC frequency 2666794890 Hz quality 800
What are the following sysctls set to?
kern.clockrate
hw.acpi.cpu.cx_lowest
dev.cpu.0.cx_lowest
dev.cpu.0.cx_usage
Thanks for the reply! I don't seem to have the last 2 you've asked about.
'sysctl -a | egrep clockrate|cpu' reported the following:
kern.clockrate: { hz = 100, tick = 1, profhz = 1024, stathz = 128 }
kern.threads.virtual_cpu: 1
kern.ccpu: 1948
kern.smp.maxcpus: 1
kern.smp.cpus: 1
hw.ncpu: 1
hw.clockrate: 1794
hw.acpi.cpu.cx_supported: C1/0
hw.acpi.cpu.cx_lowest: C1
hw.acpi.cpu.cx_usage: 100.00%
machdep.cpu_idle_hlt: 1
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1796
dev.cpu.0.freq_levels: 1796/-1 1571/-1 1347/-1 1122/-1 898/-1 673/-1 449/-1
224/-1
dev.acpi_throttle.0.%parent: cpu0
dev.cpufreq.0.%driver: cpufreq
dev.cpufreq.0.%parent: cpu0
Do you have SMP enabled?
No. Both boxes have pretty minimal, basic installations.
You also might be able to tune the kernel clock rate to obtain better
performance; I forget what the values were for sysctl, but if you search
around the current@ archives a bit, there was a discussion involving VMware
and clock tuning approximately 2-3 months ago which details this issue, and
possible solutions.
Perhaps tuning could help. I'll check the archives.
However, it just seems to me that the 1.8 GHz box ought to perform the simple
prog (orig post) at least as fast as the 6 MHz box.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI slowing CPU... or something else
I've two 5.4 desktop boxes. Pretty much the same installation; both from the same CD, same apps, no monitor/keyboard, 1-user logged-on via ssh (command-line only w/no gui) and otherwise lightly loaded. Box_A: CPU: AMD-K7(tm) Processor (598.84-MHz 686-class CPU) avail memory = 121630720 (115 MB) ACPI disabled by blacklist. Box_B: CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1794.19-MHz 686-class CPU) avail memory = 252186624 (240 MB) cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 When running the following segment of a small gawk program: cnt=0; s=systime(); while(s==systime()) ; # next second s=systime(); while(s==systime()) cnt++; # count for 1-sec Box_A(600M) always reports 'cnt' between 31 to 32. Box_B(1800M) has been as low as 167000 and never higher than 254000. So -- Box_B is 3-times faster than Box_A but runs the segment (at best) about 20% more slowly! Yesterday was when I saw the Box_B(1800M) 167000-ish numbers. Today after seeing an increase to the 25-ish numbers, I started to read-up on ACPI. sysctl -a | grep cpu.*freq reports: dev.cpu.0.freq: 1796 dev.cpu.0.freq_levels: 1796/-1 1571/-1 1347/-1 1122/-1 898/-1 \ 673/-1 449/-1 224/-1 dev.cpufreq.0.%driver: cpufreq dev.cpufreq.0.%parent: cpu0 If I understand the 'sysctl' output, Box_B is running (now) at 1796-MHz. And for Box_B cnt==252433; for Box_A cnt==318942. Any opinions on what's going on and/or what I'm not understanding? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Help! Mail to 'localhost' not staying local
Somthing changed -- literally overnight! Or perhaps, some old problem is just showing up. All my log reports, et cetera are stuck in mqueue. Example -- for years, the following line has been in root's crontab: (sorry if folded) @reboot /bin/echo reboot |/usr/bin/mail -s start-up at `date` [EMAIL PROTECTED] It has worked without any problems delivering an email indicating start-up time. Now... Well, here's some lines from the 'mqueue' file: H??Received: from zebra.athome.net (localhost.athome.net [127.0.0.1]) by zebra.athome.net (8.13.3/8.13.3) with ESMTP id l33AFhEA000481 for [EMAIL PROTECTED]; Tue, 3 Apr 2007 06:15:44 -0400 (EDT) (envelope-from [EMAIL PROTECTED]) H??Received: (from [EMAIL PROTECTED]) by zebra.athome.net (8.13.3/8.13.3/Submit) id l33AFhqS000433 for [EMAIL PROTECTED]; Tue, 3 Apr 2007 06:15:43 -0400 (EDT) (envelope-from root) It seems that my local network name of athome.net is being evaluated. From 'whois athome.net' -- Domain Name: ATHOME.NET Registrar: NETWORK SOLUTIONS, LLC. Whois Server: whois.networksolutions.com Referral URL: http://www.networksolutions.com Name Server: NS3.LAMEDELEGATION.NET Name Server: NS4.LAMEDELEGATION.NET Status: clientTransferProhibited Updated Date: 02-apr-2007 Creation Date: 30-nov-1999 Expiration Date: 30-nov-2015 It's been around since 1999, but was updated yesterday. I'm assuming I did something wrong years back in my 'sendmail' setup. At this point, I certainly don't remember the whys hows of what I did! Could someone *please* help? Thanks! V ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help! Mail to 'localhost' not staying local
Your domain is not set correctly, or you set it to athome.net. Sendmail is just trying to deliver the email. Normally you don't need the domain to send to root. As long as you have root defined in /etc/mail/aliases you should be able to send to just root. @reboot /bin/echo reboot |/usr/bin/mail -s start-up at `date` root Thanks for the quick answer. Unfortunately, sending to just root does exactly the same as [EMAIL PROTECTED] I agree I proabably set something wrong *years* ago -- but it's only showing up today!! I'm really unsure where to change what. At 08:34 AM 4/3/2007, V.I.Victor wrote: Somthing changed -- literally overnight! Or perhaps, some old problem is just showing up. All my log reports, et cetera are stuck in mqueue. Example -- for years, the following line has been in root's crontab: (sorry if folded) @reboot /bin/echo reboot |/usr/bin/mail -s start-up at `date` [EMAIL PROTECTED] It has worked without any problems delivering an email indicating start-up time. Now... Well, here's some lines from the 'mqueue' file: H??Received: from zebra.athome.net (localhost.athome.net [127.0.0.1]) by zebra.athome.net (8.13.3/8.13.3) with ESMTP id l33AFhEA000481 for [EMAIL PROTECTED]; Tue, 3 Apr 2007 06:15:44 -0400 (EDT) (envelope-from [EMAIL PROTECTED]) H??Received: (from [EMAIL PROTECTED]) by zebra.athome.net (8.13.3/8.13.3/Submit) id l33AFhqS000433 for [EMAIL PROTECTED]; Tue, 3 Apr 2007 06:15:43 -0400 (EDT) (envelope-from root) It seems that my local network name of athome.net is being evaluated. From 'whois athome.net' -- Domain Name: ATHOME.NET Registrar: NETWORK SOLUTIONS, LLC. Whois Server: whois.networksolutions.com Referral URL: http://www.networksolutions.com Name Server: NS3.LAMEDELEGATION.NET Name Server: NS4.LAMEDELEGATION.NET Status: clientTransferProhibited Updated Date: 02-apr-2007 Creation Date: 30-nov-1999 Expiration Date: 30-nov-2015 It's been around since 1999, but was updated yesterday. I'm assuming I did something wrong years back in my 'sendmail' setup. At this point, I certainly don't remember the whys hows of what I did! Could someone *please* help? Thanks! V ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help! Mail to 'localhost' not staying local
Check that localhost is defined in /etc/hosts and your name resolution is working in /etc/nsswitch.conf Thanks for your continued input! /etc/nsswitch.conf has never been changed: group: compat group_compat: nis hosts: files dns networks: files passwd: compat passwd_compat: nis shells: files /etc/hosts is also the same as years-back: ::1 localhost.athome.net localhost 127.0.0.1 localhost.athome.net localhost 192.168.254.250 zebra.athome.net chloe 192.168.254.250 zebra.athome.net. At 09:40 AM 4/3/2007, V.I.Victor wrote: Your domain is not set correctly, or you set it to athome.net. Sendmail is just trying to deliver the email. Normally you don't need the domain to send to root. As long as you have root defined in /etc/mail/aliases you should be able to send to just root. @reboot /bin/echo reboot |/usr/bin/mail -s start-up at `date` root Thanks for the quick answer. Unfortunately, sending to just root does exactly the same as [EMAIL PROTECTED] I agree I proabably set something wrong *years* ago -- but it's only showing up today!! I'm really unsure where to change what. At 08:34 AM 4/3/2007, V.I.Victor wrote: Somthing changed -- literally overnight! Or perhaps, some old problem is just showing up. All my log reports, et cetera are stuck in mqueue. Example -- for years, the following line has been in root's crontab: (sorry if folded) @reboot /bin/echo reboot |/usr/bin/mail -s start-up at `date` [EMAIL PROTECTED] It has worked without any problems delivering an email indicating start-up time. Now... Well, here's some lines from the 'mqueue' file: H??Received: from zebra.athome.net (localhost.athome.net [127.0.0.1]) by zebra.athome.net (8.13.3/8.13.3) with ESMTP id l33AFhEA000481 for [EMAIL PROTECTED]; Tue, 3 Apr 2007 06:15:44 -0400 (EDT) (envelope-from [EMAIL PROTECTED]) H??Received: (from [EMAIL PROTECTED]) by zebra.athome.net (8.13.3/8.13.3/Submit) id l33AFhqS000433 for [EMAIL PROTECTED]; Tue, 3 Apr 2007 06:15:43 -0400 (EDT) (envelope-from root) It seems that my local network name of athome.net is being evaluated. From 'whois athome.net' -- Domain Name: ATHOME.NET Registrar: NETWORK SOLUTIONS, LLC. Whois Server: whois.networksolutions.com Referral URL: http://www.networksolutions.com Name Server: NS3.LAMEDELEGATION.NET Name Server: NS4.LAMEDELEGATION.NET Status: clientTransferProhibited Updated Date: 02-apr-2007 Creation Date: 30-nov-1999 Expiration Date: 30-nov-2015 It's been around since 1999, but was updated yesterday. I'm assuming I did something wrong years back in my 'sendmail' setup. At this point, I certainly don't remember the whys hows of what I did! Could someone *please* help? Thanks! V ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help! Mail to 'localhost' not staying local CORRECTION
Check that localhost is defined in /etc/hosts and your name resolution is working in /etc/nsswitch.conf Thanks for your continued input! /etc/nsswitch.conf has never been changed: group: compat group_compat: nis hosts: files dns networks: files passwd: compat passwd_compat: nis shells: files Sorry all -- I'm at work an bouncing between 3-machines and copied a line wrong: The following is correct: /etc/hosts is also the same as years-back: ::1 localhost.athome.net localhost 127.0.0.1 localhost.athome.net localhost 192.168.254.250 zebra.athome.net zebra 192.168.254.250 zebra.athome.net. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help! Mail to 'localhost' not staying local CORRECTION
I don't think your hosts file is correct, unless you are telling me you own the domain athome.net. You need to use a domain name you own or one that is not in use. OK. No I don't own athome.net. BUT I've been using it for years without problems -- until today! As I said, the hosts file is it's always been. It seems that localhost just isn't local any more. I'm trying to figure what's changed and what I should do about it. So far, I've stopped all the internal mail to localhost. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help! Mail to 'localhost' not staying local CORRECTION
My guess is that DNS was propagated and now athome.net is in the maps of the DNS server you query. Probably. But (from orig post): Domain Name: ATHOME.NET Status: clientTransferProhibited Updated Date: 02-apr-2007 Creation Date: 30-nov-1999 Expiration Date: 30-nov-2015 whois shows an update yesterday and creation 8-years ago. Presumably, something happened based on the update... Just change your /etc/hosts file, you can use a domain suffix that does not exist for instance. Yes -- that works. I'd changed .net to .nzt and localhost works again. I've spent the last couple hours trying to get sendmail to not do a DNS for specified-local addresses. Lots of google-info, but none that directly works. Much to be assimilated -- I'm pretty sure there's a sendmail solution too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Post DST changes
On Mon, 12 Mar 2007, Mike Tancsa wrote: I am seeing some inconsistent and strange results after the DST change this weekend. On all the boxes, it seems setup OK ... yet different behaviour. Any idea whats up ? This is the same thing I asked about yesterday (Daylight Savings Time -- /etc/localtime and what else?) w/o responses From what I could tell, virtually every process needed a restart. sshd, cron, sendmail, et al were running an hour off. I guess they have a time ref based on their original start-up. After I restarted them all, I ended up doing a reboot anyway -- I wasn't sure if everything had been caught and I didn't want a Monday morning surprise. Today -- all seems OK. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Daylight Savings Time -- /etc/localtime and what else?
A month ago I downloaded tzdata2007b.tar.gz, compiled it and installed a new /etc/localtime. All seemed OK. Now, after the time change, I've had to restart both 'fetchmail' and 'sendmail' to get '/var/log/maillog' in-sync with the new time. Not a problem; apparently these processes use time-data based on their original startup. But what else needs to be restarted? 'top' (edited) for root shows: PID STATETIME WCPUCPU COMMAND 242 select 4:37 0.00% 0.00% syslogd 386 nanslp 3:28 0.00% 0.00% cron 418 select 0:32 0.00% 0.00% inetd 18001 select 0:01 0.00% 0.00% sshd 6985 RUN 0:00 0.00% 0.00% top 6844 pause0:00 0.00% 0.00% csh 423 ttyin0:00 0.00% 0.00% getty (x8 Lines) 167 pause0:00 0.00% 0.00% adjkerntz 224 select 0:00 0.00% 0.00% devd Maybe 'cron' -- daily security email is an hour off. Should I just restart the whole system? (FreeBSD 5.4, i386) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Is a re-boot req'd after changing 'resolv.conf' ?
I'm simply going to change 2 nameserver ip-addresses. Most of what I've found re. 'resolv.conf' implies it can just be changed on-the-fly. However, other sources (mostly upgrading info) have a reboot involved. So -- re-boot or not? (Note: this is a static-ip box running v5.4.) Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pkg_add question
Generally -- is it OK to do a 'pkg_add' from 'packages-6-stable' to a 5.4 system? Specifically, I think I need to update 'fetchmail.' What I've read *seems* to indicate it's OK, but... Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_add question
V.I.Victor wrote: Generally -- is it OK to do a 'pkg_add' from 'packages-6-stable' to a 5.4 system? Specifically, I think I need to update 'fetchmail.' What I've read *seems* to indicate it's OK, but... Well I guess it works, but why not just cvsup your ports ( or use portsnap ) and use portupgrade to update your ports ? In general that would be the best Idea -- -Frank Staals This is a small machine that is only used as an email front-end. When I built it I didn't install 'ports' -- sorry, I should have mentioned that in the original post. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_add question
-Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 9, 2006 03:02 PM On Wed, Aug 09, 2006 at 01:43:10PM +, V.I.Victor wrote: Generally -- is it OK to do a 'pkg_add' from 'packages-6-stable' to a 5.4 system? Absolutely not. Specifically, I think I need to update 'fetchmail.' What's wrong with using packages-5-stable? :-) Probably nothing! I (wrongly) thought that *all* 5.x package/paths had the same version of 'fetchmail' and when I found the new 'fetchmail' in 6.x I figured that was where I had to get it. I'll try a 'pkg_add' from packages-5-stable as soon as I can stop the system for a while. Thanks for the pointer! Although I should probably have installed ports during the original install -- I didn't. Now, it seems a long way to go just to see if the newest version of 'fetchmail' fixes its problem (I'm not confident it will) What I've read *seems* to indicate it's OK, but... Where did you read this, so we can try to correct the bogus advice? Hard to say. I did 6-8 Google searches with various keys trying to find some specifics for adding packages between FreeBSD versions. The *seems*...OK I mentioned may have been in relation to simple programs. I don't know. Since I was unable to find anything solid, I asked here! Again -- Thank-you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Every 12-hrs -- ad0: TIMEOUT - WRITE DMA
On Sun, 19 Feb 2006, Mike Tancsa wrote: On Sun, 19 Feb 2006 22:21:04 +, in sentex.lists.freebsd.questions you wrote: On Thu, 16 Feb 2006, Mike Tancsa wrote: For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been reporting: Feb 12 12:08:05 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279 Feb 13 00:08:51 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279 Feb 13 12:09:38 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2963331 Feb 14 00:10:24 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2705947 So -- can anyone help track this down? It sounds like a hardware issue. Install /usr/ports/sysutils/smartmontools and ask the drive to see whats up. I installed 'smartmontools' but haven't used as yet. I've been waiting to see what happens -- the problem simply stopped. There've been no ad0: TIMEOUT messages for 3-days. The errors get logged in the drive so you dont have to wait for more errors to happen. Start it running now so you can see if any of the bad counters are changing as well as to ask the drive what it was. My guess is you have some bad sectors the drive remapped. OK. No problems found... And -- still -- no more ad0: TIMEOUTs But, I'm not really surprised. As mentioned in the original post, a 2-gig file had been created that presumably moved-past any bad sector patches; approx. midway during the TIMEOUT report period. Plus -- since the drive is (was) storing email, writing logs, etc. 24-hrs a day, it seems improbable that bad-sectors would only show-up every 12-hrs. Although I'm uncomfortable with magic-fixes, I wonder if there's more than a coincidental connection between setting the date and the reports starting and stopping. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Every 12-hrs -- ad0: TIMEOUT - WRITE DMA
On Thu, 16 Feb 2006, Mike Tancsa wrote: For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been reporting: Feb 12 12:08:05 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279 Feb 13 00:08:51 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279 Feb 13 12:09:38 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2963331 Feb 14 00:10:24 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2705947 So -- can anyone help track this down? It sounds like a hardware issue. Install /usr/ports/sysutils/smartmontools and ask the drive to see whats up. I installed 'smartmontools' but haven't used as yet. I've been waiting to see what happens -- the problem simply stopped. There've been no ad0: TIMEOUT messages for 3-days. The only thing done outside of the ordinary, prior to the messages stopping, was to set the date. It's probably a coincidence but setting the date was also the last thing done before the the messages started. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Every 12-hrs -- ad0: TIMEOUT - WRITE DMA
For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been reporting: Feb 12 12:08:05 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279 Feb 13 00:08:51 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279 Feb 13 12:09:38 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2963331 Feb 14 00:10:24 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2705947 Feb 14 12:11:09 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2706335 Feb 15 00:12:02 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2832383 Feb 15 12:12:57 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=139839 Feb 16 00:13:50 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=131391 Feb 16 12:14:36 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=131391 The system was created Jan 08 and, prior to the above, the ad0: timeout had only been reported twice: Jan 25 11:43:34 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=17920255 Feb 6 11:59:42 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2832383 Before to asking here, I did several searches for possible causes. I think I've eliminated disk spin-down and bad-block-mapping -- just before the Feb 15, 12:12 period a 2-gig file was created; leaving the disk 'spinning' and bad-blocks presumably bypassed. Another found item said that some IBM drives recalibrate every 25-hours. Interesting concept, but a different period and without previous history. Lastly, several items referred to changing PREEMPTION but never seemed to reach a final conclusion. I also checked the cron log and found nothing running at the timeout times. So -- can anyone help track this down? Final note: the hardware is an old, resurrected Win98 machine running 24/7 and is used only for email processing. I installed it primarily as a proof of concept, so it can be replaced if necessary. Some specifics: FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 CPU: AMD-K7(tm) Processor (598.84-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x612 Stepping = 2 Features=0x81f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,MMX AMD Features=0xc040AMIE,DSP,3DNow! real memory = 134152192 (127 MB) avail memory = 121630720 (115 MB) ACPI disabled by blacklist. Contact your BIOS vendor. ad0: 14664MB IBM-DJNA-351520/J56OA30K [29795/16/63] at ata0-master UDMA66 acd0: CDROM CREATIVE CD5233E/C2.05 at ata1-master PIO4 Thanks for any help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
