public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: John Elliott <jce@seasip.demon.co.uk>
To: Marek Kriz <marek.kriz@tco.cz>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Access denied after write to named pipe
Date: Tue, 18 Mar 2003 20:31:43 +0000 (GMT)	[thread overview]
Message-ID: <E18vNkN-0000Vu-00@seasip.demon.co.uk> (raw)
In-Reply-To: <no.id> from "Marek Kriz" at Mar 17, 2003 08:51:12

: 
: When I try create named pipe (to some directory which is 'visible' from 
: dosemu) in RDONLY mode, so after command
: ECHO HELLO > NAMED.PIP
: I got error message Access denied. Where is the problem? Permissions of 
: pipe are 0777, umask is 000, run under user ROOT.

  I suspect that echo may be trying to open the pipe in Read+Write mode;
I get the same effect with dosemu-1.0.1.0 and DRDOS 6. But if I write a 
C program to write to the pipe:

#include <unixio.h>
#include <string.h>

#define O_WRONLY 1

int main(int argc, char **argv)
{
	int n;
	int fd = open(argv[1], O_WRONLY);

	for (n = 2; n < argc; n++) 
	{
		write(fd, argv[n], strlen(argv[n]));
		write(fd, " ", 1);
	}
	close(fd);
	return 0;
}

 - then it works.  

------------- http://www.seasip.demon.co.uk/index.html --------------------
John Elliott           |BLOODNOK: "But why have you got such a long face?"
                       |SEAGOON: "Heavy dentures, Sir!"    - The Goon Show 
:-------------------------------------------------------------------------)

  parent reply	other threads:[~2003-03-18 20:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <no.id>
2002-10-18 19:53 ` DPMI: Interrupt vector overwritten John Elliott
2002-12-16 19:19 ` increase base memory John Elliott
2002-12-16 20:01   ` Bart Oldeman
2003-03-18 20:31 ` John Elliott [this message]
2003-03-17  7:51 Access denied after write to named pipe Marek Kriz

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=E18vNkN-0000Vu-00@seasip.demon.co.uk \
    --to=jce@seasip.demon.co.uk \
    --cc=linux-msdos@vger.kernel.org \
    --cc=marek.kriz@tco.cz \
    /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