similar to: forwarding stdin/out to remote socket

Hi, I'm trying to configure ssh to get this behaviour: ssh binds on "localhost:60110" and when a local application connect to that port, all the data are forwarded to the "server". The particular fact is that I can't use port forwarding because I don't have any pop3 daemon on the "server". In fact I'm using a pop3 script as user's shell! $

While this isn't a complete fix, this will improve the reliability of drm_dp_get_last_connected_port_and_mstb() pretty significantly during hotplug events, since there's a chance that the in-memory topology tree may not be fully updated when drm_dp_get_last_connected_port_and_mstb() is called and thus might end up causing our search to fail on an mstb whose topology refcount has reached 0,

While this isn't a complete fix, this will improve the reliability of drm_dp_get_last_connected_port_and_mstb() pretty significantly during hotplug events, since there's a chance that the in-memory topology tree may not be fully updated when drm_dp_get_last_connected_port_and_mstb() is called and thus might end up causing our search to fail on an mstb whose topology refcount has reached 0,

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote: > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > > The current way of handling refcounting in the DP MST helpers is really > > confusing and probably just plain wrong because it's been hacked up many > > times over the years without anyone actually going over the code and > > seeing if things

On Tue, Dec 18, 2018 at 04:27:58PM -0500, Lyude Paul wrote: > On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote: > > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > > > The current way of handling refcounting in the DP MST helpers is really > > > confusing and probably just plain wrong because it's been hacked up many > > > times over the

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > The current way of handling refcounting in the DP MST helpers is really > confusing and probably just plain wrong because it's been hacked up many > times over the years without anyone actually going over the code and > seeing if things could be simplified. > > To the best of my understanding, the current scheme

Hi everyone. Zed, thanks for Mongrel. I''ve been running mongrel on my WiFi cafe site (http://wifi.earthcode.com), and it''s been great. It handled a front-page digg a few weeks ago without blinking. However, I''m setting up a staging environment right now, and I''m getting what looks like three mongrel processes *all listening on the same port* for each mongrel

Hello all: I have a couple CentOS 4 servers (all up-to-date) that are having strange command failures. I first noticed this with a perl script that uses lots of system calls. Basically, sometimes a command just won't run: thoth(52) /tmp> ls thoth(53) /tmp> ls thoth(54) /tmp> ls thoth(55) /tmp> ls learner lost+found/ thoth(56) /tmp> ls learner lost+found/ thoth(57)

Hi - I'm having some problems with network browsing using a Samba PDC (3.0.22) and I'd appreciate any hints that might push me in the right direction. One of the problems is that I am on a very crowded subnet that is being used by several different groups. There are a two separate WinNT/2000-style domains active on this network as well as an AD domain controller. Here are the

Hi, samba 3.0.24, debian etch I'm seeing a strange effect with samba and traffic over a bond0 interface in round robin mode. 2 server each with 2 GbE interfaces as bond0 device ind rr mode. netio benchmark: NETIO - Network Throughput Benchmark, Version 1.26 (C) 1997-2005 Kai Uwe Rommel TCP connection established. Packet size 1k bytes: 182840 KByte/s Tx, 197599 KByte/s Rx. Packet size

Hi, I''m having a mysterious problem that occurs when I''m using Rails 1.2.2. My app works fine when the environment.rb file reads: RAILS_GEM_VERSION = ''1.1.6'' When I change this to: RAILS_GEM_VERSION = ''1.2.2'' and try to load http://<mydevhost>:3000/srs/, I get the following traceback in the developer log: Expected

You need to add a semicolon and then the command rm %s to the end of your print command. However, you'll need to delete the files already there manually from Unix. print command = /bin/pt %p %s %M %U %T %a %v %m %I %d;rm %s Steve Litt At 03:22 AM 12/09/1999 +1100, you wrote: >I've set up Samba 2.0.6 for use as a print server on our company NT >network. For some reason, the print

I have set up a Samba server to act as our lab's print server for a bunch of NT clients. It works quite well, except for one thing. Nobody can control the print queue from Windows. When a job is sent, it never shows up in the Windows print queue window, even when there are lots of other jobs ahead of it. Using lpq under Linux shows the jobs just fine. Lprm et al work perfectly too. So I assume

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

Hi Tomas, Thanks for your answer. Indeed, I checked and my R-3.4.1 installed from the ubuntu repository use 'libopenblasp-r0.2.18.so' while my R-3.3.2 that I did compiled on my machine use 'libRblas.so' which explain the difference of behavior. I will use RhpcBLASctl to avoid issue when combining matrix product and other multi-threading package. Maybe this point regarding

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

Hi Ista, Maybe a little comment in the 'matmult {base}' doc page or on the 'options {base}' in the field 'matprod' would be useful to remind users to be cautious regarding BLAS multi-threading? I understand why this is a BLAS related issue and not directly an R related issue. Nonetheless, my concern was for non-advanced R users, that may don't even know what BLAS