Hello, guys !
Long time no seen. I have a question about Linux web servers. I guess it is a more general question, but in my case it is a Linux web server. I want to know how much RAM memory should I put on my servers. Do you have some formula or guidelines on how should I calculate the amount... (1 Reply)
hi,
currently we have SAP application running on a solaris machine that has 8 dual core CPUs @ 2.4 GHZ and the performance of the system is perfectly normal. We plan to migrate the app to a suse linux VM image on a vmware box now. So my questions are:
1) Should i size the linux image to... (2 Replies)
We have a system with 4 Xeon Processors each with 10 cores, total 512 GB RAM and 10 TB Hard Drive.
we want to create multiple user accounts with different resource limitations as :
User 1: RAM : 50GB, PROCESSOR: 10 Cores , User folder in home directory of 10GB space.
User 2: RAM :... (5 Replies)
Hi,
I will be creating a process myself and I want to know the average CPU and RAM used by the process over the lifetime of the process. I see that there are various tools available(pidstat) for doing , I was wondering if it possible to do it in a single command while creation.
Thanks in... (3 Replies)
Hi
i have 2 esxi. one is amd based cpu and the other is intel based cpu.
i have a redhat linux machine that was created in amd cpu esxi, now i need to migrate it (powered off) to INTEL based esxi. will the redhat machine will be OK with that?
Thanks (2 Replies)
Discussion started by: guy3145
2 Replies
LEARN ABOUT DEBIAN
bplay
BPLAY(1) General Commands Manual BPLAY(1)NAME
bplay, brec - buffered sound recording/playing
SYNOPSIS
bplay [-d device] [-B buffersize] [-S] [-s speed] [-b bits] [[-t secs] | [-T samples]] [[-j secs] | [-J samples]] [-D level] [file]
brec [-d device] [-B buffersize] [-S] [-s speed] [-b bits] [[-t secs] | [-T samples]] [-r|-v|-w] [-D level] [file]
DESCRIPTION
bplay copies data from the named sound file (or the standard input if no filename is given) to the audio device.
brec copies data from the audio device to the named sound file (or the standard output if no filename is present).
These programs are intended to be drop-in replacements for the vplay and vrec programs by Michael Beck (beck@informatik.hu-berlin.de).
OPTIONS
-B buffersize
Use the supplied audio buffer size instead of the default.
-d device
Use the supplied audio device instead of the default.
-S Sound file is stereo.
-s speed
The speed in samples per second.
-b bits
The number of bits per sample. Only 8 and 16 are currently supported.
-t secs
The number of seconds to be played or recorded.
-T samples
The number of samples to be played or recorded.
-j secs
When playing, the number of seconds to skip at the beginning of the input before playing.
-J samples
When playing, the number of samples to skip at the beginning of the input before playing.
-r When recording, write raw sound file.
-v When recording, write Creative Labs VOC sound file.
-w When recording write Microsoft Wave sound file. Note that the WAVE file format is limited to 4GiB filesize. Recording more data is
possible, but the length info won't be consistent.
-q Quiet mode. No messages are displayed.
-D level
Print debug information to stderr. Debug level ranges from 0 to 2, where 0 is no debug information.
FILES
/dev/dsp The audio device.
BUGS
The -t, -T, -j and -J options may do strange things when playing VOC files.
There are limitations on recording VOC format files - specifically VOC files are only recorded in the 1.20 version of the format, which
some player programs may choke on. There is also currently a limit of around 16M on the size of a VOC file which will be recorded. This is
probably not a problem since I don't think anybody really uses VOC files anymore.
This program prefers to run setuid root. This is because it wants to use setpriority() to run at the highest possible priority, and also
locks down the buffers it uses to avoid them being swapped out.
AUTHOR
David Monro (davidm@amberdata.demon.co.uk or davidm@cs.usyd.edu.au)
The option parsing code was originally taken from vplay to maintain compatibility.
20 September 1999 BPLAY(1)