Sponsored Content
Operating Systems Linux SuSE NoMachine NX window closes after establishing connection Post 302381655 by sles1983 on Saturday 19th of December 2009 11:03:29 AM
Old 12-19-2009
Try clear the tmp files.
 

10 More Discussions You Might Find Interesting

1. Programming

multiuser chat server closes when one client closes. code included

I have been trying to write a very basic chat program but at the moment I am having problems getting it to be multiuser as it closes all connections when one client shutsdown. I have also been having problems trying to get the program to display a list of usernames to the clients. I have tried... (0 Replies)
Discussion started by: dooker
0 Replies

2. UNIX for Dummies Questions & Answers

Establishing connections

Hello there, just a quick question.....Can someone please explain the concept that enables you to establish a connection using the same userId Thanx (1 Reply)
Discussion started by: BigTool4u2
1 Replies

3. Shell Programming and Scripting

Problem establishing Connection on the LAN

Hi everybody i need your help on this I have LAN which run Sun microsystem with solaris 7 OS on each of the servers. The LAN was working fine before an interruption of power supply which makes servers to operating as standalone servers. i.e none of the servers have access to one another. How do i... (2 Replies)
Discussion started by: sbmada
2 Replies

4. UNIX for Advanced & Expert Users

SSH closes connection when using arrow keys

Hi, I'm having a problem with my ssh link to various Sun servers running Solaris 9 and 10 from an Windows XP box running Cygwin/X. I am using ssh to connect to a number of different Sun servers. My problem is that when editing a remote shell command line with the arrow direction keys the... (0 Replies)
Discussion started by: stv_t
0 Replies

5. Solaris

Solaris 10 ftp connection problem (connection refused, connection timed out)

Hi everyone, I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies

6. Ubuntu

establishing connection with e-kermit running on LINUX from my operating system

we designed a primitive operating system for learning basics fundamentals and we created process switching, interrupt/polled IO for device drivers like UART and printers. We accomplish this by using our own tools called SPEDE (for downloading compiled elf image from host ubuntu system that have... (0 Replies)
Discussion started by: bicepjai
0 Replies

7. Solaris

sftp connection closes if idle for around 10minutes

does sftp connection closes by default if it stays idle for a prolonged time ? i have checked sshd_config files , there is no time out value set. but still the connection closes after certain period of time. Please help. verbose mode output : sftp> debug1: channel 0: free:... (10 Replies)
Discussion started by: chidori
10 Replies

8. Shell Programming and Scripting

Establishing remote connection to a Xserver from a UNIX Box

Hello Guys , I have been working on a script where we are looking to connect a remote Xserver from a Unix box. Once a connection is made , i need to run several commands on remote machine to check various stuffs. As per my knowledge on unix (which is like a drop in ocean) , i found SSH as a... (7 Replies)
Discussion started by: himanshu sood
7 Replies

9. UNIX for Beginners Questions & Answers

Sftp connection not establishing from Linux to DataPower

Hi Everyone, I am trying to send files from Linux to DataPower server using public key based authentication but it's not working as expected and every-time password expecting for sftp transfer. Can someone please help on this? Steps I fallowed: Created keys pair at source server... (4 Replies)
Discussion started by: renukeswar
4 Replies

10. Shell Programming and Scripting

Telnet connection closes before i execute GET command

I tried the below steps for telnet command from a remote server: 1. telnet myservice.com 443 2. GET / HTTP/1.0 3. Press enter key twice Please see the output below: bash-3.2$ hostname remoteserver1 bash-3.2$ telnet myservice.com 443 Trying 191.172.172.133... Connected to... (7 Replies)
Discussion started by: mohtashims
7 Replies
Server(3pm)						User Contributed Perl Documentation					       Server(3pm)

NAME
Net::SMTP::Server - A native Perl SMTP Server implementation for Perl. SYNOPSIS
use Carp; use Net::SMTP::Server; use Net::SMTP::Server::Client; use Net::SMTP::Server::Relay; $server = new Net::SMTP::Server('localhost', 25) || croak("Unable to handle client connection: $! "); while($conn = $server->accept()) { # We can perform all sorts of checks here for spammers, ACLs, # and other useful stuff to check on a connection. # Handle the client's connection and spawn off a new parser. # This can/should be a fork() or a new thread, # but for simplicity... my $client = new Net::SMTP::Server::Client($conn) || croak("Unable to handle client connection: $! "); # Process the client. This command will block until # the connecting client completes the SMTP transaction. $client->process || next; # In this simple server, we're just relaying everything # to a server. If a real server were implemented, you # could save email to a file, or perform various other # actions on it here. my $relay = new Net::SMTP::Server::Relay($client->{FROM}, $client->{TO}, $client->{MSG}); } DESCRIPTION
The Net::SMTP::Server module implements an RFC 821 compliant SMTP server, completely in Perl. It's extremely extensible, so adding in things like spam filtering, or more advanced routing and handling features can be easily handled. An additional module, Net::SMTP::Server::Relay has also been implemented as an example of just one application of this extensibility. See the pod for more details on that module. This extension has been tested on both Unix and Win32 platforms. Creating a new server is as trivial as: $server = new Net::SMTP::Server($host, $port); This creates a new SMTP::Server. Both $host and $port are optional, and default to the current hostname and the standard SMTP port(25). However, if you run on a multi-homed machine, you may want to explicitly specify which interface to bind to. The server loop should look something like this: while($conn = $server->accept()) { my $client = new Net::SMTP::Server::Client($conn) || croak("Unable to handle client connection: $! "); $client->process; } The server will continue to accept connections forever. Once we have a connection, we create a new Net::SMTP::Server::Client. This is a new client connection that will now be handled. The reason why processing doesn't begin here is to allow for any extensibility or hooks a user may want to add in after we've accepted the client connection, but before we give the initial welcome message to the client. Once we're ready to process an SMTP session, we call $client->process. This may HANG while the SMTP transaction takes place, as the client and server are communicating back and forth (and if there's a lot of data to transmit, well...). Once $client->process returns, various fields have been filled in. Those are: $client->{TO} -- This is an array containing the intended recipients for this message. There may be multiple recipients for any given message. $client->{FROM} -- This is the sender of the given message. $client->{MSG} -- The actual message data. :) The SMTP::Server module performs no other processing for the user. It's meant to give you the building blocks of an extensible SMTP server implementation. For example, using the MIME modules, you can easily process $client->{MSG} to handle MIME attachments, etc. Or you could implement ACLs to control who can connect to the server, or what actions are taken. Finally, a suggested use that the author himself uses, is as an SMTP relay. There are lots of times I need access to an SMTP server just to send a message, but don't have access to one for whatever reason (firewalls, permissions, etc). You can run your own SMTP server whether under Unix or Win32 environments, and simply point your favorite mail client to it when sending messages. See the Net::SMTP::Server::Relay modules for details on that use. AUTHOR AND COPYRIGHT Net::SMTP::Server / SMTP::Server is Copyright(C) 1999, MacGyver (aka Habeeb J. Dihu) <macgyver@tos.net>. ALL RIGHTS RESERVED. You may distribute this package under the terms of either the GNU General Public License or the Artistic License, as specified in the Perl README file. SEE ALSO
Net::SMTP::Server::Client, Net::SMTP::Server::Relay perl v5.10.1 1999-12-28 Server(3pm)
All times are GMT -4. The time now is 02:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy