Hi everybody!
Thanks for answering my questions and helping me out with this problem.
It's been fixed now and I managed to locate the problem with the find /
-type d | awk 'length 900' command.
What caused it was something that looked like a directory loop or at least
a very deep list of sub
Can't seem to figure out the problem with MAXPATHLEN.
locate: integer out of +-MAXPATHLEN (1024): 1029
In my /etc/locate.rc I have pruned several directories (even the most
obvious) - still the locate DB exeeds well over 1GB before outputting this
error message.
I have moved the tmp dir for
Btw, is /etc/locate.rc being read at all?
/Andy
On Thu, Aug 23, 2012 at 11:04 AM, Andy Wodfer wod...@gmail.com wrote:
Can't seem to figure out the problem with MAXPATHLEN.
locate: integer out of +-MAXPATHLEN (1024): 1029
In my /etc/locate.rc I have pruned several directories (even the
On Wed, 22 Aug 2012 21:24:47 -0700
Michael Sierchio wrote:
On Wed, Aug 22, 2012 at 7:17 PM, RW rwmailli...@googlemail.com
wrote:
tmpfs and swap md devices don't actually need swap. I don't seen
any advantage in your way of creating an md device for /tmp.
Then you don't understand. ;-)
On Thu, 23 Aug 2012 09:54:08 -0400, kpn...@pobox.com wrote:
On Thu, Aug 23, 2012 at 11:04:02AM +0200, Andy Wodfer wrote:
Can't seem to figure out the problem with MAXPATHLEN.
locate: integer out of +-MAXPATHLEN (1024): 1029
In my /etc/locate.rc I have pruned several directories
Andy Wodfer wodfer at gmail.com
Thu Aug 23 09:04:08 UTC 2012
Can't seem to figure out the problem with MAXPATHLEN.
locate: integer out of +-MAXPATHLEN (1024): 1029
Your database may be corrupted. I would suggest you delete it and
recreate.
jb
___
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply remove it
and create a symbolic link ln -s to say /usr/tmp instead (where I have
several hundred GBs free)?
PS! This
Hi,
On Wed, 22 Aug 2012 12:59:13 +0200
Andy Wodfer wod...@gmail.com wrote:
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply
remove it and create a symbolic link
On Wed, 22 Aug 2012 12:59:13 +0200
Andy Wodfer wrote:
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply
remove it and create a symbolic link ln -s to say /usr/tmp
RW writes:
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
There's also a periodic script to remove older files from /tmp which
may help.
My gut reaction is: what's taking up so much room?
My /tmp contains
El día Wednesday, August 22, 2012 a las 12:59:13PM +0200, Andy Wodfer escribió:
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply remove it
and create a symbolic
Thanks to all for your input!
Editing /etc/periodic.rc seem to do the trick, but now I faced a different
problem which I've never seen before:
locate: integer out of +-MAXPATHLEN (1024): 1029
There are some directories that contains A LOT of small files I think. Need
to investigate.
Also
How can I find which directories break the MAXPATHLEN variable?
or can I somehow run the periodic script in verbose mode to see the output?
/Andy
On Wed, Aug 22, 2012 at 2:04 PM, Andy Wodfer wod...@gmail.com wrote:
Thanks to all for your input!
Editing /etc/periodic.rc seem to do the trick,
Le 22/08/2012 12:59, Andy Wodfer a écrit :
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply remove it
and create a symbolic link ln -s to say /usr/tmp instead (where
On Wed, 22 Aug 2012 12:59:13 +0200, Andy Wodfer wod...@gmail.com wrote:
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply remove
it
and create a symbolic link ln
From owner-freebsd-questi...@freebsd.org Wed Aug 22 05:59:52 2012
Date: Wed, 22 Aug 2012 12:59:13 +0200
From: Andy Wodfer wod...@gmail.com
To: freebsd-questions freebsd-questions@freebsd.org
Subject: /tmp filesystem full
Hi,
I have about 500MB in my /tmp and it seems to be too small when
On Wed, 22 Aug 2012 14:12:25 +0200, Andy Wodfer wrote:
How can I find which directories break the MAXPATHLEN variable?
It's easy to do this with find and awk:
% find / -type d | awk 'length LIMIT'
where LIMIT is the numerical value you want to be exceeded (in
your case, MAXPATHLEN).
: /tmp filesystem full
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply
remove it and create a symbolic link ln -s to say /usr/tmp instead
(where I have
Andy Wodfer wrote at 12:59 +0200 on Aug 22, 2012:
Hi,
I have about 500MB in my /tmp and it seems to be too small when the
periodic LOCATE script runs every week.
What's the best way to increase the size of /tmp ? Could I simply remove it
and create a symbolic link ln -s to say /usr/tmp
From owner-freebsd-questi...@freebsd.org Wed Aug 22 08:27:59 2012
Date: Wed, 22 Aug 2012 14:25:51 +0100
From: Steve O'Hara-Smith st...@sohara.org
To: freebsd-questions@freebsd.org
Subject: Re: /tmp filesystem full
On Wed, 22 Aug 2012 08:14:35 -0500 (CDT)
Robert Bonomi bon...@mail.r
If you use zfs, that is easy... zfs set quota=NNG pool/tmp
if not
try to mount tmp in memory...
in /etc/rc.conf
tmpmfs=YES
tmpsize=400m
reboot
this would create a /tmp in memory (swap)
size=400 Megabytes
Sergio
___
This will happen automatically if you go to multiuser without a
writeable /tmp. See /etc/rc.d/tmp
I have a problem with the semantics of the rc scripts for this and
var, though - if you are going to use a memory-backed filesystem, you
should reserve all the space at the outset. Bad things can
On Wed, 22 Aug 2012 14:14:17 -0700
Michael Sierchio wrote:
This will happen automatically if you go to multiuser without a
writeable /tmp. See /etc/rc.d/tmp
It doesn't, the default is an old-fashioned md device, not tmpfs.
I have a problem with the semantics of the rc scripts for this and
On Wed, 22 Aug 2012 23:21:12 +0100
RW wrote:
On Wed, 22 Aug 2012 14:14:17 -0700
Michael Sierchio wrote:
This will happen automatically if you go to multiuser without a
writeable /tmp. See /etc/rc.d/tmp
It doesn't, the default is an old-fashioned md device, not tmpfs.
Sorry I misread
On Wed, Aug 22, 2012 at 3:29 PM, RW rwmailli...@googlemail.com wrote:
Sorry I misread the previous post which *was* referring to an md device,
but the rest is right.
Not really. ;-) The one compelling reason to use an md filesystem for
/tmp or /var is when you have no swap, and/or your root
On Wed, 22 Aug 2012 17:35:29 -0700, Michael Sierchio wrote:
On Wed, Aug 22, 2012 at 3:29 PM, RW rwmailli...@googlemail.com wrote:
Sorry I misread the previous post which *was* referring to an md device,
but the rest is right.
Not really. ;-) The one compelling reason to use an md
On Wed, Aug 22, 2012 at 5:43 PM, Polytropon free...@edvax.de wrote:
For the mentioned appliances, that would not be a problem.
However there's a distinction between /tmp and /var/tmp
that can be summarized like this: The content of /tmp may
disappear after a reboot (see clear_tmp_enable=YES
On Wed, 22 Aug 2012 17:35:29 -0700
Michael Sierchio wrote:
On Wed, Aug 22, 2012 at 3:29 PM, RW rwmailli...@googlemail.com
wrote:
Sorry I misread the previous post which *was* referring to an md
device, but the rest is right.
Not really. ;-) The one compelling reason to use an md
On Wed, Aug 22, 2012 at 7:17 PM, RW rwmailli...@googlemail.com wrote:
tmpfs and swap md devices don't actually need swap. I don't seen any
advantage in your way of creating an md device for /tmp.
Then you don't understand. ;-) The advantage of my approach is
avoiding a kernel panic when
On ia64 8.0-beta1 SMP mutt-devel-1.5.20_1 freezes on some folders with
/tmp: write failed, filesystem is full
Could not copy message
top shows that mutt is in wdrain state and in /var/log/messages I see
kernel: pid 43702 (mutt), uid 1001 inumber 23554 on /tmp: filesystem
, to correct the problem, I log into the router, removed the big
log and several other files in /var to free up some space, and assumed
this would correct the problem.
It did not.
Several minutes after freeing up a lot of space on /var, I continued
to get filesystem full messages and df continued to show
policies.
So, to correct the problem, I log into the router, removed the big
log and several other files in /var to free up some space, and assumed
this would correct the problem.
It did not.
Several minutes after freeing up a lot of space on /var, I continued
to get filesystem full
filesystem full messages and df continued to show the
capacity at 100%. I checked df -i for the inodes too. That was
fine. I ran a quick fsck to see if that might shock the system into
seeing all the space that I'd freed up, but no good.
I ended up rebooting the box.
Was there any other possible
on /var, I continued
to get filesystem full messages and df continued to show the
capacity at 100%. I checked df -i for the inodes too. That was
fine. I ran a quick fsck to see if that might shock the system into
seeing all the space that I'd freed up, but no good.
I ended up rebooting the box
On Friday 22 May 2009 18:19:25 Steve Bertrand wrote:
# pkg_add -r lsof
Or use the native fstat(1).
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
On Fri, 22 May 2009, Steve Bertrand wrote:
Luke Dean wrote:
I ended up rebooting the box.
Was there any other possible solution I could've tried?
You have to restart the service that was holding the log file(s) open.
The system does not release the space while an application is 'using'
On Thursday 15 January 2009 13:37:06 Polytropon wrote:
On Thu, 15 Jan 2009 21:37:24 +0100, Andy Wodfer wod...@gmail.com wrote:
Added context:
Here's the output of fsck (this was a new command to me):
# fsck
** /dev/ar0s1a (NO WRITE)
Should I run fsck -y? Is it safe to do so?
At
On Thu, 22 Jan 2009 10:24:39 -0900, Mel fbsd.questi...@rachie.is-a-geek.net
wrote:
In short: reboot in single user mode, then run fsck -y at the prompt.
Never ever run fsck -y on a live filesystem.
A very good hint. Didn't I mention it? No? Bad idea.
Background concept: The fsck utility
On Wed, Jan 14, 2009 at 8:27 PM, Glen Barber glen.j.bar...@gmail.comwrote:
On Wed, Jan 14, 2009 at 1:34 PM, Andy Wodfer wod...@gmail.com wrote:
Hi,
I'm getting an error message every week and I can't seem to understand
why
nor manage to fix it. Here it is:
[snip]
# df -h
On Wed, Jan 14, 2009 at 7:34 PM, Andy Wodfer wod...@gmail.com wrote:
Hi,
I'm getting an error message every week and I can't seem to understand why
nor manage to fix it. Here it is:
#dmesg
[snip]
pid 54753 (locate.code), uid 65534 inumber 23557 on /tmp: filesystem full
# df -h
On Thu, 15 Jan 2009 21:37:24 +0100, Andy Wodfer wod...@gmail.com wrote:
Should I run fsck -y? Is it safe to do so?
At least, fsck will do its best to repair the defective file system.
As you have seen from the messages, you will surely lose some files
when their information gets cleared. If you
Hi,
I'm getting an error message every week and I can't seem to understand why
nor manage to fix it. Here it is:
#dmesg
[snip]
pid 54753 (locate.code), uid 65534 inumber 23557 on /tmp: filesystem full
# df -h
Filesystem SizeUsed Avail Capacity Mounted on
/dev/ar0s1a989M 53M
On Wed, Jan 14, 2009 at 1:34 PM, Andy Wodfer wod...@gmail.com wrote:
Hi,
I'm getting an error message every week and I can't seem to understand why
nor manage to fix it. Here it is:
[snip]
# df -h
Filesystem SizeUsed Avail Capacity Mounted on
/dev/ar0s1a989M 53M
On 01/14/2009 10:34 AM, Andy Wodfer wrote:
Hi,
I'm getting an error message every week and I can't seem to understand why
nor manage to fix it. Here it is:
#dmesg
[snip]
pid 54753 (locate.code), uid 65534 inumber 23557 on /tmp: filesystem full
# df -h
Filesystem SizeUsed
Booting into single-user via serial console, KVM, KVM-over-IP, or
iLO/LOM (if HP/Compaq) is sufficient. If you have servers which are
remote and you lack any of these features, I'm both surprised and not
sure what to tell you. You'll encounter this problem with any OS, not
just FreeBSD.
I'm
may not be
reclaimed if a process still has the file open.
but even if you run df -ki in the exact moment of when the filesystem full
messages are appearing in the logs, it reports of having 40G free and a
lot of free inodes.
If you reboot the machine or restart some of the applications
On Thu, Nov 13, 2008 at 02:05:28PM +0300, Varshavchick Alexander wrote:
Booting into single-user via serial console, KVM, KVM-over-IP, or
iLO/LOM (if HP/Compaq) is sufficient. If you have servers which are
remote and you lack any of these features, I'm both surprised and not
sure what to tell
On Wed, Nov 12, 2008 at 05:26:58PM +0300, Varshavchick Alexander wrote:
I would start by taking the machine down, booting it into single-user,
and running fsck -y. background fsck does not catch all errors.
Okay then, are there any ways of performing it remotely, without my going
to the
I have an old enough server with FreeBSD 5.4 which from time to time
complains about filesystem full. But the problem is that the partition in
question has about 15G free space and more than 1000 free inodes. Then
all by itself the error dissapears, only to be repeated several hours
later
On Wed, Nov 12, 2008 at 03:34:11PM +0300, Varshavchick Alexander wrote:
I have an old enough server with FreeBSD 5.4 which from time to time
complains about filesystem full. But the problem is that the partition in
question has about 15G free space and more than 1000 free inodes
, full fsck -y was done all the
same. But you're right, running fsck -y once again will not harm.
Also, how soon do you check the box to see how much space/free inodes it
has after receiving a filesystem full error? Are we talking I
checked it 4-5 hours later, or I checked it 30 seconds after
On Wed, Nov 12, 2008 at 03:34:11PM +0300, Varshavchick Alexander wrote:
I have an old enough server with FreeBSD 5.4 which from time to time
complains about filesystem full. But the problem is that the partition in
question has about 15G free space and more than 1000 free inodes
I have an old enough server with FreeBSD 5.4 which from time to time
complains about filesystem full. But the problem is that the partition
in question has about 15G free space and more than 1000 free inodes.
Then all by itself the error dissapears, only to be repeated several hours
later
Le Wednesday 12 November 2008, Varshavchick Alexander a écrit :
I have an old enough server with FreeBSD 5.4 which from time to time
complains about filesystem full. But the problem is that the partition
in question has about 15G free space and more than 1000 free inodes.
Then all
of the applications, does
the issue disappear ?
Regards,
Adrian.
On Wed, Nov 12, 2008 at 1:05 PM, Varshavchick Alexander
[EMAIL PROTECTED] wrote:
I have an old enough server with FreeBSD 5.4 which from time to time
complains about filesystem full. But the problem is that the partition in
question
Varshavchick Alexander wrote:
I have an old enough server with FreeBSD 5.4 which from time to time
complains about filesystem full. But the problem is that the partition
in question has about 15G free space and more than 1000 free inodes.
Then all by itself the error dissapears, only
I would start by taking the machine down, booting it into single-user,
and running fsck -y. background fsck does not catch all errors.
Okay then, are there any ways of performing it remotely, without my going
to the data center and standing near the server for an hour while it
checks? I mean
During make installkernel KERNCONF=GENERIC I get
/: write failed, filesystem is full
install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device
*** Error code 71
output of df -H gives
Filesystem SizeUsed Avail Capacity Mounted on
/dev/ad0s1a260M259M-20M 108%
In response to Leslie Jensen [EMAIL PROTECTED]:
During make installkernel KERNCONF=GENERIC I get
/: write failed, filesystem is full
install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device
*** Error code 71
output of df -H gives
Filesystem SizeUsed Avail
Bill Moran skrev:
In response to Leslie Jensen [EMAIL PROTECTED]:
During make installkernel KERNCONF=GENERIC I get
/: write failed, filesystem is full
install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device
*** Error code 71
output of df -H gives
Filesystem SizeUsed
Leslie Jensen writes:
/: write failed, filesystem is full
install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device
*** Error code 71
My question is can I get around this or have I made my / slice to
small?
Yes. :-)
Start by cleaning up /; usually that
On Mon, Apr 21, 2008 at 05:44:43PM +0200, Leslie Jensen wrote:
During make installkernel KERNCONF=GENERIC I get
/: write failed, filesystem is full
install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device
*** Error code 71
output of df -H gives
Filesystem SizeUsed
quoth the Martin Tournoij:
On Mon, Apr 21, 2008 at 05:44:43PM +0200, Leslie Jensen wrote:
During make installkernel KERNCONF=GENERIC I get
/: write failed, filesystem is full
install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device
*** Error code 71
output of df -H gives
quoth the darren kirby:
quoth the Martin Tournoij:
On Mon, Apr 21, 2008 at 05:44:43PM +0200, Leslie Jensen wrote:
During make installkernel KERNCONF=GENERIC I get
/: write failed, filesystem is full
install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device
*** Error
On Mon, Apr 21, 2008 at 06:08:39PM +0200, Leslie Jensen wrote:
Bill Moran skrev:
In response to Leslie Jensen [EMAIL PROTECTED]:
During make installkernel KERNCONF=GENERIC I get
/: write failed, filesystem is full
install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device
On Mon, Apr 21, 2008 at 12:10:03PM -0400, Robert Huff wrote:
Leslie Jensen writes:
/: write failed, filesystem is full
install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device
*** Error code 71
My question is can I get around this or have I made my / slice to
I have an app server that uses mmap a lot. After running a long batch
(four hours, 5,100+ transactions), I got the message filesystem full
(/usr--ufs, local, soft-updates). df -i says plenty of space.
I restarted the batch process, and watched app server process
carefully with fstat -p
Hi,
I'm running FreeBSD 7.0 RC1 on AMD 64, dual Opteron with h/w raid1 (scsi).
I have an app server that uses mmap a lot. After running a long batch
(four hours, 5,100+ transactions), I got the message filesystem full
(/usr--ufs, local, soft-updates). df -i says plenty of space.
I restarted
Matthew Seaman wrote:
David Kelly wrote:
On Mon, Mar 17, 2008 at 06:11:47PM +0100, Erwan David wrote:
I use lsof to get the list of removed files still open (lsof +L1,
useful after a port upgrade to check wether all upgraded daemons
indeed restarted). It seems it's not possible with fstat.
Hi, Ive got a big problem now on a production server.
When i do various things, i am getting write failed, file system full
messages all over the place. Ive gone through and deleted
things i can, and i should have the space now, but its just
not available:
$ df -m
Filesystem 1M-blocks Used
Dr. Jennifer Nussbaum [EMAIL PROTECTED] writes:
Hi, Ive got a big problem now on a production server.
When i do various things, i am getting write failed, file system full
messages all over the place. Ive gone through and deleted
things i can, and i should have the space now, but its just
At 10:34 AM 3/17/2008, Dr. Jennifer Nussbaum wrote:
Hi, Ive got a big problem now on a production server.
When i do various things, i am getting write failed, file system full
messages all over the place. Ive gone through and deleted
things i can, and i should have the space now, but its just
On Mon, Mar 17, 2008 at 08:34:18AM -0700, Dr. Jennifer Nussbaum wrote:
Hi, Ive got a big problem now on a production server.
When i do various things, i am getting write failed, file system full
messages all over the place. Ive gone through and deleted
things i can, and i should have the
i need to get this space released ASAP! Can anyone help?
Please see the FreeBSD FAQ entries on The du and df commands show
different amounts of disk space available. What is going on? and How
is it possible for a partition to be more than 100% full?
Also be sure to: $ alias df=/bin/df
17 maart 2008 16:34
Aan: freebsd-questions@freebsd.org
Onderwerp: Urgent: filesystem full, though space is available
Hi, Ive got a big problem now on a production server.
When i do various things, i am getting write failed, file system full
messages all over the place. Ive gone through and deleted
On Mon, Mar 17, 2008 at 08:34:18AM -0700, Dr. Jennifer Nussbaum wrote:
This is a FAQ and has to do with space reserved for root(system).
Check the FAQs on the FreeBSD web site.
jerry
Hi, Ive got a big problem now on a production server.
When i do various things, i am getting write
Or try to find the culprit with lsof (can't remember the options). You will
see some processes using files you don't have -- kill that process and your
space will be freed.
I hope this helps.
Regards and good luck.
On Mon, Mar 17, 2008 at 5:10 PM, Jerry McAllister [EMAIL PROTECTED] wrote:
In response to Armando Cambra [EMAIL PROTECTED]:
Or try to find the culprit with lsof (can't remember the options). You will
see some processes using files you don't have -- kill that process and your
space will be freed.
You can also use fstat if you don't wan to install Linux software on
In the last episode (Mar 17), Bill Moran said:
In response to Armando Cambra [EMAIL PROTECTED]:
Or try to find the culprit with lsof (can't remember the options).
You will see some processes using files you don't have -- kill
that process and your space will be freed.
You can also use
In response to Dan Nelson [EMAIL PROTECTED]:
In the last episode (Mar 17), Bill Moran said:
In response to Armando Cambra [EMAIL PROTECTED]:
Or try to find the culprit with lsof (can't remember the options).
You will see some processes using files you don't have -- kill
that
Le Mon 17/03/2008, Bill Moran disait
In response to Dan Nelson [EMAIL PROTECTED]:
In the last episode (Mar 17), Bill Moran said:
In response to Armando Cambra [EMAIL PROTECTED]:
Or try to find the culprit with lsof (can't remember the options).
You will see some processes using
On Mar 17, 2008, at 11:34 AM, Dr. Jennifer Nussbaum wrote:
Hi, Ive got a big problem now on a production server.
When i do various things, i am getting write failed, file system
full
messages all over the place. Ive gone through and deleted
things i can, and i should have the space now,
On Mon, Mar 17, 2008 at 06:11:47PM +0100, Erwan David wrote:
I use lsof to get the list of removed files still open (lsof +L1,
useful after a port upgrade to check wether all upgraded daemons
indeed restarted). It seems it's not possible with fstat.
... which is exactly what Jennifer needs
David Kelly wrote:
On Mon, Mar 17, 2008 at 06:11:47PM +0100, Erwan David wrote:
I use lsof to get the list of removed files still open (lsof +L1,
useful after a port upgrade to check wether all upgraded daemons
indeed restarted). It seems it's not possible with fstat.
... which is exactly
On Thu, Dec 13, 2007 at 10:08:08AM -0600, Cesar Amaya wrote:
You should add something like this to your sendmail.mc config:
define(`confMAX_MESSAGE_SIZE', `2100')dnl
...which will set a maximum message size that your SMTP server is
willing to accept. The recommended max size in
You should add something like this to your sendmail.mc config:
define(`confMAX_MESSAGE_SIZE', `2100')dnl
...which will set a maximum message size that your SMTP server is
willing to accept. The recommended max size in the RFCs was something
like 10 MB, but season to taste.
Do I have
On Thu, Dec 13, 2007 at 11:10:33AM -0600, Cesar Amaya wrote:
Huh??? Where else would you put it?
In /etc/mail/sendmail.cf
I think you want to put it in sendmail.mc and then run the make
in /ec/sendmail rather than modify sendmail.cf directly.
jerry
I think you want to put it in sendmail.mc and then run the make
in /ec/sendmail rather than modify sendmail.cf directly.
Do I create the sendmail.mc file from scratch because I don´t have any?
I just have a freebsd.mc file.
___
Huh??? Where else would you put it?
In /etc/mail/sendmail.cf
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Thu, Dec 13, 2007 at 11:35:57AM -0600, Cesar Amaya wrote:
Do I create the sendmail.mc file from scratch because I don´t have any?
I just have a freebsd.mc file.
Be sure to make a backup of /etc/mail/sendmail.cf. Then, should be
able to add the line to /etc/mail/freebsd.mc, run make, and
Be sure to make a backup of /etc/mail/sendmail.cf. Then, should be
able to add the line to /etc/mail/freebsd.mc, run make, and copy
/ett/mail/freebsd.cf to /etc/mail/sendmail.cf.
o.k. it seems it worked, hope don´t get that messages anymore.
thank you very much.
regards!!!
: pid 7240 (mail.local), uid 0 inumber 11
on /tmp: filesystem full
Dec 12 05:51:31 napstats kernel: pid 7240 (mail.local), uid 0 inumber 11
on /tmp: filesystem full
Dec 12 06:18:32 napstats kernel: pid 7303 (mail.local), uid 0 inumber 11
on /tmp: filesystem full
Dec 12 06:21:23 napstats kernel
--On Wednesday, December 12, 2007 11:55:23 -0600 Cesar Amaya
[EMAIL PROTECTED] wrote:
But when I run a df -hi it says 0% of capacity is used on /tmp filesystem.
napstats# df -hi
Filesystem SizeUsed Avail Capacity iusedifree %iused
Mounted on
/dev/ad4s1a989M 76M834M
Cesar Amaya writes:
napstats# fstat | grep /tmp
www httpd 1739 15 /tmp 4 -rw--- 0 rw
Can you afford to shut down the web server (Apache ?)?
Robert Huff
___
Paul Schmehl wrote:
--On Wednesday, December 12, 2007 11:55:23 -0600 Cesar Amaya
[EMAIL PROTECTED] wrote:
But when I run a df -hi it says 0% of capacity is used on /tmp
filesystem.
napstats# df -hi
Filesystem SizeUsed Avail Capacity iusedifree %iused
Mounted on
/dev/ad4s1a
On Wed, Dec 12, 2007 at 03:08:50PM -0600, Cesar Amaya wrote:
Robert Huff wrote:
Cesar Amaya writes:
napstats# fstat | grep /tmp
www httpd 1739 15 /tmp 4 -rw--- 0 rw
Can you afford to shut down the web server (Apache ?)?
Robert Huff wrote:
Cesar Amaya writes:
napstats# fstat | grep /tmp
www httpd 1739 15 /tmp 4 -rw--- 0 rw
Can you afford to shut down the web server (Apache ?)?
Robert Huff
Nothing is shown if I shut down
--On Wednesday, December 12, 2007 16:13:42 -0500 Jerry McAllister
[EMAIL PROTECTED] wrote:
On Wed, Dec 12, 2007 at 03:08:50PM -0600, Cesar Amaya wrote:
Robert Huff wrote:
Cesar Amaya writes:
napstats# fstat | grep /tmp
www httpd 1739 15 /tmp 4 -rw--- 0 rw
Looks like something, maybe your mail program has a large file open -
maybe trying to receive a huge file. Killing the process could get
that file closed and either it would be gone or would finally show
how much space it is holding.
jerry
I even restarted the server but the
--On Wednesday, December 12, 2007 16:11:24 -0600 Cesar Amaya
[EMAIL PROTECTED] wrote:
Looks like something, maybe your mail program has a large file open -
maybe trying to receive a huge file. Killing the process could get
that file closed and either it would be gone or would finally show
1 - 100 of 188 matches
Mail list logo
