Try truncating some files.
-Kip
On Tue, Jul 28, 2009 at 8:29 PM, grarpamp wrote:
> One week old build...
>
> # df -i .
> Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on
> ram01/mnt1 239465344 239465344 0 100% 13163 0 100% /mnt1
> # ls -aliT zero
> 207
One week old build...
# df -i .
Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on
ram01/mnt1 239465344 239465344 0 100% 13163 0 100% /mnt1
# ls -aliT zero
20797 -rw-r--r-- 1 user user 43515904 Jul 28 23:20:57 2009 zero
# rm -f zero
rm: zero: No space l
I have a pair on boxes running 7.2-RELEASE/i386 and have found that
it is generating stray RST packets. As an example,
ssh server echo hello
will generate a sequence like the following (as seen on the server):
10:03:29.277427 IP client.55871 > server.22: S 1808736437:1808736437(0) win
49640
1
On Tue, 28 Jul 2009, Andrew Reilly wrote:
On Mon, Jul 27, 2009 at 06:13:07PM -0700, Doug Barton wrote:
On Tue, 28 Jul 2009, Andrew Reilly wrote:
corresponding to port revisions. Portmaster was checking the
installed version against the MD5 hashes in the "old" version
+CONTENTS file, and they
On Tue, 28 Jul 2009, Ben Morrow wrote:
Yes, I can see it needs to be an option. Presumably 'don't ask me again' is
too Microsoft :)? Maybe something like 'Mark this package as explicitly
required?'? That's pretty much the user-visible effect.
Thanks for the suggestions.
I know the first time
On Tue, Jul 28, 2009 at 11:03:50AM -0400, Dan wrote:
> Kostik Belousov wrote:
> >I highly suspect that your problem was fixed by r194815.
>
> Will this fix work on a release, or would it be best to upgrade to the
> stable branch.
If it is applicable without conflicts, then most likely it will wo
Kostik Belousov wrote:
On Tue, Jul 28, 2009 at 10:33:16AM -0400, Dan wrote:
Hi,
One of my servers running 7.2-RELEASE-p2 is crashing about every 2 or 3
days with the following backtrace. This particular one is from July
24.I still have all the vmcores available if any further info is require
On Tue, Jul 28, 2009 at 10:33:16AM -0400, Dan wrote:
> Hi,
>
> One of my servers running 7.2-RELEASE-p2 is crashing about every 2 or 3
> days with the following backtrace. This particular one is from July
> 24.I still have all the vmcores available if any further info is required.
>
>
> Fatal
Hi,
One of my servers running 7.2-RELEASE-p2 is crashing about every 2 or 3
days with the following backtrace. This particular one is from July
24.I still have all the vmcores available if any further info is required.
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
f
Doug Barton wrote:
On Thu, 23 Jul 2009, Ben Morrow wrote:
The problem with that is if you install pkg A deliberately, but it then
later becomes a dependancy of pkg B. If you remove pkg B (because it's
no longer needed) there is then no evidence that pkg A was installed on
purpose, rather than i
On Mon, Jul 27, 2009 at 06:13:07PM -0700, Doug Barton wrote:
> On Tue, 28 Jul 2009, Andrew Reilly wrote:
> >corresponding to port revisions. Portmaster was checking the
> >installed version against the MD5 hashes in the "old" version
> >+CONTENTS file, and they weren't matching.
>
> FYI, portmast
On Tue, Jul 28, 2009 at 09:23:03AM +0200, Václav Haisman wrote:
> Andrew Reilly wrote:
> > Problem solved!
> >
> > In case anyone is interested, or has encountered a similar
> > problem, I believe that my problem was that somehow my
> > /var/db/pkg directory had a whole pile of near-duplicate entr
> This sort of mechanism has been suggested before, but the problem you
> described (ports installed "on purpose" becoming a dependency of something
> else) is not an easy one to solve.
I don't earlly see why that is a "problem" tha needs solving. cerrtainl
all I want is to be able to list ports
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew Reilly wrote:
> Problem solved!
>
> In case anyone is interested, or has encountered a similar
> problem, I believe that my problem was that somehow my
> /var/db/pkg directory had a whole pile of near-duplicate entries
> corresponding to port
14 matches
Mail list logo