02-18-2016
easiest way to troubleshoot if it's DNS related would be to ssh directly to the IP rather than the host name.
If the two VM's and the physical server are both having the same issue, and assuming they are all configured the same way. Then I agree it might be a DNS configuration issue.
if it was just one machine having the issue or if you have some application running on all the Solaris hosts then I would see it being an application issue.
again I would recommend running ssh -vvv to see where the delay lies, I would also recommend attempting to ssh directly to the IP to rule out DNS.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
While installing a firewall, I was pinging the interface from SCO 5.0.6 Openserver box, while no response, I hit "DEL" to cancel, but no cancel. Then all of a sudden I get BOO-KOO traffic lights on HUB and Switch.... Then a kernel trap error. System froze... Proceeded with a cold boot. Now I have... (8 Replies)
Discussion started by: nashvillek5
8 Replies
2. Shell Programming and Scripting
Hi all.
I have a problem at work which I have managed to break down into a simple test scenario:
I have written a monitoring script that outputs every second the status of various processes, but for now, lets just print the date
input.sh:
while true
do
date
sleep 1
done
This... (9 Replies)
Discussion started by: spudtheimpaler
9 Replies
3. Linux
Hi, We currently have a problem on a centos server when i try to ssh to it there is a significant delay in getting a login prompt. What would be the steps in troubleshooting this issue? I have try to narrow down a possible network issue but cannot see anything obviously wrong in the routing table,... (4 Replies)
Discussion started by: borderblaster
4 Replies
4. Solaris
Hi All,
I was installed new server M5000 on solaris10. I'am try to connect to server by ssh client (putty) after type user name and password the server take long time to return prompt to me about 30-60 second. any body can suggess me how to do it. (8 Replies)
Discussion started by: cesmk
8 Replies
5. Shell Programming and Scripting
Hi,
i have typed telnet yahoo.com 80 in command prompt
it displays as a blank command prompt page titling as Telnet Yahoo.com
Other than that i am not able to get anything. can anyone sort me out the reason for this (12 Replies)
Discussion started by: satheeshkr_cse
12 Replies
6. Shell Programming and Scripting
Hi,
The code below is used to telnet to list of devices and configure them. The program executes in this manner:
1. telnet to the first device in file.txt
2. one the telnet command is executed a "press any key to continue" prompts.
3. once a return key is executed it ask for username,... (1 Reply)
Discussion started by: sureshcisco
1 Replies
7. Solaris
I am trying to configure a 4 second delay between failed login attempts on SSH. (1 Reply)
Discussion started by: LittleLebowski
1 Replies
8. Red Hat
OS - Oracle Linux 5.6 and 6.3 (Oracle Linux is based on Red Hat).
Background: I have several OL 5.6 virtual machines running under Virtual Box on my Win7 Pro desktop. Due to the way VBox handles networking through the network adapter it installs on the host OS, I build my vm's with 2 virtual... (8 Replies)
Discussion started by: edstevens
8 Replies
9. Solaris
I'm having an issue with SSH on a server that hasn't had any configuration changes made on it in a long time. I SSH to the server and it hangs at "debug1: SSH2_MSG_KEXINIT sent" for exactly 40 seconds then connects fine after that pause. Everything I have found points to DNS, but I use host files... (19 Replies)
Discussion started by: kingdbag
19 Replies
LEARN ABOUT SUSE
mlmmj-recieve
mlmmj-recieve(1) General Commands Manual mlmmj-recieve(1)
NAME
mlmmj-recieve - recieve mails for an mlmmj managed mailinglist
SYNOPSIS
mlmmj-recieve -L /path/to/listdir [-h] [-V] [-P] [-F]
-h: This help
-F: Don't fork in the background (debugging only)
-L: Full path to list directory
-P: Don't execute mlmmj-process (debugging only)
-V: Print version
DESCRIPTION
The mlmmj-recieve binary is the one specified in the mailserver configuration file (aliases file), which writes the mail to the <list-
dir>/incoming directory and invokes mlmmj-process unless the -P option is specified. On systems using mailservers supporting the
/etc/aliases file, a line to activate an mlmmj managed mailinglist would look like this:
list: "|/usr/bin/mlmmj-recieve -L /var/spool/mlmmj/list/"
It's very important to specify the full path to the binary, or the mailinglist will not function.
When the -F option is used, it will not fork in the background. The reason it forks is that if delivery of a mail takes longer time than
the mail server will allow a command to be idle before presumed dead, the mail server would kill it.
SEE ALSO
mlmmj-process(1)
AUTHORS
This manual page was written by the following persons:
Soren Boll Overgaard <boll@debian.org> (based on html2man output)
Mads Martin Jorgensen <mmj@mmj.dk>
mlmmj-recieve September 2004 mlmmj-recieve(1)