10-04-2001
Delay when logging in remote
Hello again!
When I log in to my computer (Ultra 5 running Solaris 8) from a pc (FTP or Telnet) I have to wait forever (about 30 seconds) before I can log in. Is this some kind of security thing? Can I turn it of? How?
Anders
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I want to log-in to a remote server using shell script.
The server requires the following while allowing a connection:
username
password
one - letter authorisation.
How can i implement this in my script?
thanks,
abey (6 Replies)
Discussion started by: abey
6 Replies
2. Shell Programming and Scripting
Hi All,
I am using a script for remotely logging into a rhost using telnet and shutdown a server. The script is as follows.
IP = 10.24.12.23; export IP
UNAME = username ; export UNAME
PWD = password; export PWD
CRDIR = /etc/rc.d/init.d ; export CRDIR
echo "logging into remote... (4 Replies)
Discussion started by: patil_reddy
4 Replies
3. AIX
Hi gurus,
I am trying to configure ssh2 for not asking passwords when logging in from a remote machine, but it is failing. I ran the command based on the oracle documentation. down below are the steps, please do let me know how to get this solved.
the steps followed
$ /usr/bin/ssh-keygen2 -t dsa... (1 Reply)
Discussion started by: arunrao_oradba
1 Replies
4. Cybersecurity
Hi gurus,
I am trying to configure ssh2 for not asking passwords when logging in from a remote machine, but it is failing. I ran the command based on the oracle documentation. down below are the steps, please do let me know how to get this solved.
the steps followed
$ /usr/bin/ssh-keygen2 -t dsa... (2 Replies)
Discussion started by: arunrao_oradba
2 Replies
5. Shell Programming and Scripting
Hi all
I'm creating a script that runs a few commands on some boxes and everything can be logged EXCEPT the java -version command, there doesn't seem to be any output...
Can anyone help explain why this does not work? Do I need to do something extra to append the output from the java... (3 Replies)
Discussion started by: Keepcase
3 Replies
6. Solaris
Hi,
My requirement - for security purpose -
I want all root logins to my solaris servers are done by a script kept
in a separate unix box. This script will telnet into remote solaris server with
root user and log every session via log file.
Now my purpose is to log every telnet session... (3 Replies)
Discussion started by: rahul_jain250
3 Replies
7. SCO
Hello,
I am trying to write log from sco box to a remote host.
We already have that setting working for linux server using syslog.
With this setting(on LINUX)
*.* @remote-host for sco I have this
*.debug /usr/adm/syslog
*.* ... (3 Replies)
Discussion started by: polestar
3 Replies
8. AIX
I've noticed that when running a script that connects to a number of our servers (to essentially run batch commands) that the commands aren't logged in the user's .sh_history or .bash_history files. Is there a place where this is logged (assuming the script itself isn't doing the logging and I'm... (3 Replies)
Discussion started by: kneemoe
3 Replies
9. Shell Programming and Scripting
Below is the code.
I need to login into the router if the 1st set of credentials are correct..
if wrong... then it has to check with 2nd set of credentials..
=> if the credentials are correct... then it should continue..
=> if the credentials are wrong(should not check for 2nd time... then... (0 Replies)
Discussion started by: scriptscript
0 Replies
LEARN ABOUT ULTRIX
elcsd.conf
elcsd.conf(5) File Formats Manual elcsd.conf(5)
Name
elcsd.conf - error logging configuration file
Description
The file contains information used by the daemon to configure error logging for the system. The system manager maintains this file. The
error logging daemon is dependent on the current order of the entries in the file. Do not change the order.
The information in the file shows any defaults and describes what you can enter. A newline is used to delimit each entry in the file, a
null entry consists of a newline alone, and comments begin with #.
#
# elcsd - errlog configuration file
#
{ # delimiter DON'T remove or comment out!
1 # status 1-local,2-logrem,4-remlog,5-remlog+priloglocal
# errlog file size limit num. of blocks
/usr/adm/syserr # errlog dir. path
# backup errlog dir. path
/ # single user errlog dir. path
/usr/adm/syserr # log remote hosts errlog dir. path
# remote hostname to log to
} # delimiter DON'T remove or comment out!
# hosts to log :S - separate file or :R - remotes file (together)
remote1:S
remote2:S
#remote3:S # disabled
remote4:S
.
.
.
The status line of the file describes where you can log error packets, also called error messages:
Logs error packets locally =
1, the default.
Logs error packets from a remote system or systems to the local machine =
2.
Logs local and remote error packets locally =
3.
Logs error packets from the local system to a remote system =
4.
Logs error packets from the local system remotely and logs high
priority messages locally = 5.
The errorlog file size defines the maximum size of an errorlog file. If disk space is limited, you can specify the maximum number of
blocks (512 bytes each) you want the errorlog file to be. If you do not specify the maximum number of blocks, the system will notify you
when the file system is 98% full.
The default errorlog directory path is You can direct error packets to a different directory; if you do, you must change the default for
also. For further information, see
If the error-logging daemon cannot write to the primary errorlog directory path, it attempts to log to the backup errorlog directory path
automatically.
The root directory is the default for the single-user errorlog directory path. When the system makes the transition to multiuser mode,
errors logged in single-user mode are transferred to the default errorlog directory path You can direct single-user error packets to
another directory.
To log error packets from a remote system locally, set up an errorlog directory path on the local system. The default is
Errorlog packets from remote systems can be logged to separate files or to one file. S sets up a separate errorlog file for each remote
system that logs locally. R logs packets from the corresponding remote system to the file syserr.remotes. The default is S.
Restrictions
You must have superuser privileges to change the file. However, anyone can view the file.
Files
elcsd daemon messages
See Also
elcsd(8), eli(8), uerf(8)
Guide to the Error Logger System
elcsd.conf(5)