similar to: FreeBSD mknod refuses to create pipes and fifos

-----BEGIN PGP SIGNED MESSAGE----- ============================================================================= FreeBSD-SA-99:01 Security Advisory FreeBSD, Inc. Topic: BSD File Flags and Programming Techniques Category: core Module: kernel Announced: 1999-09-04

Hello folks, I have a panic at shutdown related to FUSE. #0 doadump (textdump=<value optimized out>) at pcpu.h:234 234 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt full #0 doadump (textdump=<value optimized out>) at pcpu.h:234 No locals. #1 0xffffffff8090d9a6 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:449 _ep = (struct

In zfs_mount() function, when we process a mount by a regular user through the delegated administration, the comment states: /* * Make sure user is the owner of the mount point * or has sufficient privileges. */ This makes sense, but the code doesn''t match the comment. The code ensures that user is the owner of the mount point _and_ can write to the directory. Or does "has

Since mkfifo, mknod_b, and mknod_c add the correct file type to the modes of the resulting file, make sure the specified mode contains only permissions bits. --- daemon/mknod.c | 15 +++++++++++++++ generator/actions.ml | 21 ++++++++++++++++++--- 2 files changed, 33 insertions(+), 3 deletions(-) diff --git a/daemon/mknod.c b/daemon/mknod.c index 7f71210..9af8701 100644 ---

https://bugzilla.samba.org/show_bug.cgi?id=6280 Summary: (Bug incl. PATCH) Linux mknod does not work when syncing fifos and sockets from Solaris Product: rsync Version: 3.0.6 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=1804 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX ------- Additional Comments From wayned@samba.org 2004-09-22 09:56

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- This syncs it up with what's in envytools. Some of the names are a bit different, but I'm inclined to trust envytools as the correct thing. drivers/gpu/drm/nouveau/core/engine/graph/nv50.c | 29 ++++++++++++------------ 1 file changed, 15 insertions(+), 14 deletions(-) diff --git

I have been running rsync for about 2 weeks now and I will occasionally recieve the following errors: mknod ./{filename} : Invalid argument mknod ./{filename} : Invalid argument mknod ./{filename} : Invalid argument mknod ./{filename} : Invalid argument mknod ./{filename} : Invalid argument wrote 16 bytes read 336751 bytes 131.52 bytes/sec total size is 33812275937 speedup is 100402.58 rsync

Show usage instead of segfaulting when no args are passed. 0d844078 added typec and assigned value without actually using it. As variable is properly named just use it in coressponding switch. Signed-off-by: maximilian attems <max at stro.at> --- usr/utils/mknod.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/usr/utils/mknod.c b/usr/utils/mknod.c index

I want * to answer the phone when call comes-in. I've enabled /dev/phone0 in phone.conf and created /dev/phone0 with a command: mknod /dev/phone0 c 100 0 Though, when I start * I get: Parsing '/etc/asterisk/phone.conf': Found Sep 12 00:18:42 WARNING[16384]: chan_phone.c:950 mkif: Unable to open '/dev/phone0' Sep 12 00:18:42 ERROR[16384]: chan_phone.c:1141 load_module: Unable

Greetings! I'm experiencing these problems as described in this mail: ------- From: Thomas Quinot (thomas@melusine.cuivre.fr.eu.org) Subject: Rsync 2.5.5: FreeBSD mknod can't create FIFO's This is the only article in this thread View: Original Format Newsgroups: mailing.unix.rsync Date: 2002-06-24 06:05:25 PST The following patch

Hi all, I ran across a few threads on google regarding FreeBSD's rsync mknod problem but I didn't find any good fix. I was wondering if anyone knows more about this and a good fix. Here's an example of the output. mknod qmail/queue/lock/trigger : Invalid argument mknod qmail/supervise/qmail-send/log/supervise/control : Invalid argument mknod

Hi all, Currently, umask takes effect when we create device file via mknod, as bellow commands show: ><fs> mknod-b 0760 8 1 /dev/sdf ><fs> ll /dev/sdf brwxr----- 1 root root 8, 1 Apr 15 11:10 /sysroot/dev/sdf But I wonder whether it is reasonable? For mknod(1), when we use option -m mode, we set file permission bits to MODE, not a=rw - umask. Should this also be applicable

The following patch (adapted to rsync 2.5.5 from the one posted in Dec. 2000, http://lists.samba.org/pipermail/rsync/2000-December/003349.html) is necessary to prevent rsync from failing on creating FIFOs or UNIX sockets on FreeBSD. Any chance for it to be integrated in a future release of rsync? Thomas. diff -ur work/rsync-2.5.5/config.h.in work.patch/rsync-2.5.5/config.h.in ---

Hi I am a rsync (on Mac OS X, RsyncX version with extended HFS+/-eahfs forks) beginner (I merely use it for backing up my desktop machine to a bootable external firewire volume, so that I can resume work in case of a harddrive disaster) and I got these messages: mknod "/Volumes/backup/Applications/Plone2/Sites/Default/var/zopectlsock" failed: Invalid argument mknod

Hello I have a large list of URLs (from a database, generated automatically during tests) that I want to download using several wget processes at the same time. With our internal web servers, this will be a lot faster than downloading the pages one at a time with a single process. So I create 20 pipes in my script with `mkfifo? and connect the read end of each one to a new wget process for

When trying to move my root to a btrfs filesystem, I found a missing feature (or a bug). It's not possible to create device files. To reproduce, run this on a btrfs filesystem: mknod test c 1 1 result: mknod: `test': Operation not permitted Frank

Here's a patch against 4.8-RELEASE kernel that allows disk writes on softupdates-enabled filesystems to be delayed for (theoretically) arbitrarily long periods of time. The motivation for such updating policy is surprisingly not purely suicidal - it can allow disks on laptops to spin down immediately after I/O operations and stay idle for longer periods of time, thus saving considerable amount

Signed-off-by: Paulo Alcantara <pcacjr at zytor.com> --- com32/cmenu/menugen.py | 56 +++++++++++++++++++++++++------------------------- 1 file changed, 28 insertions(+), 28 deletions(-) diff --git a/com32/cmenu/menugen.py b/com32/cmenu/menugen.py index 70ec1f8..da64d93 100644 --- a/com32/cmenu/menugen.py +++ b/com32/cmenu/menugen.py @@ -72,9 +72,9 @@ class Menusystem:

Hi, I am getting the following errors on /boot partition on a production server running 2.4.18 kernel. ------------- Aug 10 00:19:37 kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 ------------- /boot is not readable at all and attempt to do an ls will return the same error.