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 d
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
___
fr
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 dir
On Wed, 22 Aug 2012 21:24:47 -0700
Michael Sierchio wrote:
> On Wed, Aug 22, 2012 at 7:17 PM, RW
> 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
Btw, is /etc/locate.rc being read at all?
/Andy
On Thu, Aug 23, 2012 at 11:04 AM, 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 (even the most
> obvio
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 loc
On Wed, Aug 22, 2012 at 7:17 PM, RW 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 writing to the tmpfs when
On Wed, 22 Aug 2012 17:35:29 -0700
Michael Sierchio wrote:
> On Wed, Aug 22, 2012 at 3:29 PM, RW
> 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 o
On Wed, Aug 22, 2012 at 5:43 PM, Polytropon 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" in
> /etc/rc
On Wed, 22 Aug 2012 17:35:29 -0700, Michael Sierchio wrote:
> On Wed, Aug 22, 2012 at 3:29 PM, RW 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
On Wed, Aug 22, 2012 at 3:29 PM, RW 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 fs is read
only (or read m
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
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 an
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 o
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
___
freebsd-questio
> 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"
> To: freebsd-questions@freebsd.org
> Subject: Re: /tmp filesystem full
>
> On Wed, 22 Aug 2012 08:14:35 -0500 (CDT)
> R
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 /us
On Wed, 22 Aug 2012 08:14:35 -0500 (CDT)
Robert Bonomi wrote:
> > 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
> > To: freebsd-questions
> > Subject: /tmp filesystem full
> &g
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).
> 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
> To: freebsd-questions
> Subject: /tmp filesystem full
>
> Hi,
> I have about 500MB in my /tmp and it seems to be too small when the
>
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
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 I
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 wrote:
> Thanks to all for your input!
>
> Editing /etc/periodic.rc seem to do the trick, but now I fac
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 thank
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 symb
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 con
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 /us
Hi,
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 s
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 is
On Thu, 22 Jan 2009 10:24:39 -0900, Mel
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 does changes to the file system
when
On Thursday 15 January 2009 13:37:06 Polytropon wrote:
> On Thu, 15 Jan 2009 21:37:24 +0100, "Andy Wodfer" 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 least
On Thu, 15 Jan 2009 21:37:24 +0100, "Andy Wodfer" 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 use -y, fsck i
On Wed, Jan 14, 2009 at 7:34 PM, 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: filesyste
On Wed, Jan 14, 2009 at 8:27 PM, Glen Barber wrote:
> On Wed, Jan 14, 2009 at 1:34 PM, 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:
> >
>
> [snip]
>
> >
> > # df -h
> > Filesystem SizeUsed
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
>
On Wed, Jan 14, 2009 at 1:34 PM, 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:
>
[snip]
>
> # df -h
> Filesystem SizeUsed Avail Capacity Mounted on
> /dev/ar0s1a989M 53M857M 6%
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/ar0s1a98
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!!!
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, a
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.
___
freebsd-questions
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
___
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 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
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 t
On Dec 12, 2007, at 2:19 PM, Jerry McAllister wrote:
[EMAIL PROTECTED] wrote:
I even restarted the server but the problem is still there.
this is what I got every amount of time (not always).
root mail.local 89873 /tmp 4 -rw---
616886272 rw
I don´t understand why mail
>> Apparently someone out there keeps trying to resend that awful
>> huge mail file, so whenever you restart, it gets stuck in that
>> same condition. If you can track down the source of the file,
>> either nuke it or block it.
In addition to finding the actual cause of the problem, you may want
On Wed, Dec 12, 2007 at 05:56:23PM -0600, Cesar Amaya wrote:
>
> >
> >Apparently someone out there keeps trying to resend that awful
> >huge mail file, so whenever you restart, it gets stuck in that
> >same condition. If you can track down the source of the file,
> >either nuke it or block it.
>
Apparently someone out there keeps trying to resend that awful
huge mail file, so whenever you restart, it gets stuck in that
same condition. If you can track down the source of the file,
either nuke it or block it.
jerry
___
freebsd-questi
--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
On Wed, Dec 12, 2007 at 04:11:24PM -0600, Cesar Amaya 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
> >how much space
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 proble
--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---
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
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
___
freebsd-questio
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 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
: 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
58 matches
Mail list logo
