[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: temp queues
- To: Liam <allenwc@shaw.ca>
- Subject: Re: temp queues
- From: Chuck Yerkes <chuck+obsd@2002.snew.com>
- Date: Sat, 2 Nov 2002 19:48:57 -0800
- Cc: Nick Nauwelaerts <nick@wanadoo.be>, tech@openbsd.org
- Content-Disposition: inline
- References: <20021029232706.2183c8f5.nick@wanadoo.be> <r01050400-1021-C7F2314AEB9511D6A3F8000393920B20@[192.168.0.3]>
- User-Agent: Mutt/1.2.5i
Ensure that the fifo create actually worked and you are looking
at YOUR fifo, avoiding some race conditions (e.g., bad guy creates
a fifo right before you try to and his gets the information).
I dunno what a "pacs image server" is, so I dunno if you don't
want your own (owned by your user) area that just clears the
dir on startup.
Quoting Liam (allenwc@shaw.ca):
> >Nick Nauwelaerts on 29/10/2002 wrote the bit with this mark:
>
> >>On Tue, 29 Oct 2002 14:03:10 -0800 Liam <allenwc@shaw.ca> wrote:
> >>
> >> I want to create some temporary fifos.
> >>
> >> Under openBSD, where is the approved location for these?
> >> (/var/spool/myqueues ?) or ( /temp/myqueues ?)
> >
> >Most files in /tmp don't survive a reboot, so that will be a large
> >factor I guess. It all depends on the kind of application: * do the
> >files need to be kept open * do they need to be accessible by other
> >processes/users
>
> It's for a pacs image server . . . not that such info will help but . .
> .
>
> they are temp files only, one per connection, they would be ideally
> removed on reboot.
> They would be read/written only by the server or its children.
> Ideally, as each child finishes it should remove its fifo.
>
> >I'd feel inclined to just store them in a subdirectory of my homedir
> >if it's for a user process or use mkstemp() if they don't have to
> >survice a reboot.
>
> hmmmm, sounds like /tmp is it
>
> --
> Liam Allen allenwc@shaw.ca
> it may be that your sole purpose in life
> is to serve as a warning to others