Use of Capabilities Post: 302596888

Sponsored Content

Top Forums UNIX for Advanced & Expert Users Use of Capabilities Post 302596888 by MikeGM on Wednesday 8th of February 2012 01:33:09 PM

02-08-2012

Registered User

Thanks Corona,

The system normally has about 180 processes active but despite this the processor utilisation rarely exceeds 30% to 40% of which rhythmbox is only a few percent. Rhythmbox works except that every 30 seconds to one minute the sound "glitches".

I have spent a considerable amount of time eliminating/fixing other issues with it and am now left with this residue of infrequent glitches. My current working hypothesis is that occasionally the demands of some other process briefly blocks rhythmbox from the processor causing a buffer underrun. This hypothesis is supported by the fact that on the significantly more powerful processor there is no glitching.

On the basis that the processing demands of Rhythmbox are slight and that it's probably the most time-critical application running, I thought it might be instructive to see what a higher priority might achieve.

tldnr; I'm not really using it as a go faster button, I'm hoping it will be a latency reduction mechanism.

MikeGM

View Public Profile for MikeGM

Find all posts by MikeGM

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix Capabilities?

We are looking into buying a new software, billing software that is, and want to know if you can run that on the same UNIX server as another major software? Is there a limit to the different types of software Unix can run, or is it like windows where you can install as many as you like? ...

2. UNIX for Advanced & Expert Users

p570 Capabilities

Hi there. I've been tasked with making a new design for our Unix systems :eek: Now the question I have is; How many LPARs can a p570 hold WITHOUT using a VIO Server. Many Thanks Kees

3. Red Hat

Adding capabilities to an RPM

Hi. I downloaded a package that could only be installed on RHEL5, and not 4 or 3, so I got the source in order to compile it on RHEL 3 so hopefully it will work on all versions. So I have the source for a working package, but when I build it in RHEL 3 and then try to install it in RHEL 5, it...

4. SCO

Slow Processing - not matching hardware capabilities

I have been a SCO UNIX user, never an administrator...so I am stumbling around looking for information. I don't know too much about what is onboard in terms of hardware, however; I will try my best. We have SCO 5.07 and have applied MP5. We have a quad core processor with 4 250 GB...

5. UNIX for Advanced & Expert Users

Linux capabilities discussion

Hi I'm trying to compile my linux kernel with CONFIG_SECURITY_CAPABILITIES=y. any idea what this thing does ?? Also another question , If I compile the kernel that I'm currently using , what'll happen ? ~cheers

6. UNIX for Advanced & Expert Users

CentOS7 restoring file capabilities

Quite an obscure question I think. We have a rebuild process for remote sites that allows us to PXE rebuild a till (actually a PC with a touch screen and various fancy bits) running CentOS. The current CentOS5 tills work just fine with a tar image restore and some personalisation. Sadly,...

LEARN ABOUT REDHAT

nice

NICE(2) 						     Linux Programmer's Manual							   NICE(2)

NAME

       nice - change process priority

SYNOPSIS

       #include <unistd.h>

       int nice(int inc);

DESCRIPTION

       nice adds inc to the nice value for the calling pid.  (A large nice value means a low priority.)  Only the superuser may specify a negative
       increment, or priority increase.

RETURN VALUE

       On success, zero is returned.  On error, -1 is returned, and errno is set appropriately.

ERRORS

       EPERM  A non-super user attempts to do a priority increase by supplying a negative inc.

CONFORMING TO

       SVr4, SVID EXT, AT&T, X/OPEN, BSD 4.3. However, the Linux and glibc (earlier than glibc 2.2.4) return  value  is  nonstandard,  see  below.
       SVr4 documents an additional EINVAL error code.

NOTES

       Note  that  the routine is documented in SUSv2 to return the new nice value, while the Linux syscall and (g)libc (earlier than glibc 2.2.4)
       routines return 0 on success.  The new nice value can be found using getpriority(2).  Note that an implementation in which nice returns the
       new  nice  value  can  legitimately  return -1.	To reliably detect an error, set errno to 0 before the call, and check its value when nice
       returns -1.

SEE ALSO

       nice(1), getpriority(2), setpriority(2), fork(2), renice(8)

Linux								    2001-06-04								   NICE(2)