similar to: Problemes with ControlPersist

Displaying 20 results from an estimated 300 matches similar to: "Problemes with ControlPersist"

2008 Feb 20
5
procmail deliver and envelope-to
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, first of all, please reply private as I am not subscribed to the list. But if this question takes to much traffic I can subscribe. My problem is that I have to use procmail (as it can call external programs) which finally calls deliver. My main rules are sieve and they work find except that I cannot use subaddress matching in envelope to (not
2011 Nov 15
4
Reopening sqlite3 db
Hello, I am not sure if I trigger a bug and if so it could also be in ruby sqlite3 backend. However, maybe I do something totally wrong. I have the following part in puppet.conf: [master] storeconfigs = true dblocation = /var/lib/puppet/state/clientconfigs.sqlite3 dbadapter = sqlite3 Now every time a client (agent in puppet speak) is run I get one more connection to the
2010 Nov 10
4
Custom facts in current and old environments
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I read that there is several problems about custom facts on this list. However, none is serving my task exactly so I start another. (Topic »custom facts in legacy puppet 0.24.[89]« is the might be the same issue but that gets no answer.) My problem is that I have to serve clients with different versions of puppet. The systems running ubuntu
2010 Oct 26
7
puppetdoc and wrong comparison
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, at the moment I fight with puppetdoc and end in a ruby confusion. To the problem: > puppetdoc --debug --trace --mode rdoc --all manifests/site.pp info: scanning: ["manifests/site.pp"] /usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `output_resource_doc'' /usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `sort''
2010 Jun 06
19
Collecting _all_ ssh keys
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I read and find a way (well, there seems to be several equal implementations) to collect the ssh keys of machines. However they all give only the choice to choose between the key formats. But is there a way to collect both keys of a machine, the rsa _and_ the dss key (and maybe the rsa1 too)? I didn''t find a way to solve this as
2002 Nov 29
3
Version 2.2.6 and above are not able to store big fil es over 2GB
I'm hitting the 2G limit taring from 2.2.2 to ntfs NT4. could this be my problem as well. -----Original Message----- From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org]On Behalf Of Klaus Ethgen Sent: 29 November 2002 4:10 PM To: samba@lists.samba.org Subject: [Samba] Version 2.2.6 and above are not able to store big files over 2GB Hello, when I store a file biger than
2002 Nov 29
6
Version 2.2.6 and above are not able to store big files over 2GB
Hello, when I store a file biger than 2GB to a samba server version 2.2.5 everythink works fine. But when I do that with a server version 2.2.6 or 2.2.7 the saving fails on the 2GB limit. The problem can be seen with windowsclients or with smbclient (any version > 2.2.5). I did some debuging and find that the lseek64 fails. But I didn't find the reason. Regards Klaus Ethgen
2007 Jan 29
1
ControlPersist and multiple X11 forwarding.
Good afternoon! I've been looking for a way to avoid having to keep my "master" ssh session open while I have others open. This is particularly a pain when my "master" is an scp connection. After searching the archives, I came up with this thread "ControlPersist and multiple X11 forwardings." However, I can't find anything saying that it was
2014 Jun 12
1
Improve ControlPersist documentation
Hi, While testing the ControlPersist option (which is very useful by the way, thank you), I find out that setting it to 0 has the same behaviour as setting it to yes, while I would have expected to exit as soon as the last client exits. I'd like to make this behaviour clear, I think it should be documentated in the man page for example like this: $ cvs diff -u ssh_config.5 Index:
2013 Jun 06
2
[Bug 1988] ControlPersist causes stderr to be left open until the master connection times out
https://bugzilla.mindrot.org/show_bug.cgi?id=1988 Darren Tucker <dtucker at zip.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dtucker at zip.com.au Blocks| |2076 -- You are receiving this mail
2007 Jul 05
36
[Bug 1330] New: RFE: 'ControlPersist' support -- automatically fork and leave ControlMaster behind as a dæmon
http://bugzilla.mindrot.org/show_bug.cgi?id=1330 Summary: RFE: 'ControlPersist' support -- automatically fork and leave ControlMaster behind as a d?mon Product: Portable OpenSSH Version: 4.6p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component:
2017 Apr 08
2
lvm cache + qemu-kvm stops working after about 20GB of writes
Hello, I would really appreciate some help/guidance with this problem. First of all sorry for the long message. I would file a bug, but do not know if it is my fault, dm-cache, qemu or (probably) a combination of both. And i can imagine some of you have this setup up and running without problems (or maybe you think it works, just like i did, but it does not): PROBLEM LVM cache writeback
2011 Jul 04
10
[Bug 1917] New: Escape sequence (~) doesn't work right with ControlMaster/ControlPersist connections
https://bugzilla.mindrot.org/show_bug.cgi?id=1917 Bug #: 1917 Summary: Escape sequence (~) doesn't work right with ControlMaster/ControlPersist connections Classification: Unclassified Product: Portable OpenSSH Version: 5.8p1 Platform: All OS/Version: All Status: NEW Severity: normal
2011 Oct 16
4
[Bug 1943] New: [PATCH] ssh -W opens two connections when ControlPersist is enabled.
https://bugzilla.mindrot.org/show_bug.cgi?id=1943 Bug #: 1943 Summary: [PATCH] ssh -W opens two connections when ControlPersist is enabled. Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority:
2020 Mar 14
2
ssh -f and -O ControlPersist=yes, ControlMaster=yes leaves stderr open
Hi I'm trying to wrap ssh in an application using glib. For now, I'm launching the ssh client in master mode and want it to detach, keeping the control socket around. I figured I could do that using the -f flag and the usual Control* options to force ssh to daemonize (ideally without executing any command), but it turns out that glib doesn't recognize the daemonized process as
2013 Jun 06
5
[Bug 1917] Escape sequence (~) doesn't work right with ControlMaster/ControlPersist connections
https://bugzilla.mindrot.org/show_bug.cgi?id=1917 Darren Tucker <dtucker at zip.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dtucker at zip.com.au --- Comment #10 from Darren Tucker <dtucker at zip.com.au> --- Created attachment
2015 Jul 03
6
[Bug 2420] New: Race condition regarding ControlPersist and ControlMaster=auto
https://bugzilla.mindrot.org/show_bug.cgi?id=2420 Bug ID: 2420 Summary: Race condition regarding ControlPersist and ControlMaster=auto Product: Portable OpenSSH Version: 6.6p1 Hardware: amd64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh
2010 May 28
0
Logging bugs (was Re: Toplevel domain and facter)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Klaus Ethgen wrote: > > Behind the line it was more problematic to get to the informations about > the bug tracker and the knowledge to apply to this mailing list with a > non-google address than it is needed and more than it is common with > other software projects. And that was, beside the bug, the main subject > of that thread.
2004 May 22
1
call waiting indicator do not work for me.
Hi, The call waiting indicator do not work for me. I am using a snom200 cwi is switched on in phone-config. Have asked snom, but there are can not help me, because it is working for them. When it is coming in an call while the phone is busy. The phone returns: -- Got SIP response 486 "Busy Here" back from 190.100.200.19 But it should not, should make a "call waiting
1999 Oct 30
2
MD5 passwords in Red Hat Linux 6.1
Hello, Recently I realized that entering first 8 characters from my root password is enough to log in as root although I've enabled MD5 passwords in installation program. Also I've added two other users during installation. After looking through /etc/shadow it seems that root's password isn't md5 although passwords of other two users are md5. Is it correct behaviour? Eugene --