Running
where the file is on a known FAST file system would help isolate if the issue is in the send or the receive. Run the send, see how fast it is, then run receive off that file and see how fast that is.
Maybe some useful data points can be generated.
And there might even be some way to use a file and some standard utilities to duplicate the functionality of mbuffer. Maybe something as simple as starting the send to a file, waiting a few minutes, then starting the receive might work if the send always runs faster than the receive and the receive won't hit EOF before the send is done.
Requirements:
A server program should read a file and send the message to the client . if the file is not there, then switch to the receive part of the same program and receive any messages from the socket. If no messages to receive then switch to send part of the program to... (2 Replies)
Hi all,
First post!
I have just discovered that I can use unix to send mail to a mail address. I normally use entourage for my mail.
This unix mail is very intriguing to me, but something is not working... I tried the search, but could not find the answer...
This works:
(in terminal)... (1 Reply)
Hi,
One of the users in our company can send but not receive email. We are using SENDMAIL in conjunction with procmail. The funny thing is that all his sent email is in his /var/spool/mail but the email client does not pick anything up! He is using IMAP.
Anyone see have any ideas? (2 Replies)
Hello,
I need to create a script to monitor sent/received packets for a period of time (the period of time will be a users input) and write the result to some txt file.
Is there any command (don`t want to use any 3rd party sw) what I can use?
I`m using Solaris 10.
Thank you (14 Replies)
Hi All,
I am writing one script to automate one long process. In this process we need to upload some input files and download some output files. So , I want to automate this upload and download by using mail functionality.
I want to trigger this script when I am sending mail to server. I know... (0 Replies)
I have two servers, we'll call them sv1 and sv2.
both are Solaris 11.1 LDOMS running on a T4-4 with RBAC enabled.
my user has zfs allow send, receive on both servers and has ssh keys shared.
on sv2 (the destination) I have a zpool called zones that has no zfs fs built
on sv1 (the source) I... (5 Replies)
trying to clone a zfs file system on the same system using
zfs send -r root/branch@snapshot |zfs receive root/newbranch and get the following error :parent does not exist. How do I fix this? (1 Reply)
i have connected with my board through serial interface using minicom and i am running a bash script, which should test ethernet (ping test), USB read/write, RS232 ..
I have managed to test ethernet and USB read/write.
I test ethernet with ping.
I test USB read/write, using dd and verifying... (10 Replies)
Good morning everyone,
I'm looking for some help to retrieve data in a scenario where I might have made a big mistake. I'm hoping to understand what I did wrong.
My system is made of two Solaris 11 Express servers (old free version for evaluation). The first if for data and the second is... (7 Replies)
Discussion started by: rnd
7 Replies
LEARN ABOUT OPENSOLARIS
shutdown
shutdown(3XNET) X/Open Networking Services Library Functions shutdown(3XNET)NAME
shutdown - shut down socket send and receive operations
SYNOPSIS
cc [ flag ... ] file ... -lxnet [ library ... ]
#include <sys/socket.h>
int shutdown(int socket, int how);
DESCRIPTION
The shutdown() function disables subsequent send() and receive() operations on a socket, depending on the value of the how argument.
PARAMETERS
how Specifies the type of shutdown. The values are as follows:
SHUT_RD Disables further receive operations.
SHUT_WR Disables further send operations.
SHUT_RDWR Disables further send and receive operations.
socket Specifies the file descriptor of the socket.
RETURN VALUES
Upon successful completion, shutdown() returns 0. Otherwise, -1 is returned and errno is set to indicate the error.
ERRORS
The shutdown() function will fail if:
EBADF The socket argument is not a valid file descriptor.
EINVAL The how argument is invalid.
ENOTCONN The socket is not connected.
ENOTSOCK The socket argument does not refer to a socket.
The shutdown() function may fail if:
ENOBUFS Insufficient resources were available in the system to perform the operation.
ENOSR There were insufficient STREAMS resources available for the operation to complete.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
SEE ALSO getsockopt(3XNET), recv(3XNET), recvfrom(3XNET), recvmsg(3XNET), select(3C), send(3XNET), sendto(3XNET), setsockopt(3XNET), socket(3XNET),
attributes(5), standards(5)SunOS 5.11 10 Jun 2002 shutdown(3XNET)