If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that:
can provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3.
My question is --> is there an equivalent to "cvai" in AIX 5.3 or something similar on the AIX 5.3 client side that provides the VIO Server and vhost # that the vscsi disk is mapped to ?
This User Gave Thanks to The Doctor For This Post:
I have identical scripts on two machines: one a laptop running Ubuntu 9.04, and the other a Windows XP desktop running Cygwin. The files I'd like to process are on the Windows machine. Running the script in Cygwin engages eight calls to an external executable and spins off who knows how many forks... (1 Reply)
Folks,
I am trying to solve the following problem. I have a process on machine A running as root that needs to mount and access an NFS partition being exported from machine B.
However, I cannot have 'no_root_squash' option given on B, hence I see NFS requests from machine A end up as 'nobody'... (1 Reply)
Hello,
I have a VIOS System and would like to do mapping some hdisks, hdisk160 until hdisk165 to a vSCSi Adapter. I try to do this in the oem_setup_env like the following:
for i in $(lspv | grep hdisk* | awk {'print $1'};
do
mkdev -V $i -p vhost20
done
There where a mapping with... (4 Replies)
I have several ssh servers *running aix 5.3 and they respond to sftp requests just fine, but I have one that requires clients to specify the path to the sftp server using the -s flag which is*/usr/sbin/sftp-server
I check the sshd_config across all servers and they are the same. *The other... (1 Reply)
When i tried to mount the nfs i see this error message
mount -t nfs 192.168.20.194:/remote/proj1 /nfsmount
mount: 192.168.20.194:/remote/proj1 failed, reason given by server: Permission denied
and the /etc/exports file in the host side looks like this
/remote/proj1 ... (12 Replies)
Hi guys,
I have two questions about acknowledgement in client side with JMS and AMQP:
1. what happens if we set CLIENT_ACKNOWLEDGE in producer side in JMS?
2. if basic.publish finishes executing and there is no exception thrown, this means message has been received in message server? or we... (0 Replies)
Hello,
When I assigned CDROM from IVM (VIOS) to LPAR and then running cfgmgr i get the following message on the client lpar
#cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed.
devices.vscsi.disk
searching... (0 Replies)
Hi everybody,
I have Power5 server with 4 internal hdisks each of 70Gb.
VIOS server was installed via Virtual I/O Server Image Repository on the HMC.
HMC release - 7.7.0
VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
LEARN ABOUT DEBIAN
roar_vs_file
roar_vs_file(3) RoarAudio Programmer's Manual roar_vs_file(3)NAME
roar_vs_file, roar_vs_file_simple, roar_vs_new_from_file - File mode for VS API
SYNOPSIS
#include <roaraudio.h>
int roar_vs_file(roar_vs_t * vss, struct roar_vio_calls * vio, int closefile, int * error);
int roar_vs_file_simple(roar_vs_t * vss, char * filename, int * error);
roar_vs_t * roar_vs_new_from_file(const char * server, const char * name, char * filename, int * error);
DESCRIPTION
These functions are used to open the VS object in file mode. In the file mode the VS API reads or writes the data from or to the file
itself. The file mode uses normal VIO/DSTR so it supports streams as well. Just pass the stream URL as filename.
roar_vs_file() sets up the file mode for a already opened object using the open VIO handle vio. This function requires the use of
roar_vs_stream(3).
roar_vs_file_simple() sets up the file mode using a given filename (or URL). It opens the file using DSTR API. By default the function
assumes playback mode and tries to auto detect the audio parameters. To override the auto detection or use a diffrent stream direction use
roar_vs_stream(3).
roar_vs_new_from_file() creates a new VS object and enters file mode using the file (or URL) given as filename.
To send data to or read data from use roar_vs_iterate(3) or roar_vs_run(3).
PARAMETERS
server The server to connect to. NULL for defaults.
name The application name. This should be something the user can use to identify the application. It MUST NOT be the application's
binary name or the value of argv[0].
vio The VIO handle to be used by the file mode.
closefile
This parameter tells the file mode if the file should be closed on roar_vio_close(3). Must be ROAR_VS_TRUE (common) or
ROAR_VS_FALSE.
filename
The filename used to open the file for file mode. The file is opend using DSTR API. All kinds of files supported by DSTR are sup-
ported. This includes HTTP streams.
error This is a pointer to a integer used to store the error value in case of error. This can be NULL if not used but it is very recom-
mended to use this error value to report good error messages to the user.
RETURN VALUE
On success roar_vs_new_from_file() return a new VS object. On error, NULL is returned. roar_vs_file() and roar_vs_file_simple() returns 0
on success and -1 on error.
EXAMPLES
roar_vs_t * vss;
int err;
vss = roar_vs_new_from_file(NULL, "MyApp", "http://...", &err);
if ( vss == NULL ) {
//handle error.
}
if ( roar_vs_run(vss, &err) == -1 ) {
//handle error.
}
if ( roar_vs_close(vss, ROAR_VS_FALSE, &err) == -1 ) {
//handle error.
}
SEE ALSO roar_vs_new_simple(3), roar_vs_iterate(3), roar_vs_run(3), roar_vs_close(3), roarvs(7), libroar(7), RoarAudio(7).
RoarAudio June 2011 roar_vs_file(3)