List Info

Thread: Debian devkit and /var/tmp
Debian devkit and /var/tmp
user name
 2006-06-01 19:40:00 

  


  

    If I set up a target that doesn't include the debian devkit, and I run an executable that uses /var/tmp, which doesn't exist, for writing temporary (during execution only) files, the executable succeeds.

However, if I set up a target that does include the debian devkit, but I don't actually install it for the target, and I run an executable that use /var/tmp, which doesn't exist, the executable fails, complaining that it can't write the file. If I then 'sb-conf install -d', a /var/tmp dir is created (along with several other /var subdirs) and the executable succeeds.


Note that this only happens when the debian devkit is included in the target setup. If I include just the cputransp devkit and/or the perl devkit, this doesn't happen -- no /var/tmp exists (nor is one created when I later do a 'sb-conf install -d'), but the executable runs fine.


Can someone explain this to me?

Thanks,
Diane


  

  
  
   
     
    

  

    Debian devkit and /var/tmp
  


  

     user name

     2006-06-06 12:57:09
  


  

    
On Thu, Jun 01, 2006 at 12:40:00PM -0700, Diane Holt wrote:
>    Can someone explain this to me?

debian devkit sets 

TMPDIR=/var/tmp
TMP=/var/tmp

enviroinment variables. Without those variables set,
temporary files
are written to /tmp , which does exist. Using a target with
devkits
enabled but where "sb-conf in -d" (or the
equilavent in sb-menu)
has not been done is unsupported and will yield undefined
behaviour.
_______________________________________________
Scratchbox-users mailing list
Scratchbox-userslists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman
/listinfo/scratchbox-users


  


  

    
  

  
  
   
     
    






 [1-2]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )