|
|
| Author |
Message |
| 25 new of 293 responses total. |
keesan
|
|
response 102 of 293:
|
Jan 22 21:16 UTC 2002 |
Why so slow right now?
|
gelinas
|
|
response 103 of 293:
|
Jan 22 22:19 UTC 2002 |
The usual culprits are 'load', which can be checked with the "uptime" command
(in picospan, !uptime at the nearest prompt), and 'network traffic', which
I've not found a way to check from grex (the usual tools are
disabled/restricted because of their usefulness to Bad Guys (TM)).
|
keesan
|
|
response 104 of 293:
|
Jan 22 22:50 UTC 2002 |
Fixed.
|
tsty
|
|
response 105 of 293:
|
Jan 23 16:31 UTC 2002 |
uhhh, re 100, 101 ... that looks like the um pine stuff although there
is some similarity. and , i *have* looked with both less and setup
NumerousTimes (tm) trying to figure this out.
does your .pinerc explicitly state:
# Syntax: optnl-label {optnl-imap-hostname}optnl-directory-path[]
folder-collections=IMAP Server {g.imap.itd.umich.edu}mail/[],
IFS home directory mail/[]
(the first-column braces are indent chars, i presume)
|
tsty
|
|
response 106 of 293:
|
Jan 23 16:34 UTC 2002 |
for the record, .pinerc states:
# Path of (local or remote) INBOX, e.g. ={mail.somewhere.edu}inbox
# Normal Unix default is the local INBOX (usually /usr/spool/mail/$USER).
inbox-path=/a/t/s/tsty/pine/INBOX
###################### Collections, Folders, and Files #####################
# List of incoming msg folders besides INBOX, e.g. ={host2}inbox, {host3}inbox
# Syntax: optnl-label {optnl-imap-host-name}folder-path
incoming-folders=
and there are no [] indicated anywhere ???????????????????
|
gelinas
|
|
response 107 of 293:
|
Jan 23 18:27 UTC 2002 |
Yup; that's a copy-and-paste from my current .pinerc. Here's what shows
on grex:
:r ~/.pinerc
# Updated by Pine(tm) 3.96, copyright 1989-1996 University of Washington.
#
# Pine configuration file -- customize as needed.
{Ellipsis. JLG.}
########################### Essential Parameters ###########################
# Over-rides your full name from Unix password file. Required for PC-Pine.
personal-name=
{Ellipsis. JLG.}
# Path of (local or remote) INBOX, e.g. ={mail.somewhere.edu}inbox
# Normal Unix default is the local INBOX (usually /usr/spool/mail/$USER).
inbox-path=
###################### Collections, Folders, and Files #####################
# List of incoming msg folders besides INBOX, e.g. ={host2}inbox, {host3}inbox
# Syntax: optnl-label {optnl-imap-host-name}folder-path
incoming-folders=
# List of directories where saved-message folders may be. First one is
# the default for Saves. Example: Main {host1}mail/[], Desktop mail\[]
# Syntax: optnl-label {optnl-imap-hostname}optnl-directory-path[]
folder-collections=
{Ellipsis. JLG.}
# List of context and folder pairs, delimited by a space, to be offered for
# pruning each month. For example: {host1}mail/[] mumble
pruned-folders=
# Over-rides default path for sent-mail folder, e.g. =old-mail (using first
# folder collection dir) or ={host2}sent-mail or ="" (to suppress saving).
# Default: sent-mail (Unix) or SENTMAIL.MTX (PC) in default folder collection.
default-fcc=
{Elision of remainder. JLG.}
That's all I know.
|
tsty
|
|
response 108 of 293:
|
Jan 24 04:45 UTC 2002 |
yeh, right, tha's how my grex pine STARTED. then i added the
explicit stuff ... adn get teh errors. your grex pine has NO customization.
was teh first example from um's pine?
|
gelinas
|
|
response 109 of 293:
|
Jan 24 04:53 UTC 2002 |
Yes.
|
tsty
|
|
response 110 of 293:
|
Jan 25 09:58 UTC 2002 |
staff: question: is the protocol gelinas used on um's pine applicable
to the pine that grex uses?
|
senna
|
|
response 111 of 293:
|
Jan 25 09:59 UTC 2002 |
Last night and this morning, Grex has been randomly killing my connection
after short (five-ten minutes) periods of time. The rest of my internet
connection works fine while this is happening, but I get nothing here. Any
ideas?
|
gelinas
|
|
response 112 of 293:
|
Jan 25 13:19 UTC 2002 |
try a traceroute from your starting point to grex; look for dropped packets.
|
jp2
|
|
response 113 of 293:
|
Jan 25 14:49 UTC 2002 |
This response has been erased.
|
davel
|
|
response 114 of 293:
|
Jan 25 15:15 UTC 2002 |
Re 112 re 111: This has happened to me intermittently, but way too often,
lately. But I was dialed in, and my starting point was just the term server,
I think.
|
russ
|
|
response 115 of 293:
|
Jan 26 18:56 UTC 2002 |
Amidst a download of a pile of e-mail, I got this on my tty:
Sat Jan 26 13:52:03
This terminal has been idle 15 minutes. If it remains idle
for 5 more minutes it will be logged out by the system.
Can't Grex recognize that a terminal running something like sz
is NOT idle and should NOT have unwanted data dumped on it,
let alone be cut off?
|
tsty
|
|
response 116 of 293:
|
Jan 26 21:51 UTC 2002 |
i thought that had been fixed when yu were in short pants?
|
davel
|
|
response 117 of 293:
|
Jan 26 22:30 UTC 2002 |
I'm rather puzzled as to how you saw the message, if it was in the middle of
a file transfer.
|
russ
|
|
response 118 of 293:
|
Jan 27 19:59 UTC 2002 |
The "down until approximately 1 PM" notice on Grex was still playing
at 1:42 PM. If backups are going to take longer or be started later,
it would be much friendlier of staff to correct the estimate to be
closer to reality.
|
gull
|
|
response 119 of 293:
|
Jan 27 20:28 UTC 2002 |
The problem may be that if it's not known that it'll take longer before
the backups are started, changing the estimate would require modifying
a filesystem being backed up, which is generally considered a Bad Idea.
|
aruba
|
|
response 120 of 293:
|
Jan 27 22:39 UTC 2002 |
Thanks, Scott, for doing that backup!
|
drew
|
|
response 121 of 293:
|
Jan 27 23:55 UTC 2002 |
Re #119: Not necessarily. It's possible to put both multiple filesystems and
multiple OSes on a single machine, and even on a single hard drive! A small
special purpose OS/filesystem could be dedicated to showing the estimate and
running the backup software.
|
russ
|
|
response 122 of 293:
|
Jan 28 00:21 UTC 2002 |
Re #117: It was actually just a bit after downloading over 1/2 megabyte
of e-mail and conference text. Regardless, it should not have occurred.
Even if the idle-killer checks the tty to see if it's in raw mode and
ignores it, one could be logged out immediately after finishing a
download if the timing is exactly wrong.
|
polytarp
|
|
response 123 of 293:
|
Jan 28 00:42 UTC 2002 |
Pl-e--a---s----e-----! -I-- ---n----e-----ed- --h---e----l-----p!-
B--r---o----k-----en- --t---h----i-----s -i--s---!----
|
mvpel
|
|
response 124 of 293:
|
Jan 29 01:14 UTC 2002 |
Grex does not appear to be running the Network Time Protocol daemon, and its
clock is coming up on a minute fast.
|
tsty
|
|
response 125 of 293:
|
Jan 29 15:02 UTC 2002 |
threr might be an Xnix version as well, but nistime32 (googls search)
is an excellent windoze time synchronizer, fwiw. even works
on xp!
|
mvpel
|
|
response 126 of 293:
|
Jan 30 07:53 UTC 2002 |
Re: 110 - Back when I first deployed Pine at UM, I used the IMAP protocol.
I doubt that anything has changed since then. If you set your mailbox to
{mailserver.name.whatever}INBOX, Pine will attempt to use IMAP to connect to
it.
|