similar to: rsyncing fifos and sockets on FreeBSD

Displaying 20 results from an estimated 2000 matches similar to: "rsyncing fifos and sockets on FreeBSD"

2000 Feb 02
2
problems with openssh-1.2.2 and pam_tacplus.so
Hello, I have the following problem: I have installed openssh-1.2.2 on FreeBSD 3.4-RELEASE. I intentionally did not took the FreeBSD port because it does not support PAM. My aim is to make sshd authenticate against a TACACS+ server using the pam_tacplus.so module shipped with FreeBSD. That works perfectly with this line in my /etc/pam.conf: login auth sufficient pam_tacplus.so
2003 Oct 27
0
rsyncing fifos and sockets on FreeBSD
Hi there, I already asked the list about the problems with sockets on FreeBSD (see here: http://www.mail-archive.com/rsync@lists.samba.org/msg08121.html). I adopted Andrew Flury's patch to the recent CVS version of rsync: Index: rsync.h =================================================================== RCS file: /cvsroot/rsync/rsync.h,v retrieving revision 1.155 diff -r1.155 rsync.h
2000 Feb 02
2
bash: scp: command not found
On Wed, 2 Feb 2000, Harald at iki.fi wrote: > How come I can't get scp to work properly. It just complains like this: > > scp foo host: > bash: scp: command not found > lost connection Maybe you should check for the path on the remote machine: it seems like the remote shell can't find scp in its $PATH. -- Dominik - http://www.saargate.de/~domi/
2002 Mar 14
0
rsync 2.5.2 doens't compile on Tru64 5.1 and FIFO, socket files
Hi all, I have rsync 2.5.1 (with a patch from albert chin - china@thewrittenword.com) installed OK on Tru64 5.1 UNIX. When I run rsync, it doesn't work with special files (FIFO, socket,...) Here is the error: mknod cluster/members/member1/dev/binlogdmb : Invalid argument mknod cluster/members/member1/dev/log : Invalid argument mknod cluster/members/member1/dev/printer : Invalid
2002 Mar 07
0
rsync 2.5.2 doens't compile on Tru64 5.1
Hi all, I have rsync 2.5.1 (with a patch from albert chin - china@thewrittenword.com) installed OK on Tru64 5.1 UNIX. When I run rsync, it doesn't work with special files (FIFO, socket,...) Here is the error: mknod cluster/members/member1/dev/binlogdmb : Invalid argument mknod cluster/members/member1/dev/log : Invalid argument mknod cluster/members/member1/dev/printer : Invalid
2003 Aug 23
1
mknod / rsync error
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
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:
2004 Sep 22
6
[Bug 1804] FreeBSD's mknod can't create FIFOs and sockets
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
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 Jun 24
0
Rsync 2.5.5: FreeBSD mknod can't create FIFO's
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 ---
2000 Mar 07
0
ANNOUNCE: openssh-1.2.2p1
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a patch release which contains fixes to all the problems which have been reported over the last month. Most importantly: OpenSSL-0.9.5 has exposed a bug in RSA key generation on systems which lack a /dev/random (Solaris, HPUX, SCO). On such systems this port was not properly initialising OpenSSL's entropy pool. This results in lower
2000 Apr 11
2
X forwarding (still) broken on Linux
On Sun, 9 Apr 2000, barker at ling.ucsd.edu wrote: > This may be a lack-of-adequate-documentation problem rather than a bug, > but I can't get X forwarding to work: > > localhost$ set | grep DIS > DISPLAY=localhost.localdomain:11.0 > localhost$ set | grep XA > XAUTHORITY=/tmp/ssh-gzg13204/cookies > localhost$ ssh -v localhost > SSH Version
2005 Jul 24
2
[Bug 2868] Allow fifos to be copied by normal users
https://bugzilla.samba.org/show_bug.cgi?id=2868 ------- Additional Comments From rsync@cpe-24-95-91-210.columbus.res.rr.com 2005-07-23 23:36 ------- this should apply to both fifos and sockets. creation of both are unprivileged operations, see mkfifo(2), socket(2)/bind(2) on freebsd. suggest moving/modifying do_mknod in these sections backup.c generator.c to run regardles of uid and simply
2007 Nov 26
1
CPCA?
It would be great to know if and where an R code for Common Principal Component Analysis is available. Thanks, Daniel Daniel Berner Redpath Museum & Dept. of Biology McGill University 859 Sherbrooke St. W. Montreal, QC, H3A 2K6 Canada Phone: 514-398-4086 ext. 00908 Fax: 514-398-3185 Email: daniel.berner at mail.mcgill.ca
2004 May 26
3
Common principle components
Dear all, Can anyone point me to a package that can perform Common principle components? Thank you. Jos?? P. Granadeiro
2001 Nov 02
7
Entropy and DSA keys
I remember a discussion to the effect that using DSA keys in sshd increases the requirement for random bits available on the system... and that this requirement (was it a 128 bit random number per connection?) presents security problems on systems that don't have a decent source of entropy? Am I misinterpreting those discussions? We are having a problem deploying sshd (no prngd) where sshd
2009 Nov 27
6
Learning R - View datasets
Hi All, I am making a serious effort to try to learn R, but one hurdle I am facing is that I need to "see" the data as I walk through the examples in the packages. For instance, many examples on the web start by a command like data("wines"). How can I actually view what the dataset looks like prior to transformations and analysis? I have tried to use edit() , print, and
2007 Sep 30
1
[Patch] reenable fifos if we get an error while fifos disabled
Hello, while playing around with multiple fifo contexts I got fifo hangs when opening glxgears nr.3. The reason is that in drm/linux_core/nouveau_fifo.c l.342 engine->graph.create_context() returns -ENOMEM (I dont know why but I think this problems also appears with other errors). But the real problem is that then nouveau_fifo alloc() returns without reenabling fifo execution, so all fifos
2002 Aug 05
1
samba pdc- dialin allowed flag?
I would like to use a genuine Windows 2000 server as my PPTP server (getting poptop to work correctly is annoying the hell out of me) which needs to authenticate off of a Samba server configured as a PDC. A Windows-based PDC has a flag for "dialin access allowed" for each user. I searched the Samba archives and see several posts over the years that say it "sounds easy enough to
2000 Mar 27
2
FreeBSD 3.1 & OpenSSH 1.2.3
Hi all, I am trying to get OpenSSH working on an i386 BSD 3.1 box we have. Everything compiles OK, installs, and I can launch SSHD. Here is a sample session of sshd with the debug switch: <BEGIN SSHD OUTPUT, NAMES CHANGED TO PROTECT THE INNOCENT :)> computer# /usr/local/sbin/sshd -d debug: sshd version OpenSSH-1.2.3 debug: Bind to port 22 on 0.0.0.0. Server listening on 0.0.0.0 port 22.