public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: pcaulfield@sourceware.org To: lvm2-cvs@sources.redhat.com Subject: LVM2 ./WHATS_NEW daemons/clvmd/clvmd.c Date: Wed, 06 Oct 2004 10:12:00 -0000 [thread overview] Message-ID: <20041006101234.30269.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: pcaulfield@sourceware.org 2004-10-06 10:12:34 Modified files: . : WHATS_NEW daemons/clvmd : clvmd.c Log message: Revert the fork back to where it was as it seems to confuse pthreads. Instead, the parent now waits for the daemon to signal that it has completed successfully (or not) so it can return status to the user. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.100&r2=1.101 http://sources.redhat.com/cgi-bin/cvsweb.cgi/LVM2/daemons/clvmd/clvmd.c.diff?cvsroot=lvm2&r1=1.4&r2=1.5
next reply other threads:[~2004-10-06 10:12 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-06 10:12 pcaulfield [this message] 2004-10-06 12:36 pcaulfield 2005-01-05 14:41 pcaulfield 2005-01-24 15:31 pcaulfield 2005-02-08 9:05 pcaulfield 2005-04-01 13:01 pcaulfield 2006-11-30 9:44 pcaulfield 2006-12-11 13:48 pcaulfield 2007-03-29 13:59 pcaulfield 2007-11-15 10:16 pcaulfield 2008-02-15 14:12 meyering 2008-03-17 9:37 ccaulfield 2008-03-28 12:58 ccaulfield 2008-05-09 9:59 ccaulfield 2008-06-13 7:44 ccaulfield 2008-11-21 13:48 ccaulfield 2009-03-24 11:49 ccaulfield 2009-08-13 10:39 ccaulfield 2009-09-01 9:48 ccaulfield 2009-10-12 8:33 ccaulfield 2010-02-02 8:54 ccaulfield 2010-04-06 15:29 ccaulfield 2010-12-01 10:46 zkabelac 2010-12-01 12:41 zkabelac 2010-12-13 10:49 prajnoha 2011-03-08 13:27 mbroz 2011-03-08 22:48 zkabelac 2011-03-30 12:36 zkabelac 2011-06-28 13:42 zkabelac 2011-08-11 12:57 mbroz 2011-09-16 14:40 mbroz 2011-10-11 9:26 zkabelac 2011-10-11 9:54 zkabelac 2012-02-27 9:58 zkabelac 2012-02-27 11:26 zkabelac 2012-02-28 9:53 zkabelac 2012-02-28 9:58 zkabelac 2012-02-28 11:06 zkabelac
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=20041006101234.30269.qmail@sourceware.org \ --to=pcaulfield@sourceware.org \ --cc=lvm2-cvs@sources.redhat.com \ /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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).