Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 01 Mar 2006 10:00:14 -0600
From:      Paul Schmehl <pauls@utdallas.edu>
To:        ports@FreeBSD.org
Subject:   Re: FreeBSD Port: mpack-1.6
Message-ID:  <BCA5F50D2461133FF65B3BD8@utd59514.utdallas.edu>
In-Reply-To: <44050D77.2030503@j2d.lam.net.au>
References:  <44050D77.2030503@j2d.lam.net.au>

next in thread | previous in thread | raw e-mail | index | archive | help
--On Wednesday, March 01, 2006 13:56:55 +1100 Nik Lam 
<freebsdnik@j2d.lam.net.au> wrote:

> Hi,
>
> I'm having trouble running the latest mpack (1.6) on FreeBSD 5.4.
>
Since posting the patches last night, that changed the "/usr/tmp" path to 
"/tmp" in some source files, a new problem has emerged.

If you do this:
 ktrace mpack -s "Testing" Makefile pauls@utdallsa.edu

It results in this:
|\uffff(\uffff\uffff\uffff\uffff\uffff&(\uffff(: File exists

Ktrace shows this:
 79012 mpack    CALL  open(0x804f060,0xa02,0x1a4)
 79012 mpack    NAMI  "/tmp/mpackCl8rPI"
 79012 mpack    RET   open -1 errno 17 File exists
 79012 mpack    CALL  writev(0x2,0xbfbfcb20,0x4)
 79012 mpack    GIO   fd 2 wrote 31 bytes
       0x0000 7c90 1328 f4d3 bfbf e026 0528 a414 0728  ||..(.....&.(...(|
       0x0010 013a 2046 696c 6520 6578 6973 7473 0a    |.: File exists.|

 79012 mpack    RET   writev 31/0x1f
 79012 mpack    CALL  exit(0x1)

I've looked through the source code, but I'm not sure where the problem is. 
I only see one call to open the file.  Can someone help?

Paul Schmehl (pauls@utdallas.edu)
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/ir/security/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BCA5F50D2461133FF65B3BD8>