Sponsored Content
Full Discussion: SCO TCP/IP ?
Operating Systems SCO SCO TCP/IP ? Post 302535094 by doc_holiday on Wednesday 29th of June 2011 05:28:41 PM
Old 06-29-2011
Hello Ed,

the forum wont let me send a PM. Best is if you send me your email as PM
and I respond there directly.

Regards, Michael
 

9 More Discussions You Might Find Interesting

1. IP Networking

TCP/IP printing on SCO 2.1.3

I am trying to set up TCP/IP printing to so we can remove the old novel server. The printer details have been added to the etc/hosts file correctly, and the printer added as a remote UNIX printer . However when a print job is issued lpstat -o displays the job, but it dosent move. Any help yould... (2 Replies)
Discussion started by: eel_king
2 Replies

2. Filesystems, Disks and Memory

SCO TCP/IP runtime System for SCO Unix

Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies

3. UNIX for Dummies Questions & Answers

SCO UNIX "TCP/IP not licensed error"

I have been running 5.0.02 for more than 10 years in its present configuration. I am running a business software package on it (text based). I am trying to use my windows machines to access it through a program like "reflections" so that I can run my software from different systems but I get... (2 Replies)
Discussion started by: Parkegio
2 Replies

4. SCO

all tcp are CLOSED on SCO Unix on VMWARE

Hi folks, First of all, sorry about my english, isn't the best and thks for advance. Here es my problem... I have virtualize an SCO unix with VMware ESX 3 and everything was going on beatifull until that i try to connect from anorther host, i can't do it so i check the connection with... (5 Replies)
Discussion started by: martocapo
5 Replies

5. SCO

/dev/inet/tcp not listening in SCO 6.

While in SCO Openserver 5.0.7, Sybase listened to /dev/inet/tcp, the same is not working in SCO Openserver 6. The Network card is however active and pinging fine. What can be the reason? What is the way out? An early response will be appreciated. Thank you Regards TCG (2 Replies)
Discussion started by: thecobolguy
2 Replies

6. SCO

TCP in sco unix 3.2

Hi every body. I am looking for TCP package under sco unix 3.2 or sco xenix system. would you please help me? (7 Replies)
Discussion started by: javad1_maroofi
7 Replies

7. SCO

SCO TCP/IP 1.2.0. floppys needed

Hi, every body, I have the same problem but with the SCO TCP/IP 1.2.0. I have the 3 floppy disks but I get an error on disk 3, unreadable. I have seen the closed post regarding the sco tcp/ip. Does anybody have those disks? Thank you in advance Mariano (8 Replies)
Discussion started by: locovich
8 Replies

8. SCO

Sco Openserver Starting TCP/IP Services

Hi all, I have a customer whose sco unix server wasnt power off correctly and when booting it up I noticed that the boot up takes a while to finish the " Starting TCP services: snmpd routed lpd". after that the server is ready for login, but you cannot ping anything from the server (apart from... (2 Replies)
Discussion started by: CharlL
2 Replies

9. Solaris

Too much TCP retransmitted and TCP duplicate on server Oracle Solaris 10

I have problem with oracle solaris 10 running on oracle sparc T4-2 server. Os information: 5.10 Generic_150400-03 sun4v sparc sun4v Output from tcpstat.d script TCP bytes: out outRetrans in inDup inUnorder 6833763 7300 98884 0... (2 Replies)
Discussion started by: insatiable1610
2 Replies
Email::Send::Test(3pm)					User Contributed Perl Documentation				    Email::Send::Test(3pm)

NAME
Email::Send::Test - Captures emails sent via Email::Send for testing SYNOPSIS
# Load as normal use Email::Send; use Email::Send::Test; # Always clear the email trap before each test to prevent unexpected # results, and thus spurious test results. Email::Send::Test->clear; ### BEGIN YOUR CODE TO BE TESTED (example follows) my $sender = Email::Send->new({ mailer => 'Test' }); $sender->send( $message ); ### END YOUR CODE TO BE TESTED # Check that the number and type (and content) of mails # matched what you expect. my @emails = Email::Send::Test->emails; is( scalar(@emails), 1, 'Sent 1 email' ); isa_ok( $emails[0], 'Email::MIME' ); # Email::Simple subclasses pass through DESCRIPTION
Email::Send::Test is a driver for use in testing applications that use Email::Send to send email. To be able to use it in testing, you will need some sort of configuration mechanism to specify the delivery method to be used, or some other way that in your testing scripts you can convince your code to use "Test" as the mailer, rather than "Sendmail" or another real mailer. How does it Work Email::Send::Test is a trap for emails. When an email is sent, it adds the emails to an internal array without doing anything at all to them, and returns success to the caller. If your application sends one email, there will be one in the trap. If you send 20, there will be 20, and so on. A typical test will involve doing running some code that should result in an email being sent, and then checking in the trap to see if the code did actually send out the email. If you want you can get the emails out the trap and examine them. If you only care that something got sent you can simply clear the trap and move on to your next test. The Email Trap The email trap is a simple array fills with whatever is sent. When you send an email, it is pushed onto the end of the array. You can access the array directly if you wish, or use the methods provided. METHODS
send $message As for every other Email::Send mailer, "send" takes the message to be sent. However, in our case there are no arguments of any value to us, and so they are ignored. It is worth nothing that we do NOTHING to check or alter the email. For example, if we are passed "undef" it ends up as is in the trap. In this manner, you can see exactly what was sent without any possible tampering on the part of the testing mailer. Of course, this doesn't prevent any tampering by Email::Send itself :) Always returns true. emails The "emails" method is the preferred and recommended method of getting access to the email trap. In list context, returns the content of the trap array as a list. In scalar context, returns the number of items in the trap. clear The "clear" method resets the trap, emptying it. It is recommended you always clear the trap before each test to ensure any existing emails are removed and don't create a spurious test result. Always returns true. deliveries This method returns a list of arrayrefs, one for each call to "send" that has been made. Each arrayref is in the form: [ $mailer, $email, @rest ] The first element is the invocant on which "send" was called. The second is the email that was given to "send". The third is the rest of the arguments given to "send". SUPPORT
All bugs should be filed via the CPAN bug tracker at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Email-Send-Test <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Email-Send-Test> For other issues, or commercial enhancement or support, contact the author. AUTHORS
Current maintainer: Ricardo SIGNES, <rjbs@cpan.org>. Original author: Adam Kennedy <cpan@ali.as>, <http://ali.as/> COPYRIGHT
Copyright (c) 2004 - 2005 Adam Kennedy. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of the license can be found in the LICENSE file included with this module. perl v5.12.4 2011-08-31 Email::Send::Test(3pm)
All times are GMT -4. The time now is 02:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy