|
|
| Author |
Message |
mcpoz
|
|
Password rejected
|
Apr 17 12:50 UTC 1995 |
password problems
I just tried to log on to the two 9600 lines and my password was refused.
I then logged on as "trouble" and left a message asking for help and a
temporary password. After that, I logged onto the 2400 line and no problem.
1. I wanted the sysop to know I got back on
2. I have no idea why the 9600 lines rejected my password. I was careful
and typed it slowly.
3. Is there a number I can take for problems such that I can call in and
get someone on a voice line if I need help?
Thanks
|
| 27 responses total. |
popcorn
|
|
response 1 of 27:
|
Apr 17 20:06 UTC 1995 |
This response has been erased.
|
mcpoz
|
|
response 2 of 27:
|
Apr 17 22:24 UTC 1995 |
After my session at 2400 I signed on immediately at 9600 and got on with
out a hitch. I am certain I gave enough care initially to put the
password in without error.
|
robh
|
|
response 3 of 27:
|
Apr 17 22:52 UTC 1995 |
(1) What sysop? >8)
This reminds me of a problem I had one time many moons ago, when I
tried calling another (not Grex) board, typed in my password, and
it *insisted* that that wasn't my correct password. I created
a new account, left mail for the sysop asking him to help, then went
to do some other things - and discovered that the Z key on my
keyboard wasn't working. And there was a Z in my password. And
of course, the system wasn't echoing my password, so I had no idea
it wasn't going through. D'OH!!!
So maybe it's time for me to drag out that file on how to
clean your keyboard safely...
|
mcpoz
|
|
response 4 of 27:
|
Apr 17 23:14 UTC 1995 |
Robh, Thanks - I'll watch for errors especially in the letters in my
password.
|
davel
|
|
response 5 of 27:
|
Apr 18 01:50 UTC 1995 |
Line noise has definitely been known to take out password recognition.
This seems unlikely (you probably would have noticed, if there were
consistent enough noise to garble several attempts), but I have no
better suggestions.
|
scg
|
|
response 6 of 27:
|
Apr 18 03:57 UTC 1995 |
I too have had keyboard related password problems, and not been able to
explain them at first. If you're trying to log in and consistently
getting your password rejected, you might try typing in your password in
another window (one that echos), and see whether it echos the whole
password or whether it's missing a character. When I've had problems like
that, the two quick fixes I've found are to make sure the keyboard is
plugged in all the way, and if that doesn't work to bang on the offending key
until it starts echoing. The long term solution is to pull the key apart
and clean it. If you have several keys like that, or if it doesn't
respond to cleaning, then it may be easier to buy a new keyboard.
|
davel
|
|
response 7 of 27:
|
Apr 18 11:23 UTC 1995 |
Hm. Neat idea, Steve - switch to half-duplex long enough to enter your
password.
|
scg
|
|
response 8 of 27:
|
Apr 19 03:40 UTC 1995 |
I should also mention that if you're going to type out your password in
such a way that it echos, you shouldn't do it with somebody looking over
your shoulder.
|
jbo
|
|
response 9 of 27:
|
May 9 15:21 UTC 1995 |
i have had problems "ftping" into grex, it is rejecting my password
anyone else having this problem ?
|
robh
|
|
response 10 of 27:
|
May 9 22:56 UTC 1995 |
I had this problem too, until I ftp'ed to
ftp.cyberspace.org, not grex.cyberspace.org or cyberspace.org.
That seemed to clear things up.
(Not that I needed to ftp anything, since Grex is the only system
I call, but I wanted to find out why it wouldn't work for
anyone else...)
|
rcurl
|
|
response 11 of 27:
|
May 10 17:07 UTC 1995 |
I use the Mac ftp client Fetch, and with it Grex accepted the host name
cyberspace.org. The only problem I had was specifying the full directory
path: it would not permit entry at a higher directory level (though this
may have been due to the perms on higher directories). Rob, one might want
to ftp files to/from your or other directories: I was downloading
figlet-faq.
|
robh
|
|
response 12 of 27:
|
May 10 21:25 UTC 1995 |
Oh, I know, but since I only ever call grex, I personally
would only ever ftp files from Grex to Grex, which could just
as easily be done with the cp command.
|
jbo
|
|
response 13 of 27:
|
May 11 02:23 UTC 1995 |
You would'nt mind X-plaining the "cp compand" would you,
appreciate help.
|
peacefrg
|
|
response 14 of 27:
|
May 11 04:20 UTC 1995 |
You use the cp command when you want to copy one file to another directory.
You would use it in the same format as DOS 'copy example.exe c:\example
Exept for unix it would be 'cp example.exe \example'
Hope that helps.
|
davel
|
|
response 15 of 27:
|
May 11 10:52 UTC 1995 |
Make that cp example.exe /u/yourusername/example or something like
that. The backslash won't work, and you (hopefully) don't have rights
to put stuff under the root that way.
John, in general, you can get an online explanation of most any Unix command
by running a program called man (for "manual). For example,
man cp
(or !man cp if you're running it from an Ok: or Respond-or-pass:
prompt).
|
peacefrg
|
|
response 16 of 27:
|
May 11 12:44 UTC 1995 |
Yes, I'm sorry. I meant a forward slash.
I have never had to put /u/peacefrg though unless I'm putting something
in my root dir.
|
robh
|
|
response 17 of 27:
|
May 12 02:38 UTC 1995 |
Trying to speak DOS in a Unix environment is a bad idea. >8)
|
peacefrg
|
|
response 18 of 27:
|
May 12 05:28 UTC 1995 |
Yeah I noticed.
BTW: Speaking of Dos -> Unix
What is the Unix similar command to copy con <filename>.bat?
|
scg
|
|
response 19 of 27:
|
May 12 06:01 UTC 1995 |
cat > filename
|
davel
|
|
response 20 of 27:
|
May 12 11:11 UTC 1995 |
(Terminated with your EOF character - commonly ^D, almost never ^Z - and
followed by a chmod to give you execute access to the file you created.)
|
popcorn
|
|
response 21 of 27:
|
May 12 12:55 UTC 1995 |
This response has been erased.
|
peacefrg
|
|
response 22 of 27:
|
May 12 16:25 UTC 1995 |
And what is a batch file? I mean if I make a program with cat
will it automatically run when I enter it? Or will it just
print up on the screen?
|
davel
|
|
response 23 of 27:
|
May 12 17:54 UTC 1995 |
What Steve gave you was a way to create a file using cat (analogous to using
COPY under DOS in your example). There's no extension such as .BAT for shell
scripts ("batch programs") under Unix; however:
- your script needs to be a valid Unix shell script (program) for whatever
shell is going to execute it, not a collection of MS-DOS commands.
- for your script to be executed, the person running it must have
execute (and read) access to the script. Hence my mention of chmod.
A shell is more or less the equivalent of COMMAND.COM under DOS. Under DOS,
that's normally the only command-line interpreter available. Under Unix,
there are a bunch (sh, csh, tcsh, bash are here - I don't think ksh is but
I could be wrong). You can put a special line at the beginning of a script
to specify what shell should run it; I believe it will run under sh if you
don't do so.
(The syntax of all these shells varies, so which shell executes your script
is important. However, many (most!) Unix commands are programs, and in general
a program won't care what shell calls it.)
|
peacefrg
|
|
response 24 of 27:
|
May 12 21:05 UTC 1995 |
Cool, we should start a unix conf. I would love to learn how to write
scripts and stuff. It's so interesting. Thatnks dave.
|