Sponsored Content
Full Discussion: Perl script stopped working
Top Forums Shell Programming and Scripting Perl script stopped working Post 302904247 by belalr on Tuesday 3rd of June 2014 05:22:55 AM
Old 06-03-2014
Thanks for your reply.

I don't understand how the script know that password in entered in the first place.

as of now the script doesn't wait for password or anything, it just immediately give the error without allowing user to enter any character.

Please advise.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

#!/bin/bash has stopped working

Hi I'm writing a script and I've put #!/bin/bash as the first line so that I can just type my scripts name 'whodate' at PS1 instead of ./whodate. This has suddenly stopped working for me. It used to be the case that I could start a script with #!/bin/bash and it would work, but for this script... (2 Replies)
Discussion started by: zorrokan
2 Replies

2. Linux

Cronjobs stopped working

Hi All, I am user of a Linux machine and I have approximatly 15 cronjobs scheduled in my crontab. Yesterday my administrator made LDAP active on my userid and all the things are doing fine after that. But all cronjobs for my user id stored in my crontab have stopped working after that. Could... (1 Reply)
Discussion started by: bisla.yogender
1 Replies

3. Shell Programming and Scripting

cronjobs stopped working

Hello people, I had these cronjobs scheduled in some Unix boxes which were running fine until yesterday.But then the password was changed for that user id and then the jobs stopped working. As far as i know cron jobs run from super user. I am completely lost over here now. Thanks. (2 Replies)
Discussion started by: King Nothing
2 Replies

4. UNIX for Advanced & Expert Users

suPHP stopped working after dist-upgrade

Hi all, My server was Debian Etch (4) and had a working suPHP module (version 0.6.2-1). After I dist-upgraded it to Lenny (Debian 5), suPHP (version 0.6.2-3) stopped working. I read in the mailing list that I should change the settings of /etc/suphp/suphp.conf to this form: ;Handler... (1 Reply)
Discussion started by: mjdousti
1 Replies

5. IP Networking

Wireless stopped working- Fedora 12

I installed F12 around the time it was released and it picked up my wireless card and worked like a charm.....Suddenly last week everything stopped working and I receive what appears to be a driver error when wlan0 tries to load. Error for wireless request "Set Mode" (8B06) : SET failed on... (1 Reply)
Discussion started by: woodson2
1 Replies

6. Ubuntu

Ubuntu 10.10 LAN connection stopped working...

Well this is weird. I restarted my dual boot Win7/Ubuntu 10.10 from ubuntu to windows. Everything was working fine and windows is always connecting properly to my lan. After restarting back into Ubuntu, all of a sudden I can't connect to my network. It looks as if its trying to connect through... (15 Replies)
Discussion started by: zixzix01
15 Replies

7. UNIX for Dummies Questions & Answers

Ssh stopped working AIX

I Was able to ssh into the AIX box. now i cannot When I run the command to start it it comes back that is was started, but still does not work. Here is a shot i what i see # server:/> lslpp -l | grep ssh openssh.base.client 4.3.0.5201 COMMITTED Open Secure Shell Commands ... (2 Replies)
Discussion started by: fierfek
2 Replies

8. AIX

Printer stopped working

I have a serial printer connected to a 16 port ran. All of a sudden my printer stopped working and not sure how to get it back. Can anyone help pint me in the write direction? lsdev -Cc printer gives me the following. lp0 Defined 0A-08-11-00 Other serial printer lp1 Defined 0A-08-11-03... (3 Replies)
Discussion started by: Gmanx
3 Replies

9. Solaris

Mailx stopped working

after a new patch set on the 14th. I noticed that mailx stopped working, as far a I can tell that is the only thing that changed. solaris 10 OS it seems everything is the same, sendmail seems to be running root@server # ps -ef | grep -i sendmail smmsp 687 1 0 10:42:25 ? ... (0 Replies)
Discussion started by: goya
0 Replies
rlogin(1)						      General Commands Manual							 rlogin(1)

NAME
rlogin - Connects the local host with a remote host SYNOPSIS
rlogin [-8L] [-e character] [-l user] remote_host The remote login command (rlogin) logs into remote_host and connects your local terminal to the remote host. OPTIONS
Allows an 8-bit data path at all times. Otherwise, unless the Stop and Continue key sequences on the remote host are not standard, rlogin uses a 7-bit data path and the eighth (high) bit of each byte is stripped. Changes the Escape character. Substitute the character you choose for character. Changes the remote username to the one you specify. Otherwise, your local username is used at the remote host. Allows the rlogin session to be run in litout mode. In this mode, the escape sequence ~. (where ~ is the escape character) disconnects you from the remote host and the escape sequence ~^Z (where ^Z, or Ctrl-Z, is the suspend character) suspends the rlogin session if you are using csh. DESCRIPTION
The remote terminal type is the same as that given in the local TERM environment variable. The terminal or window size is also the same, if the remote host supports them, and any changes in size are transferred. All echoing takes place at the remote host, so except for delays, the terminal connection is transparent. Pressing the Stop and Continue key sequences stops and starts the flow of information, and the input and output buffers are flushed on Interrupts. The rlogin command can only be used to connect to systems that are running the rlogind daemon. On systems that do not support rlogin, you can use telnet (if supported) as an alternative. If you do not specify the -l option, the local username is used at the remote host. If -l user is specified, the username entered is used at the remote host. In either case, the remote host allows access only if one or both of the following conditions is satisfied: The local host is included in the remote host's /etc/hosts.equiv file, the local user is not the superuser, and the -l user option is not specified. The local host is included in a $HOME/.rhosts file in the home directory of the remote user account. If -l user is specified, the local username must also be included in the file. If neither of these conditions is met and a password is defined for the remote user account, the remote host prompts for a password. The remote password file is checked to verify the password entered, and the login prompt is displayed if the password is not correct. Pressing the End-of-File key sequence at the login prompt ends the remote login attempt. For security reasons, any $HOME/.rhosts file must be owned by either the remote user or the root user and should have permissions set to 600 (read and write by owner only). In addition to the preceding conditions, rlogin also allows access to the remote host if the remote user account does not have a password defined. However, for security reasons, use of a password on all user accounts is recommended. Unless otherwise modified by the -e option, the standard Escape character for disconnecting from the remote host is a ~ (tilde). The Escape character is only recognized by the remote host if it occurs at the beginning of a line. Otherwise, the Escape character is sent to the remote host as a normal character. To send the Escape character to the remote host as a normal character at the beginning of a line, press the Escape character twice. Pressing the Escape character and a (dot) (for example, ~.) immediately disconnects the local terminal from the remote host. EXAMPLES
In the following examples, the local host is listed in the /etc/hosts.equiv file at the remote host: To log in to a remote host with your local username, enter: $ rlogin host2 Password: <Enter password> To log off the remote host and close the connection, enter the End-of-File key sequence. To log in to a remote host with a differ- ent username, enter: $ rlogin host2 -l dale You are prompted to enter your password and then are logged in to the remote host host2 with the username dale. To log in to host2 with the your local username and change the Escape character to (backslash), enter: $ rlogin host2 -e\ FILES
Specifies remote hosts from which users can execute commands on the local host (provided these users have an account on the local host). Specifies remote users who can use a local user account. SEE ALSO
Commands: rcp(1), rsh(1), rlogind(8), telnet(1) Files: rhosts(4) rlogin(1)
All times are GMT -4. The time now is 08:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy