Re: Transport endpoint is not connected

2023-07-07 Thread hlyg
On 7/8/23 03:00, Andrew M.A. Cater wrote: If you don't have a floppy drive - don't set it up in the BIOS, If you're running off a disk that's connected via USB - it will be slower than the same disk directly attached to SATA. Debian 12 is (probably) no slower than Debian 11 - but it is more

Re: Transport endpoint is not connected

2023-07-07 Thread Andrew M.A. Cater
On Fri, Jul 07, 2023 at 12:34:48AM -0400, hlyg wrote: > deb12 is slow, it complains floppy error. in bios floppy drive is set to > 1.44M though i have no floppy drive. this isn't problem for deb10/11. it's > easy to correct bios setting but i am afraid deb12 is still slow. > If you don't have a

Re: Transport endpoint is not connected

2023-07-06 Thread hlyg
deb11 also complains floppy error, but it isn't slow

Re: Transport endpoint is not connected

2023-07-06 Thread hlyg
deb12 is slow, it complains floppy error. in bios floppy drive is set to 1.44M though i have no floppy drive. this isn't problem for deb10/11. it's easy to correct bios setting but i am afraid deb12 is still slow. Jul 06 23:50:00 bw kernel: scsi 4:0:0:0: Direct-Access USB  SanDisk 3.2Gen1

Re: Transport endpoint is not connected

2023-07-05 Thread D. R. Evans
Greg Wooledge wrote on 7/5/23 08:59: I'm still waiting for setup details to be provided. Is "sh" the user's I was merely trying to inform the OP that he wasn't alone in seeing this "Transport endpoint is not connected" message coming from bookworm when prior versions o

Re: Transport endpoint is not connected

2023-07-05 Thread Greg Wooledge
On Wed, Jul 05, 2023 at 04:49:04PM +0200, to...@tuxteam.de wrote: > On Wed, Jul 05, 2023 at 08:15:14AM -0600, D. R. Evans wrote: > > to...@tuxteam.de wrote on 7/4/23 22:23: > > > > > > > > > > FWIW, since upgrading to bookworm, I see: > > >

Re: Transport endpoint is not connected

2023-07-05 Thread tomas
On Wed, Jul 05, 2023 at 08:15:14AM -0600, D. R. Evans wrote: > to...@tuxteam.de wrote on 7/4/23 22:23: > > > > > > > FWIW, since upgrading to bookworm, I see: > > >sh: 0: getcwd() failed: Transport endpoint is not connected > > > when I ssh

Re: Transport endpoint is not connected

2023-07-05 Thread D. R. Evans
to...@tuxteam.de wrote on 7/4/23 22:23: FWIW, since upgrading to bookworm, I see: sh: 0: getcwd() failed: Transport endpoint is not connected when I ssh into the upgraded box. This seems to be coming from getcwd() (aka get current working directory, see man page). Asking the intertubes

Re: Transport endpoint is not connected

2023-07-04 Thread tomas
On Tue, Jul 04, 2023 at 01:40:18PM -0600, D. R. Evans wrote: > hlyg wrote on 6/28/23 21:32: > > > notification message: Transport endpoint is not connected > > > > FWIW, since upgrading to bookworm, I see: > sh: 0: getcwd() failed: Transport endpoint is

Re: Transport endpoint is not connected

2023-07-04 Thread D. R. Evans
hlyg wrote on 6/28/23 21:32: notification message: Transport endpoint is not connected FWIW, since upgrading to bookworm, I see: sh: 0: getcwd() failed: Transport endpoint is not connected when I ssh into the upgraded box. I have no idea why. (And, just to be clear, this has never

Re: Transport endpoint is not connected

2023-07-04 Thread hlyg
On 7/4/23 16:39, Stanislav Vlasov wrote: Try fio with config copied from /usr/share/doc/fio/examples/ssd-test.fio In config set appropriate size and directory and run `fio new_config` Thank Vlasov! i have never used fio, its manual is long, it isn't foolproof. i have to back up for write

Re: Transport endpoint is not connected

2023-07-04 Thread Stanislav Vlasov
вт, 4 июл. 2023 г. в 13:25, hlyg : > i have installed deb12 in usb disk by kingston, it's slow > > today i install it in sandisk's, it's normal(fast) > > i don't know how to use tool to test usb disk speed Try fio with config copied from /usr/share/doc/fio/examples/ssd-test.fio In config set

Re: Transport endpoint is not connected

2023-07-04 Thread hlyg
i have installed deb12 in usb disk by kingston, it's slow today i install it in sandisk's, it's normal(fast) i don't know how to use tool to test usb disk speed

Re: Transport endpoint is not connected

2023-07-01 Thread hlyg
Thank David, 3 devices are plugged to usb hub: wifi adapter, receiver for wireless keyboard/mouse and usb lamp for power only. i don't have energy to troubleshoot it as it's ok with buster and bullseye,  problem is with deb12, not with my usb device it's not too bad that newly stable deb12

Re: Transport endpoint is not connected

2023-07-01 Thread David Wright
On Fri 30 Jun 2023 at 13:06:49 (+0800), hlyg wrote: > Thank David! i suppose it close wifi connection (say goodbye to hot > spot of cell phone) as i shutdown, i don't have network FS So I assume you use have a wifi dongle, connected to the hub, that communicates with the tethered phone's hotspot.

Re: Transport endpoint is not connected

2023-06-29 Thread hlyg
Thank David! i suppose it close wifi connection (say goodbye to hot spot of cell phone) as i shutdown, i don't have network FS i don't have usb disk plugged to usb hub bookworm for both i386 and amd64 seem uncomfortable with my usb hub. last few lines below show errors i am now using

Re: Transport endpoint is not connected

2023-06-29 Thread David Wright
t in more swapping, for example. With bullseye, I ceased trying to run Firefox on an i386 with 500MB RAM. > even shutdown is slow, i see it painfully show " Transport endpoint is > not connected" So is it waiting for a timeout to expire? > my usb extension line might cause troub

Re: Transport endpoint is not connected

2023-06-29 Thread hlyg
On 6/29/23 09:20, Charles Curley wrote: Two thoughts here. * Does your hub use an external power supply or does it depend on the computer for power? If the latter, that could be a problem if the total load exceeds what the computer supplies. * It could be just a loose connector,

Re: Transport endpoint is not connected

2023-06-29 Thread Charles Curley
On Wed, 28 Jun 2023 23:32:56 -0400 hlyg wrote: > my usb extension line might cause trouble, it connect to back of pc > case at one end, at the other end is usb hub, it's handy because it > turns one usb socket to four sockets, and it works most of time, but > sometime it can cause trouble, i

Transport endpoint is not connected

2023-06-28 Thread hlyg
my general impression of bookworm for i386 is slow i suppose support for i386 becomes poor as its user base shrink even shutdown is slow, i see it painfully show " Transport endpoint is not connected" my usb extension line might cause trouble, it connect to back of pc case

Unable to identify the local socket: Transport endpoint is not connected

2006-10-20 Thread Peter Teunissen
Hi all, Since this morning I suddenly get the following error in my log: oct 20 08:47:47 localhost pure-ftpd: ([EMAIL PROTECTED]) [ERROR] Unable to identify the local socket: Transport endpoint is not connected These log entries appear at fixed intervals: at 2,3,47 and 48 minutes past

[Fwd: Re: [Samba]: getpeername failed. Error was Transport endpoint is not connected]

2006-07-07 Thread Marlos Sedrez
tenho um servidor e esta ocorrendo o seguinte erro no messages: Jul  5 16:19:28 srv smbd[17067]: [2006/07/05 16:19:28,0] lib/util_sock.c:get_peer_addr(1000)  Jul  5 16:19:28 srv smbd[17067]:   getpeername failed. Error was Transport endpoint is not connected Jul  5 16:19:28 srv smbd[17067]: [2006

Re: [Samba]: getpeername failed. Error was Transport endpoint is not connected

2006-07-06 Thread Marlos Sedrez
was Transport endpoint is not connected Jul  5 16:19:28 srv smbd[17067]: [2006/07/05 16:19:28, 0] lib/util_sock.c:get_peer_addr(1000) Jul  5 16:19:28 srv smbd[17067]:   getpeername failed. Error was Transport endpoint is not connected Jul  5 16:19:28 srv smbd[17067]: [2006/07/05 16:19:28, 0

[Samba]: getpeername failed. Error was Transport endpoint is not connected

2006-07-05 Thread Marlos Sedrez
]: getpeername failed. Error was Transport endpoint is not connected Jul 5 16:19:28 srv smbd[17067]: [2006/07/05 16:19:28, 0] lib/util_sock.c:get_peer_addr(1000) Jul 5 16:19:28 srv smbd[17067]: getpeername failed. Error was Transport endpoint is not connected Jul 5 16:19:28 srv smbd[17067]: [2006

Re: [Samba]: getpeername failed. Error was Transport endpoint is not connected

2006-07-05 Thread Marcos Vinicius Lazarini
:19:28 srv smbd[17067]: getpeername failed. Error was Transport endpoint is not connected Jul 5 16:19:28 srv smbd[17067]: [2006/07/05 16:19:28, 0] lib/util_sock.c:get_peer_addr(1000) Jul 5 16:19:28 srv smbd[17067]: getpeername failed. Error was Transport endpoint is not connected Jul 5 16:19

Re: [Samba]: getpeername failed. Error was Transport endpoint is not connected

2006-07-05 Thread joel
was Transport endpoint is not connected Jul 5 16:19:28 srv smbd[17067]: [2006/07/05 16:19:28, 0] lib/util_sock.c:get_peer_addr(1000) Jul 5 16:19:28 srv smbd[17067]: getpeername failed. Error was Transport endpoint is not connected Jul 5 16:19:28 srv smbd[17067]: [2006/07/05 16:19:28

smbd: getpeername failed. Error was Transport endpoint is not connected

2005-11-14 Thread Claus Malter
:09, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2005/11/14 12:08:09, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2005/11/14 12:08:09, 0] lib/access.c:check_access(328