From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [Linux-cluster] Fw: Building error in Cluster 2.03.09
Date: Fri, 31 Oct 2008 14:31:54 -0400 [thread overview]
Message-ID: <1225477914.3194.159.camel@ayanami> (raw)
In-Reply-To: <0d9d01c93b49$a5a81fc0$a401a8c0@mainoffice.nodex.ru>
On Fri, 2008-10-31 at 14:13 +0300, Pavel Kuzin wrote:
> node2:~/newcluster/cluster-2.03.09# uname -a
> Linux node2 2.6.27.4 #2 SMP Fri Oct 31 13:42:09 MSK 2008 i686 GNU/Linux
>
> Distro - Debian Etch
>
Maybe...
> Seems mkostemp is available since glibc 2.7.
> I have 2.6.
> Can "mkostemp" be changed to another similar function?
#define mkostemp(val, flags) mkstemp(val)
?
Man page:
int mkstemp(char *template);
int mkostemp (char *template, int flags);
...
mkostemp() is like mkstemp(), with the difference that flags as for
open(2) may be specified in flags (e.g., O_APPEND, O_SYNC).
Not sure the implications of doing this; I didn't analyze the open flags
used.
-- Lon
next parent reply other threads:[~2008-10-31 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0d9d01c93b49$a5a81fc0$a401a8c0@mainoffice.nodex.ru>
2008-10-31 18:31 ` Lon Hohberger [this message]
2008-11-02 8:49 ` [Cluster-devel] Re: [Linux-cluster] Fw: Building error in Cluster 2.03.09 Fabio M. Di Nitto
2008-11-03 4:55 ` Fabio M. Di Nitto
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=1225477914.3194.159.camel@ayanami \
--to=lhh@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: 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).