01-22-2004
Is it wrong to say that Vax is the little brother of UNIX?
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
please help, any VMS sites you know of to learn this operating system?? (3 Replies)
Discussion started by: TRUEST
3 Replies
2. UNIX for Advanced & Expert Users
How to remotely execute a script (.COM ) on a VMS system ?
rsh ?
Thanks in advance (1 Reply)
Discussion started by: ivancleber
1 Replies
3. Linux
Hi
I'm using a Linux machine (CENTOS 5) to ftp a file from a VMS Alpha box (i hardly know anything about these machines). All seems to be working upto the point where it states the transfer has started but it just hangs...
ftp> get SPOOL.28
local: SPOOL.28 remote: SPOOL.28
200 Port 228.87... (2 Replies)
Discussion started by: rizla65
2 Replies
4. UNIX for Dummies Questions & Answers
All
I am a VMS guy just learning UNIX.
My first task is to SFTP files from VMS to UNIX in BATCHMODE without having to enter a password. Note that using SFTP interactively works just fine.
I have followed some specific instructions provided by a vendor with no success. I have also read... (0 Replies)
Discussion started by: randyhouse
0 Replies
5. Virtualization and Cloud Computing
Hi,
I have an existing linux server hosting some vservers. In addition, a VMware ESX is in place.
My goal is to get rid of the linux-vserver system and migrate each vserver on the ESX properly.
Is that possible ?
Thanks for your help.
Fiss (0 Replies)
Discussion started by: fiss
0 Replies
6. Emergency UNIX and Linux Support
Hello,
I am running into this issues, few VMWare VM's that are running with RHEL 5.6 and Centos 5.7, are having read write errors on the root file system. This is noticed on all vm's. After looking to log files this what I noticed.
#touch test.txt
touch: cannot touch `test.txt': Read-only... (12 Replies)
Discussion started by: bobby320
12 Replies
7. Solaris
Hi all,
We're been having issues with quite a few Solaris 10 VMs hanging after about a week of uptime. These VMs are running on VMware ESXi 4.1 U1 hosts and the issue does not occur on any specific host. We also running CentOS VMs and are not experiencing any issues with those VMs. The VMs that... (5 Replies)
Discussion started by: derekivey
5 Replies
8. HP-UX
Hello,
I am looking into HP-UX 11.31 VMs and I had a few questions.
We own two systems with 11.31 installed on them:
HP 9000 rp3440 (RISC)
- 2gb memory
- 2 processors
HP Integrity rx2660 (Itanium)
- 8gb memory
- 4 processors
Looking at the memory requirements in the Integrity VM... (4 Replies)
Discussion started by: bstring
4 Replies
9. Solaris
I've been given an IP address to assign to an ldom that is in a different subnet than the host, and I am looking for assistance in getting it online. I believe I need "VLAN tagging" as found in this link, but I do not understand all of the terminology.
My host machine is on subnet 10.25.112.x,... (1 Reply)
Discussion started by: bstring
1 Replies
LEARN ABOUT DEBIAN
io_pipe
io_pipe(3) Library Functions Manual io_pipe(3)
NAME
io_pipe - create a Unix pipe
SYNTAX
#include <io.h>
int io_pipe(int64 pfd[2]);
DESCRIPTION
io_pipe creates a new UNIX ``pipe.'' The pipe can receive data and provide data; any bytes written to the pipe can then be read from the
pipe in the same order.
A pipe is typically stored in an 8192-byte memory buffer; the exact number depends on the UNIX kernel. Bytes are written to the end of the
buffer and read from the beginning of the buffer. Once a byte has been read, it is eliminated from the buffer, making space for another
byte to be written; readers cannot ``rewind'' a pipe to read old data. Once 8192 bytes have been written to the buffer, the pipe will not
be ready for further writing until some of the bytes have been read. Once all the bytes written have been read, the pipe will not be ready
for further reading until more bytes are written.
io_pipe sets d[0] to the number of a new descriptor reading from the pipe, and sets d[1] to the number of a new descriptor writing to the
pipe. It then returns 1 to indicate success. If something goes wrong, io_pipe returns 0, setting errno to indicate the error; in this case
it frees any memory that it allocated for the new pipe, and it leaves d alone.
SEE ALSO
io_readfile(3), io_createfile(3), io_socketpair(3)
io_pipe(3)