Sponsored Content
Full Discussion: Migration
Top Forums UNIX for Advanced & Expert Users Migration Post 102141 by new2ss on Thursday 16th of March 2006 01:24:53 AM
Old 03-16-2006
Thank you for the suggestion.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Migration

Is it possible to migrate a UNIX program and use it in a NetWare or Windows 2000 network? I have a client that must have one of those two operating systems for the new program that they want. However, they've been using an older UNIX program for about 7 years and they want to be able to refer to... (7 Replies)
Discussion started by: refram
7 Replies

2. UNIX for Advanced & Expert Users

migration

hi, is there any tool that i can use to update my scripts (SH scripts) form Unix to linux. please mention any useful websites. thanx in advance (2 Replies)
Discussion started by: omran
2 Replies

3. Solaris

Migration Docd

Hi, I need docs related to migration of Solaris8.0 to solaris10.0. steps to be taken care from developement side.. cheers shell scripts developer (0 Replies)
Discussion started by: mohanpadamata
0 Replies

4. UNIX for Advanced & Expert Users

Solaris migration

Hi , There is going to be a server migration from Solaris 8.0 to Solaris10.0. Could anyone give me some tips and documents regarding the steps to be remembered,tips to be followed etc. like syntax differences any new changes to the existing commands and tools we use whatever the... (1 Reply)
Discussion started by: mohanpadamata
1 Replies

5. Shell Programming and Scripting

code migration

Hi, I am working on migration project. thier are 50,000 scripts. As we are doing 70% of automization for changing the scripts. The remaining 30% doing manually. After doing manual changes i have to find the wheather the change is dont or not and also clode review process. Is there any... (2 Replies)
Discussion started by: unihp1
2 Replies

6. UNIX for Advanced & Expert Users

Migration of users

We are about to get a new server and I need to prepare for migration to the new one. This will be my first migration so I'm sure I will be learning alot. My current server is running CentOS 4.x and I want to move to a sever running Centos 5.x , thought it would make things easier. The old... (1 Reply)
Discussion started by: mcraul
1 Replies

7. AIX

Server migration

Hi, Existing several p5 server with lpar (aix5.3), also implemented with hacmp. And now planning to buy new set of server (installing aix7.1)and SAN to replace the existing server. My question is, how to perform data migration from old server/SAN to new server/SAN. Suppose I install... (6 Replies)
Discussion started by: Oceanlo2013
6 Replies

8. AIX

SAN Migration

Hi all, We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP. Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies

9. AIX

Lpar migration

We have a 2 node oracle rac cluster one node is in frame 1 and other is in frame 2 Now,because of some hardware failure(processor card and cable) in frame 1 we will failover database services from lpar in frame 1 to lpar(oracle rac cluster node2) in frame2 and the entire replacement of hardware... (9 Replies)
Discussion started by: admin_db
9 Replies

10. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 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 05:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy