Sponsored Content
Full Discussion: Free PP Allocation problem
Operating Systems AIX Free PP Allocation problem Post 302505783 by broonster on Thursday 17th of March 2011 05:34:31 PM
Old 03-17-2011
Quote:
Originally Posted by kah00na
. Since your "/var/vio/VMLibrary" is only on hdisk1, shrinking that filesystem size will only free PPs on hdisk1.
But isn't my /var/vio/VMLibrary spread over both disks, 449 LPs on hdisk0 and 147 LPs on hdisk1?
 

7 More Discussions You Might Find Interesting

1. SCO

Terminal Allocation Problem

Hello All, I am facing a problem on SCO Open Server V 5x, We are using serial communication on dumb terminals, right now i am facing a problem on some terminals, as they are not showing thier previous tty no, as tty13 or tty18, but they are showing ttya6 or ttya4, i also tried to move and link... (5 Replies)
Discussion started by: Awadhesh
5 Replies

2. Programming

Memory allocation problem

I have a program that will fetch some particular lines and store it in a buffer for further operations.The code which is given below works but with some errors.I couldn't trace out the error.Can anybody help on this plz?? #include <stdio.h> #include <stdlib.h> #include<string.h> #define... (1 Reply)
Discussion started by: vigneshinbox
1 Replies

3. Programming

Is there a problem with the memory allocation???

I have a scenario like the client has to search for the active server.There will be many servers.But not all server are active.And at a time not more than one server will be active. The client will be in active state always i.e, it should always search for an active server until it gets one.I... (1 Reply)
Discussion started by: vigneshinbox
1 Replies

4. Programming

dynamic allocation vs static allocation in c

i wrote a tiny version of tail command using a large buffer statically allocated but, in a second time, i found another version in which i use a bidimensional array dynamically allocated. here is the first version /*my tiny tail, it prints the last 5 line of a file */ #include<stdio.h>... (4 Replies)
Discussion started by: lucasclaus
4 Replies

5. Solaris

MountPoint / is 8% with 899.49MB free crossing threshold of 10% free

Hi, I have a problem one of the server file system cross the limitation MountPoint / is 8% with 899.49MB free crossing threshold of 10% free out put please help how to resolve this dev/vx/dsk/bootdg/rootvol 9.8G 8.8G 956M 91% / /devices ... (3 Replies)
Discussion started by: sriniva0
3 Replies

6. Solaris

Block-based allocation and Extent-based allocation in Solaris

Hi guys! Could you tell me what's this figure about? (See the attached figure below.) This is a representation of block allocation filesystem and extent allocation filesystem in Solaris. Does this mean that in a block-based allocation, data are placed in individual blocks while in... (0 Replies)
Discussion started by: arah
0 Replies

7. UNIX for Dummies Questions & Answers

Memory allocation problem

I am using ubuntu. I have written a program to calculate prime factors. it works perfectly fine till entered number is less than 9989 (or so ) but when one enters a number higher than that, for example 15000, it does not work. Can anyone guide me whats the problem ? although new codes are welcome,... (2 Replies)
Discussion started by: Abhishek_kumar
2 Replies
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)
All times are GMT -4. The time now is 01:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy