[...]
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
-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
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
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
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
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
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
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
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 =
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`
, 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
/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
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
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
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
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 --
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
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!
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
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
-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
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
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
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
24 matches
Mail list logo
