in reply to open vs. sysopen

no idea, i humbly suggest to try open with O_RDWR flag set instead of O_WRONLY. I also suggest you to write down you OS, and the kind of fs you ar using (mounted?).

more: do POSIX::open() works?

this may give more information to fix it.

Replies are listed 'Best First'.
O_RDWR, POSIX, OS, fs...
by sheep (Chaplain) on Dec 26, 2003 at 18:25 UTC
    Changing to O_RDWR doesn't help.
    OS: Slackware 9.1 Linux 2.4.23
    fs: /dev/hdd3 / ext2 rw 0 0
    POSIX::open() works fine
    Thanks!
    -sheep

      Perhaps you can supply some additional code, or a small test case that exhibits the behavior. The following two lines of code behave properly on my Slackware Linux box (2.4.18), assuming proper permissions on directories involved in the filepath.

      open(DEST,'>',$ggg) or die $!; sysopen(DEST, $ggg, O_WRONLY | O_TRUNC | O_CREAT) or die $!;