similar to: What magic did openssh do to handle programs like VIM?

Thanks Rowland. I've followed the guide on that page, the following page looks good: https://wiki.samba.org/index.php/Configuring_Point%27n%27Print_automatic_printer_driver_deployment However, when I try to add a driver with "Print Management" to the Samba server, I got an access denied error. Here's how I did it. ------------------------ 1. create a user with smbpasswd,

This is generated with testparam, # Global parameters [global] server string = %h server (Samba, Ubuntu) server role = standalone server map to guest = Bad User obey pam restrictions = Yes pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . unix password sync = Yes syslog =

Hi Darren, As you suggested, I've incorporated pty and enabled raw mode in my client program. VIM runs fine ;-P Now I only need to pass in the terminal window size and handle several signals Thanks for the heads up! On Mon, Feb 10, 2014 at 4:59 PM, Darren Tucker <dtucker at zip.com.au> wrote: > On Mon, Feb 10, 2014 at 7:39 PM, Aaron Lewis <the.warl0ck.1989 at gmail.com>

Are your windows machines part of the 'WORKGROUP' workgroup ? - Yes, and the windows client is not a domain member. I've checked the system properties, it show WORKGROUP Does 'work' exist as a Unix user ? - Yes, otherwise `smbpasswd -a work` complains Does 'work' exist as a windows user ? - No, the windows client can be any user. The current logon username is

Hello, I've posted the question here, http://unix.stackexchange.com/questions/312654/serving-print-driver-through-samba In short, I have a printer configuration ``` [myprinter] comment = Printer Drivers path = /var/lib/samba/printers guest ok = Yes printable = Yes printer name = My Printer ``` However windows will not find/load the drivers, so what files should I place

Hi, When I start sshd with non-absolute path, it complains: sshd re-exec requires execution with an absolute path Is there any security implications? -- Best Regards, Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/ Finger Print: 9F67 391B B770 8FF6 99DC D92D 87F6 2602 1371 4D33

Here is a version of this widely used patch specific for OpenSSH 3.1p1, as it is still not in the main tree (perhap one day...) The patch avoids spending too much time when doing an ssh()/scp() on a down host, as it does not depend off the default TCP timeout used by connect(). Patch was tested on Linux, Solaris and HP-UX. The patch can also be found on:

The attached patch adds a new 'ConnectTimeout' option (man page updated in patch) to avoid wasting time when the target host is down. I needed that because I was using rsync/rdist over ssh for massive files update and the default connect() took too long for my purpose. The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX on Linux, Solaris and HP-UX without

--- p2v/conversion.c | 32 ++++++++++++++++++++++++++------ 1 file changed, 26 insertions(+), 6 deletions(-) diff --git a/p2v/conversion.c b/p2v/conversion.c index 4ff7ecc..5c0c78e 100644 --- a/p2v/conversion.c +++ b/p2v/conversion.c @@ -44,6 +44,16 @@ /* How long to wait for qemu-nbd to start (seconds). */ #define WAIT_QEMU_NBD_TIMEOUT 10 +/* Source port for probing qemu-nbd. Should be one

Hi, re libshout: MacOSX doesn't have poll(), which prevents sock.c from compiling. I've patched sock.c to use select(), which is supported on MacOSX, and should be elsewhere too. I've marked my changes with "SKoT" comments in the file below. Main changes are in sock_write_bytes(). - SKoT ------8<----- /* sock.c * - General Socket Functions * * Copyright (c) 1999

On Fri, Nov 30, 2018 at 09:10:03PM +0800, Jason Wang wrote: > > On 2018/11/30 ??8:55, Jason Wang wrote: > > > > On 2018/11/30 ??8:52, Michael S. Tsirkin wrote: > > > > > ?? If you want to compare it with > > > > > something that would be TCP or QUIC.? The fundamental > > > > > difference between > > > > > virtio-vsock

On Fri, Nov 30, 2018 at 09:10:03PM +0800, Jason Wang wrote: > > On 2018/11/30 ??8:55, Jason Wang wrote: > > > > On 2018/11/30 ??8:52, Michael S. Tsirkin wrote: > > > > > ?? If you want to compare it with > > > > > something that would be TCP or QUIC.? The fundamental > > > > > difference between > > > > > virtio-vsock

Hi, I have the following piece of code, repeat{ ss<-read.socket(sockfd); if(ss=="") break output<-paste(output,ss) } but somehow, output is not receiving all the data that is coming through the socket.My suspicion is on the if statement. what happens if a white space occurs in between the string arriving over the socket? [[alternative HTML version deleted]]

Hi, I have a loop as follows, dataStr <- character(0) repeat{ fstr<-read.socket(sockfd) if(fstr=="") break dataStr<-paste(dataStr,fstr) } at what point does dataStr stop accepting(gets full)? I'm sending millions of records over the socket and need to know if all of it can go into dataStr. Also, Incase all of it cannot go into dataStr, I need to parse each

On Sat, Jan 7, 2017 at 2:30 PM, Peter Moody <mindrot at hda3.com> wrote: > so I spent a bit of time looking at this and it seems like the only > way to go, at least if I want to keep it in ssh_connect_direct(), is > to use pthreads. further, it seems like getting that accepted is > something of a long shot: Sorry, pthreads is a non-starter. I would have thought that using

Here are the new versions of this widely used patch for OpenSSH 3.2.2p1 and 3.2.3p1. The patch avoids waiting to long when using ssh() or scp() on a down host, it is usefull when you have to update many hosts via rsync or rdist themselves relying upon ssh(). It enables a new option 'ConnectTimeout' to control exactly the timeout value, so that it can be used even on slow links. These

As the subject says, support socket activation in virt-p2v. I have added upstream support for socket activation to nbdkit already: https://github.com/libguestfs/nbdkit/commit/7ff39d028c6359f5c0925ed2cf4a2c4c751af2e4 I posted a patch for qemu-nbd, still waiting on more reviews for that one: https://www.mail-archive.com/qemu-devel@nongnu.org/msg427246.html I tested this against old and new qemu

This patch avoids spending too much time during connect() when doing an ssh()/scp() on a down host. It uses a new client option called ConnectTimeout and is useful for rsync or rdist commands using ssh(). See http://bugzilla.mindrot.org/show_bug.cgi?id=207 for detailled info. -------------- next part -------------- --- openssh-3.6.1p1/readconf.c.ORIG Tue Apr 15 23:06:30 2003 +++

Wait up to 10 seconds for qemu-nbd to start up and respond to clients. Otherwise the conversion server may attempt to connect before qemu-nbd is ready to serve it. --- p2v/conversion.c | 72 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ p2v/p2v.h | 1 + 2 files changed, 73 insertions(+) diff --git a/p2v/conversion.c b/p2v/conversion.c index cb2deed..1aefcc6 100644 ---

On Mon, Dec 03, 2018 at 11:10:58AM +0800, jiangyiwen wrote: > On 2018/11/30 21:40, Michael S. Tsirkin wrote: > > On Fri, Nov 30, 2018 at 09:10:03PM +0800, Jason Wang wrote: > >> > >> On 2018/11/30 ??8:55, Jason Wang wrote: > >>> > >>> On 2018/11/30 ??8:52, Michael S. Tsirkin wrote: > >>>>>> If you want to compare it with