From: DervishD <zsh@dervishd.net>
To: Lloyd Zusman <ljz@asfast.com>
Cc: zsh-users@sunsite.dk
Subject: Re: File locking within zsh?
Date: Wed, 10 May 2006 23:21:55 +0200 [thread overview]
Message-ID: <20060510212155.GB5555@DervishD> (raw)
In-Reply-To: <87y7xai4ev.fsf@asfast.com>
Hola Lloyd :)))
* Lloyd Zusman <ljz@asfast.com> dixit:
> >> I know that I can do this with a number of compiled executables,
> >> but I'm looking for a zsh-only solution.
> >
> > Apart from the 'ln' trick, you can do this in Perl if you don't
> > want compiled executables.
>
> Well, the perl interpreter is a compiled executable, and a rather
> heavy one, at that. I'm trying to avoid spawning any extra
> processes.
OK. I thought that your problem was that you didn't want to write
it in C, for example. If you're trying to avoid heavy binaries, avoid
Perl ;))
> > If you could ellaborate on the problem you're trying to solve, I
> > can try to give a better solution.
>
> I'm writing a zsh shell function that might be invoked within concurrent
> terminal sessions. There's a critical section of code within this shell
> function that I want to protect with an exclusive lock. I only need to
> protect this critical section from other invocations of this same shell
> function.
OK, then probably the 'ln' solution will do.
> Perhaps I can write a loadable zsh module which can supply this
> capability.
Probably, but that's a lot of work for something you can achieve
using 'ln'. You can even write a couple of shell functions using 'ln'
to do the locking.
The only problem I see with the 'ln' solution is that it doesn't
block, you're forced to use a busy-wait loop :((
If you don't want to use a busy-wait loop, you can try to use a
FIFO (in the filesystem, I mean) or a socket. Synchronizing more than
two tasks using those mechanism is tricky, but I think it can be
done. Think of your problem not as a "locking problem" but just as an
"IPC problem". A bit complex, anyway, because the shell doesn't
provide atomic operations that block (AFAIK).
Of course, a zsh module for doing locking would be great ;) (or
adding the needed functions to zsh/files, for example).
> > Good luck :)
>
> Muchas gracias. :)
De nada :))) I'm happy of reading you again :)
BTW, this issue has been partially addressed in zsh-users 8632
and 8633.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to... RAmen!
prev parent reply other threads:[~2006-05-10 21:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 22:04 Lloyd Zusman
2006-05-10 3:31 ` Tim Writer
2006-05-10 5:59 ` Brian K. White
2006-05-10 10:02 ` Lloyd Zusman
2006-05-10 22:04 ` Tim Writer
2006-05-11 3:41 ` Bart Schaefer
2006-05-11 14:25 ` Tim Writer
2006-05-11 15:01 ` Peter Stephenson
2006-05-12 4:22 ` Tim Writer
2006-05-12 9:17 ` Subshells and parameters (was: File locking within zsh?) Vincent Lefevre
2006-05-12 12:09 ` Subshells and parameters Lloyd Zusman
2006-05-12 23:09 ` Vincent Lefevre
2006-05-13 2:05 ` Lloyd Zusman
2006-05-17 14:24 ` Vincent Lefevre
2006-05-17 15:42 ` Bart Schaefer
2006-05-17 16:07 ` Vincent Lefevre
2006-05-13 2:10 ` Dan Nelson
2006-05-11 16:13 ` File locking within zsh? Brian K. White
2006-05-10 17:13 ` Vincent Lefevre
2006-05-11 15:45 ` Brian K. White
2006-05-12 7:54 ` Vincent Lefevre
2006-05-12 19:40 ` Tim Writer
2006-05-12 23:24 ` Vincent Lefevre
2006-05-10 21:53 ` Tim Writer
2006-05-10 6:29 ` DervishD
2006-05-10 10:02 ` Lloyd Zusman
2006-05-10 21:21 ` DervishD [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060510212155.GB5555@DervishD \
--to=zsh@dervishd.net \
--cc=ljz@asfast.com \
--cc=zsh-users@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).