zsh-users
 help / color / mirror / code / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
To: zsh-users@sunsite.dk
Subject: Re: File locking within zsh?
Date: Wed, 10 May 2006 06:02:16 -0400	[thread overview]
Message-ID: <87y7xai4ev.fsf@asfast.com> (raw)
In-Reply-To: <20060510062930.GB4340@DervishD>

DervishD <zsh@dervishd.net> writes:

>     Hi Lloyd :)

¡Hola Raúl!


>  * 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.


> [ ... ]
>
>     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.

I know that there are various file locking executables, and I can also
write my own.  Plus, I know that I can get this functionality via
scripts in perl, ruby, python, etc.  I've just been wondering if there's
a way to do this solely within zsh, without any ancillary executables
being spawned.

Perhaps I can write a loadable zsh module which can supply this
capability.


>     Good luck :)

Muchas gracias. :)


-- 
 Lloyd Zusman
 ljz@asfast.com
 God bless you.


  reply	other threads:[~2006-05-10 10:05 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 [this message]
2006-05-10 21:21     ` DervishD

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=87y7xai4ev.fsf@asfast.com \
    --to=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).