From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] upas locking
Date: Thu, 18 Apr 2013 11:15:57 +0200 [thread overview]
Message-ID: <7C2F640A-2A94-4AA1-9CE9-4E4845F0860F@lsub.org> (raw)
Hi,
we found recently that we had a problem with /mail/tmp/L.mbox
used by upasfs to lock.
Looking into, we found that in upas/common/libsys.c the
function generating the lock file name returns always "L.mbox"
but not .../L.<mbox file name> as it seems it should.
Also, the function doing the actual lock hides the error string.
I copied our changed file to /n/sources/contrib/nemo/libsys.c
Didn't create a patch yet because I'm not sure it's the right
change for this problem.
next reply other threads:[~2013-04-18 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 9:15 Francisco J Ballesteros [this message]
2013-04-18 14:04 ` erik quanstrom
2013-04-18 14:24 ` Francisco J Ballesteros
2013-04-18 14:42 ` erik quanstrom
2013-04-18 14:51 ` Fco. J. Ballesteros
2013-04-18 15:33 ` Charles Forsyth
2013-04-18 15:43 ` lucio
2013-04-18 15:59 ` Francisco J Ballesteros
2013-04-18 16:12 ` erik quanstrom
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=7C2F640A-2A94-4AA1-9CE9-4E4845F0860F@lsub.org \
--to=nemo@lsub.org \
--cc=9fans@9fans.net \
/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.
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).