zxmaus
Here is my output
So when one VIO goes offline the second one becames active... thats everything is correct but if you do
u will see which interfaces are participating in the SEA ent7 and afterwards if u do lsattr -El ent# (I mean real adapter which participates in the SEA) u will see the following error: entstat: 0909-003 Unable to connect to device ent4, errno = 19 and as I understood thats is normal for the interfaces participating in SEA.. I hope my reply is clear :-)
Hello HP-UX Gurus,
I am having issues trying to start an x-session via eXceed 7.1.
When I bring up eXceed via XDMCP Braodcast I see the host name and IP Address but when I try to connect the X window does not come up.
I made the modification to the following file “/etc/dt/config/Xaccess”... (2 Replies)
Hi friends
recently i have installed SXDE 1/08 into my machine,and i installed wifi driver also
its working fine,Recently i was unable to connect to Internet,I have not changed any configurations and any installations,thing is that i got my iwk0 interface is UP and IP address also and i can... (6 Replies)
I shall explain the situation that I am facing to the best extent possible. I require some help, as this situation is an urgent one.
I am trying to automate sending data from one AIX machine to another. A script runs that tries to push data received from an upstream application to another AIX... (7 Replies)
Hi,
I'm trying to connect from an HP-UX with SSH2 client(ssh2 3.1.2 on hppa1.1-hp-hpux11.00) to an SSH2 server on a VxWorks system. The SSH connection is failing with the below connection logs:
> /usr/local/bin/ssh2 -v -l testuser 10.10.10.10
debug: Ssh2/ssh2.c:1391: Using file... (4 Replies)
Hello all,
Here is the explanation of my problem:
I have a cronjob that connects to a NAS to do backups from my laptop to this NAS device.
The script that I wrote does check if there is a host (the NAS) responding on 192.168.1.10 and tries to connect to it with the following command:
mount -v... (3 Replies)
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
I have managed to install Broadcom BCM43228 Wireless adapter on a laptop running CentOS 5.9 using instructions at:
wiki.centos.org/HowTos/Laptops/Wireless/Broadcom
I had the problem "Error for wireless request "Set Encode" (8B2A): SET failed on device... mentioned on the same page and solved... (0 Replies)
Hi all
unixware 7.1.3 I'm afraid ! I connected a usb tape drive and it was automatically recognised in the device list (sdiconfig -l) and created devices in /dev/rmt (ctape1 etc.). I could successfully read and write to the device.
Then unplugged the usb cable and plugged it back in again... (0 Replies)
Hello,
I just installed CentOS 7 (Server with GUI) and guess what I could install Virtual Box Guest additions without installing any extra package/software which is great news !
Now bad news or not so great news.
My Host OS is Windows 10, Virtual Box is the virtualization software. CentOS7-1... (0 Replies)
After following the instructions given by resident moderator Bakunin over here
https://www.unix.com/aix/279862-installed-memory-32gb-but-shows-only-16gb.html
#1 Connect to ASMI
#2 Configure the deconfigured memory
#3 Start the machine
OK, everything is fine, however now cannot connect to... (5 Replies)
Discussion started by: filosophizer
5 Replies
LEARN ABOUT DEBIAN
net::smtp::server
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)