shell lag

[nhdesign]

Hi,

Is anyone else experiencing a lag when typing in putty on shell.sonic.net.

Thanks,
Vic

[nhdesign]

My join date is 2001-08-21, not the displayed 2012, how do I correct it?

Thanks,
Vic

[danielg4]

This forum did not exist in 2001. There was a group on Sonic's now-defunct NNTP server before around 2012 that it replaced.

[nhdesign]

I did not know that.
When did you join sonic?
Best shell server on the west coast, well rahul was pretty good too, wonder if Desi is still running it.
Wish I could still use tin for usenet, here at sonic.

So who is using the shell?
Have you noticed a lag when reading mutt or while vi'ing?

--
Vic

[danielg4]

I did not know that.
When did you join sonic?

Order placed 2010-11-06, connected 2010-11-11, opting out of shell service because I have access to multiple other shells already, and I often had such lags in vi in the ADSL days, but with FTTN, it's only happened when the remote server's connection has had issues. What last-mile technology are you on? You may wish to simply have your own shell server on your LAN, like I did in the past and will probably do again.

[nhdesign]

Are there any shell.sonic.net users monitoring this group?
Sonic employees once monitored this group, do they still?

--
Vic

[dherr]

I am not a frequent user of the sonic shell, but I have it enabled for my account.

I am on FTTN, so my connection is not as direct as for a "pure" sonic user. I don't see any lag in the shell. I tried simply typing and also running vi.

As for network distance, my default router is about 17 ms away and the shell host is as so...

>ping -c 5 shell.sonic.net
PING bolt.sonic.net (208.201.242.19) 56(84) bytes of data.
64 bytes from bolt.sonic.net (208.201.242.19): icmp_seq=1 ttl=52 time=24.3 ms
64 bytes from bolt.sonic.net (208.201.242.19): icmp_seq=2 ttl=52 time=24.4 ms
64 bytes from bolt.sonic.net (208.201.242.19): icmp_seq=3 ttl=52 time=24.3 ms
64 bytes from bolt.sonic.net (208.201.242.19): icmp_seq=4 ttl=52 time=24.4 ms
64 bytes from bolt.sonic.net (208.201.242.19): icmp_seq=5 ttl=52 time=24.3 ms

[bobrk]

Best shell server on the west coast, well rahul was pretty good too, wonder if Desi is still running it.

I have not heard that name for a very long time. I was "rrk" at rahul.net, great service for getting into the internet...

Seems like the web page is still there, super fast loading, too!

http://www.rahul.net

[joemuller]

Are there any shell.sonic.net users monitoring this group?
Sonic employees once monitored this group, do they still?

--
Vic

Employee here.

Usually, lag over SSH is caused by either a heavy load on the server or latency/packet-loss between the client/server. We've certainly seen spikes in CPU usage from time-to-time, but in general, I'd put odds on high latency and/or packet loss.

The next time you experience lag to the shell server, I recommend running 'mtr' if you're on Linux/BSD/MacOSX or tracert on Windows. Take a look to see if the majority of the delays are happening in the first couple hops (likely on your local LAN), somewhere in-between, or at the end (shell.sonic.net).

Wish I could still use tin for usenet, here at sonic.

'tin' and 'trn' are still installed and available, you just need to point it to the newsgroup provider of your choosing. (eternal-september is an excellent choice for free access to text-only newsgroups)

-- Joe