similar to: Reading from named pipes

Displaying 20 results from an estimated 10000 matches similar to: "Reading from named pipes"

1998 Apr 07
2
SAMBA digest 1647
Very very very cool. I have been thinking of this one myself. I thought I tested it and that I came to the conclusion that Samba did not recognize named pipes, and just treated them like normal files (overwriting them when you drag a text file onto them). But I must have made a mistake somewhere. It' perfect. The way I will set it up is like this: a Progress program will sit on a named
1998 Apr 06
3
Triggering processes through Samba
Hi, I need to upload data from a barcode scanner into a Progress database on UNIX. The barcode reader is attached to a PC. We have set it up in this way that the barcode reader creates a file in a directory shared by the PC and an HP box. A simple daemon on the HP scans the directory and triggers a program to upload the data whenever it finds a file in that directory. I was wondering if
2003 Nov 30
0
FreeBSD mknod refuses to create pipes and fifos
>Submitter-Id: current-users >Originator: Joao Carlos Mendes Luis >Organization: >Confidential: no >Synopsis: FreeBSD mknod refuses to create pipes and fifos >Severity: non-critical >Priority: low >Category: kern >Class: change-request >Release: FreeBSD 4.9-RC i386 >Environment: System: FreeBSD zeus.faperj.br 4.9-RC FreeBSD 4.9-RC #3: Sat Oct 25 17:54:52 BRST
2002 Mar 01
1
PATCH - smbd/trans2.c to support writing to Unix named pipes(FIFO)
Hi, We have a simple "Remote Procedure Call" mechanism that we are using to communicate between Windows computers and our Unix Samba server. The Windows application is proprietary software (Progress - not ours) and we have to work within the constraints of it. We have a Unix named pipe sitting in a Samba shared directory. We have a small C program that runs as a Unix daemon,
2017 Jan 11
0
[tftp-hpa] [PATCH] support for named pipes
Attached is a patch for the latest tftp-hpa. This patch add support for named pipes. Named pipes are 0 byte files which can be read by a PXE boot process. They provide the necessary informations for the boot process and are deleted afterwards. This PXE boot is a single event and won't interact until another named pipe is created for the client. -- Mathias Radtke ---
2009 Apr 20
6
DO NOT REPLY [Bug 6280] New: (Bug incl. PATCH) Linux mknod does not work when syncing fifos and sockets from Solaris
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:
2017 Jan 12
0
[tftp-hpa] [PATCH] support for named pipes
> Attached is a patch for the latest tftp-hpa. > This patch add support for named pipes. > > Named pipes are 0 byte files which can be read by a PXE boot process. > They provide the necessary informations for the boot process and are > deleted afterwards. > This PXE boot is a single event and won't interact until another named > pipe is created for the client.
2001 Feb 27
2
Network Named Pipes supported under Wine ?
I have a small server process which normall runs on Windows and accepts network connections via Named Pipes. I would like to run this process under Wine to avoid having to install an NT server I get .. fixme:win32:CreateNamedPipeA (Name="\\\\.\\PIPE\\SOESRV33", OpenMode=0x000003, dwPipeMode=0x000004, MaxInst=5, OutBSize=10096, InBuffSize=10096, DefTimeOut=0, SecAttr=0x412f6f00):
2003 Dec 18
1
FreeBSD mknod errors
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
2017 Dec 20
1
MS-RPC, LSARPC and Named Pipes end points
Hi everyone, I get more and more questions from security minded clients about MS-RPC and the dynamic RPC port range. The default range is quite wide, and while it can be configured and reduced through the "rpc server dynamic port range" parameter since 4.7.0, it still get network/firewall/security people nervous. Digging further into that subject, after some more reading and
2002 May 30
1
Samba 2.2.1a and named pipes
Can Samba write to named pipes ? I am using Netsaint/Nagios for system monitoring and the command file to write system commands to is implemented as a named pipe. I can write normal files to the directory but whenever I try and write to the pipe I get access denied. Thanks. ---------------------------- Jeff White Senior Systems Engineer Xelus, Inc. Phone: 716-419-3105 Fax: 716-248-9199
2011 Oct 15
5
fuck yeah markdown
brett terpstra continues his obsession with markdown... > http://fuckyeahmarkdown.com/ there's also a g-rated version: > http://heckyesmarkdown.com/ brett has accomplished more in the last three months than this listserve accomplished in the last three years. and it looks like he's only just getting started... meanwhile, fletcher is about to send off his rocket, which
2006 Oct 31
0
6407402 Named pipes should work between labeled zones to support write up.
Author: gfaden Repository: /hg/zfs-crypto/gate Revision: 84f19e06f2d07a2e47e5d67eeab39debcef1c738 Log message: 6407402 Named pipes should work between labeled zones to support write up. 6411980 getlabel(2) returns wrong label for lofs mounted FIFOs Files: update: usr/src/uts/common/fs/fifofs/fifosubr.c update: usr/src/uts/common/fs/fifofs/fifovnops.c update: usr/src/uts/common/os/tlabel.c
2002 Sep 03
1
hangin when listing named pipes
Hi Even when you are not opening the pipe, but just listing it in cygwin, or trying to see the properties in explorer, you will have this problem: Does anybody know how to disable named pipes in samba? Or how you can kill the connection from the client side? And no, setting "nt pipe support" to no, doesn't fix the problem. /Kaj Symptom: Samba daemon hanging when trying to open
2014 Jan 30
1
Re: Notes on building libguestfs in a systemd-nspawn container
On Thu, Jan 30, 2014 at 05:07:23PM +0530, Kashyap Chamarthy wrote: > On 01/30/2014 04:38 PM, Daniel P. Berrange wrote: > > [. . .] > > >> > >> Despite reading from the `systemd-nspawn` man page: > >> > >> ". . .kernel modules may not be loaded from within the container." > >> > >> I purposefully tried from inside the
2002 Jan 25
3
suid files and bsd
Currently I only have one machine backing up to another. I am backing up to a filesystem that is mounted as nosuid. The syncing process works perfectly except it fails on files that are suid. Example proc/ root/ tmp/ mknod tmp/mysql.sock : Invalid argument mknod tmp/orbit-daud/orb-12573780511489051058 : Invalid argument mknod tmp/orbit-daud/orb-139425434385535813 : Invalid argument mknod
2014 Jan 30
0
Re: Notes on building libguestfs in a systemd-nspawn container
On 01/30/2014 04:38 PM, Daniel P. Berrange wrote: [. . .] >> >> Despite reading from the `systemd-nspawn` man page: >> >> ". . .kernel modules may not be loaded from within the container." >> >> I purposefully tried from inside the container: > > With container based virt there is only one kernel image, Noted, that's one of the main
2005 Feb 09
1
rsync backups on Mac OS X - mknod errors + icon disappears...
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
2003 Nov 07
0
rsync 2.5.6 fails to create device nodes on IRIX and NFS mount
Hi, rsync (2.5.6 protocol version 26) on IRIX fails to create device inodes to a NFS mounted filesystem. rsync via ssh, client side is on IRIX 6.5.19, server side is on RedHat Linux 7.3 (rsync 2.5.4 protocol version 26) and the NFS mount is from a linux box (NFSv3 and dev,suid as mount options, no_root_squash,rw as export option). [root@octane /]# /usr/freeware/bin/rsync -aHzvxe "ssh
2008 May 22
2
"Invalid argument" error when moving sockets to backup dir
Local end (receiving): 3.0.2, 3.0.3pre2 Remote end (sending): 2.6.9 Under 3.0.x, rsync sometimes prints an "Invalid argument" error when moving sockets to the backup directory (--backup-dir): rsync: mknod "/backup/machine/../machine-before-4/var/run/audit_events" failed: Invalid argument (22) The problem appears to be that, at least with sockets, keep_backup() is calling