Don’t worry this is the correct group, I am using QNX4.25 and tfork…
Here is my trouble :
In my main prog
I create and open (for writing) a special fifo file (in a ramdrive : /ram).
Then I create a thread (with tfork). As stated by the doc : file descriptors
are duplicated…
In this new thread I try to write to my file and … guess what : I get back
the errno 9 : EBADF (bad file descriptor…)
So what is going on???
Is there something rotten in QNX kingdom???
If any of you has any idea to overcome this problem, this would help me very
much!
Thanks,
–
Didier HARRANG
BCI S.A.
3, rue du Velay, CE1740
Petite Montagne Sud
91017 EVRY Cedex, FRANCE
Tel : 33 (0)1 69 11 30 00
Fax : 33 (0)1 60 86 30 64
QNX 4’s implementation of threads is buggy at best, i.e. errno is not thread safe.
But in your case I think the problem is that the ram disk does not support duping a file descriptor.
That’s just a guess however. Does it work if you open your file on the normal file system?
Previously, Didier Harrang wrote in qdn.public.qnx4:
Hi!
Don’t worry this is the correct group, I am using QNX4.25 and tfork…
Here is my trouble :
In my main prog
I create and open (for writing) a special fifo file (in a ramdrive : /ram).
Then I create a thread (with tfork). As stated by the doc : file descriptors
are duplicated…
In this new thread I try to write to my file and … guess what : I get back
the errno 9 : EBADF (bad file descriptor…)
So what is going on???
Is there something rotten in QNX kingdom???
If any of you has any idea to overcome this problem, this would help me very
much!
Thanks,
–
Didier HARRANG
BCI S.A.
3, rue du Velay, CE1740
Petite Montagne Sud
91017 EVRY Cedex, FRANCE
Tel : 33 (0)1 69 11 30 00
Fax : 33 (0)1 60 86 30 64
QNX 4’s implementation of threads is buggy at best, i.e. errno is not
thread safe.
But in your case I think the problem is that the ram disk does not support
duping a file descriptor.
That’s just a guess however. Does it work if you open your file on the
normal file system?
Previously, Didier Harrang wrote in qdn.public.qnx4:
Hi!
Don’t worry this is the correct group, I am using QNX4.25 and tfork…
Here is my trouble :
In my main prog
I create and open (for writing) a special fifo file (in a ramdrive :
/ram).
Then I create a thread (with tfork). As stated by the doc : file
descriptors
are duplicated…
In this new thread I try to write to my file and … guess what : I get
back
the errno 9 : EBADF (bad file descriptor…)
So what is going on???
Is there something rotten in QNX kingdom???
If any of you has any idea to overcome this problem, this would help me
very
much!
Thanks,
–
Didier HARRANG
BCI S.A.
3, rue du Velay, CE1740
Petite Montagne Sud
91017 EVRY Cedex, FRANCE
Tel : 33 (0)1 69 11 30 00
Fax : 33 (0)1 60 86 30 64
What do you recomment? Where can I download it from?
This is for QNX4.
Previously, Ian Zagorskih wrote in qdn.public.qnx4:
“Bill Caroselli” <> qtps@earthlink.net> > wrote in message
news:a7ao40$5vq$> 1@inn.qnx.com> …
vmail is now SIGSEGVing at 7:3130E8 every time I try to start it.
What can I do to fix this?
Mmmm… use another mail client which was actually designed just to work ?
What do you recomment? Where can I download it from?
Well, maybe that’s against rules & religion but personally i would recommend
M$ Outlook Express 5.50…
This is for QNX4.
Ah… then guess not so user friendly but workable method is
$telnet inn.qnx.com nntp
$>help
$>list
$> [and so on…]
If seriously, i couldn’t force qnx4’s vmail to work stable at all. It’s
trapped with SIGSEGV oftenly then i can stand Someone may prefer afair
tin for news but after revising mail/news software available at ftp.qnx.com/usr/free i desided to stay with OE. At least it’s easier to
reboot into win2k several times per day and check mail/news in sable and
user friendly environment then experimenting with available software.
ps: personal oppinion - looking at Voyager’s 2.02 SDK at /usr/lib/src/imap/*
i’m wonderying why vmail can be started at all. with such quality of code it
is essential that it dosn’t work. btw this code wasn’t done by qssl people
so no flame. but also as i understand vmail for qnx4 is really dead and
willn’t be developed/enhanced in the future so no way…
Well, maybe that’s against rules & religion but personally i would
recommend
M$ Outlook Express 5.50… >
This is for QNX4.
Ah… then guess not so user friendly but workable method is
$telnet inn.qnx.com nntp
$>help
$>list
$> [and so on…]
If seriously, i couldn’t force qnx4’s vmail to work stable at all. It’s
trapped with SIGSEGV oftenly then i can stand > > Someone may prefer afair
tin for news but after revising mail/news software available at ftp.qnx.com/usr/free i desided to stay with OE. At least it’s easier to
reboot into win2k several times per day and check mail/news in sable and
user friendly environment then experimenting with available software.
ps: personal oppinion - looking at Voyager’s 2.02 SDK at
/usr/lib/src/imap/*
i’m wonderying why vmail can be started at all. with such quality of code
it
is essential that it dosn’t work. btw this code wasn’t done by qssl people
so no flame. but also as i understand vmail for qnx4 is really dead and
willn’t be developed/enhanced in the future so no way…
Well, maybe that’s against rules & religion but personally i would
recommend
M$ Outlook Express 5.50… >
This is for QNX4.
Ah… then guess not so user friendly but workable method is
$telnet inn.qnx.com nntp
$>help
$>list
$> [and so on…]
If seriously, i couldn’t force qnx4’s vmail to work stable at all. It’s
trapped with SIGSEGV oftenly then i can stand > > Someone may prefer afair
tin for news but after revising mail/news software available at ftp.qnx.com/usr/free i desided to stay with OE. At least it’s easier to
reboot into win2k several times per day and check mail/news in sable and
user friendly environment then experimenting with available software.
ps: personal oppinion - looking at Voyager’s 2.02 SDK at
/usr/lib/src/imap/*
i’m wonderying why vmail can be started at all. with such quality of code
it
is essential that it dosn’t work. btw this code wasn’t done by qssl people
so no flame. but also as i understand vmail for qnx4 is really dead and
willn’t be developed/enhanced in the future so no way…
Someone may prefer afair