On Sun, Jun 15, 2008 at 4:58 PM, Enrico Weigelt <[EMAIL PROTECTED]> wrote:
> * Pietro Gagliardi <[EMAIL PROTECTED]> wrote:
>> Doesn't matter. Process groups are process groups on any Unix clone.
>> If it's daemons you're dealing with, then it leaves the scope of this
>> room. If it's Windows, you'r
> Doesn't matter. Process groups are process groups on any Unix clone.
> If it's daemons you're dealing with, then it leaves the scope of this
> room. If it's Windows, you're out of luck.
Not true, Windows has the concept of process groups.
See the description of CREATE_NEW_PROCESS_GROUP at
h
Hi,
Inferno's vacfs lets you cd into a score and read files from there
without a mount per-score.
--vs
* Russ Cox <[EMAIL PROTECTED]> wrote:
Hi,
> I wasn't kidding. Update your plan9port
> and you will find an unvac command.
my last checkout is a about 5 days old, and I couldn't find
some working unvac command. But I'll have a re-checkout.
> You'll get more leverage if you stick to vac files.
* Pietro Gagliardi <[EMAIL PROTECTED]> wrote:
> Doesn't matter. Process groups are process groups on any Unix clone.
> If it's daemons you're dealing with, then it leaves the scope of this
> room. If it's Windows, you're out of luck.
I'm running p9p on Linux. No idea where the actual problem s
Doesn't matter. Process groups are process groups on any Unix clone.
If it's daemons you're dealing with, then it leaves the scope of this
room. If it's Windows, you're out of luck.
On Jun 15, 2008, at 1:13 PM, Enrico Weigelt wrote:
* Pietro Gagliardi <[EMAIL PROTECTED]> wrote:
On Jun 15,
> hmm, maybe ;-o
>
> Meanwhile I've written an new tool which stores single files
> (no directory stuff at all). Not perfect yet, but already
> works quite fine (IMHO):
>
> svn://nibiru.metux.de/public/plan9port/apps/vtstore/
>
> In the next step, I'll add http-alike metadata (mimetype, etc).
>> Aha. But this still does not terminate the vacfs, right ?
>
>
> Once you kill the script, you also kill the processes it created -
> that's what process groups are, remember?
incorrect. the script exits, it is not killed. for example
; cat script
#!/bin/rc
rfork n
* Pietro Gagliardi <[EMAIL PROTECTED]> wrote:
> On Jun 15, 2008, at 12:02 PM, Enrico Weigelt wrote:
>
> >Aha. But this still does not terminate the vacfs, right ?
>
>
> Once you kill the script, you also kill the processes it created -
> that's what process groups are, remember?
That doesnt s
On Jun 15, 2008, at 12:02 PM, Enrico Weigelt wrote:
Aha. But this still does not terminate the vacfs, right ?
Once you kill the script, you also kill the processes it created -
that's what process groups are, remember?
Please read "The Use of Name Spaces in Plan 9" and the rfork man page
* Russ Cox <[EMAIL PROTECTED]> wrote:
> rfork n forks the name space, so that any changes
> made by the script don't propagate out to the
> parent process. This means that (1) vacfs can
> mount on /n/vac without any fear of bothering
> some other instance of the script, and (2) when the
> scrip
>> no, it doesn't. on plan 9, when the shell script exits,
>> nothing will have vacfs mounted anymore, so vacfs
>> will get an eof on the 9p connection and exit.
>> that's why i put an rfork n in the script.
>
> aha, that's probably what the rfork call does ?
rfork n forks the name space, so tha
* Russ Cox <[EMAIL PROTECTED]> wrote:
Hi,
> no, it doesn't. on plan 9, when the shell script exits,
> nothing will have vacfs mounted anymore, so vacfs
> will get an eof on the 9p connection and exit.
> that's why i put an rfork n in the script.
aha, that's probably what the rfork call does ?
> BTW: still leaves the problem that lot's of vacfs servers are
> started not terminated after use :(
no, it doesn't. on plan 9, when the shell script exits,
nothing will have vacfs mounted anymore, so vacfs
will get an eof on the 9p connection and exit.
that's why i put an rfork n in the script
* Russ Cox <[EMAIL PROTECTED]> wrote:
> > The venti/read and venti/write commands just support single blocks.
> > Vac seems fine as archive tool, but it only can store - I need some
> > "unvac" command. (mounting each single archive via vacfs is a bit
> > too complicated for my project).
>
> I'm h
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Since you mention using vac for storage, I assume you're using venti
> directly, not via fossil, in which case the '9fs dump' suggestion will
> do nothing for you.
ACK.
> I don't believe there is anything in Plan 9 that does what you want
> (certai
> The venti/read and venti/write commands just support single blocks.
> Vac seems fine as archive tool, but it only can store - I need some
> "unvac" command. (mounting each single archive via vacfs is a bit
> too complicated for my project).
I'm hesitant to bother replying, as we learned earlier
I don't think so. 9fs dump gives you everything afaik.
On Jun 13, 2008, at 4:29 PM, Enrico Weigelt wrote:
* Pietro Gagliardi <[EMAIL PROTECTED]> wrote:
9fs dump
command /n/dump//mmdd/absolutepathtofile
but this still requires me to mount each single vac
archive before reading, and I need
* Pietro Gagliardi <[EMAIL PROTECTED]> wrote:
> 9fs dump
> command /n/dump//mmdd/absolutepathtofile
but this still requires me to mount each single vac
archive before reading, and I need to create a new one
for each upload, right ?
cu
--
---
Since you mention using vac for storage, I assume you're using venti
directly, not via fossil, in which case the '9fs dump' suggestion will
do nothing for you.
I don't believe there is anything in Plan 9 that does what you want
(certainly the BUGS section in venti(1) implies not), but you might
lo
9fs dump
command /n/dump//mmdd/absolutepathtofile
-> year
mmdd -> month and date
On Jun 13, 2008, at 3:50 PM, Enrico Weigelt wrote:
Hi folks,
is there any command line tool for reading and writing files
on venti ?
The venti/read and venti/write commands just support single blocks.
Hi folks,
is there any command line tool for reading and writing files
on venti ?
The venti/read and venti/write commands just support single blocks.
Vac seems fine as archive tool, but it only can store - I need some
"unvac" command. (mounting each single archive via vacfs is a bit
too complic
22 matches
Mail list logo
