Wol wrote:
> On 01/09/2024 20:36, Dale wrote:
>> I wonder tho, in one of the replies, it says to create a directory in
>> /sys.  Don't those get cleared after a reboot?  I'm almost certain /proc
>> does but think /sys does too.  If so, how does that survive reboots?  I
>> may find more info as I search.
>
> I'll leave you to dig deeper, but let us know how it goes ... :-)
>
> Just about that /sys thing, that might be if you're trying to put an
> already-running program into a cgroup. If you're using cgexec to start
> a program, it should do all that for you.
>
> Cheers,
> Wol
>
>

I found this too. 


https://www.baeldung.com/linux/limit-resource-consumption


Then I figured out to install dev-libs/libcgroup and that got me a lot
of commands that makes cgroup work. 


/usr/bin/cgclassify
/usr/bin/cgcreate
/usr/bin/cgdelete
/usr/bin/cgexec
/usr/bin/cgget
/usr/bin/cgset
/usr/bin/cgsnapshot
/usr/bin/cgxget
/usr/bin/cgxset
/usr/bin/lscgroup
/usr/bin/lssubsys
/usr/sbin/cgconfigparser
/usr/sbin/cgrulesengd


I really like the cgcreate one.  That should start something.  o_O  I'm
wondering if I should have installed something else and it pull this
package in.   It is a lib which is usually a dependency of something
else.  I can't find anything else related tho.  Is this normal??

Based on some other info I found, it seems permissions is a common
problem people run into.  If I understand it correctly, I need to be a
user when I create and add things that I run as a user, not root.  I
notice most commands are in /bin too. 

I found another page I'd like to read but it has one of those page check
thingys and it just checks the page over and over and over and over and
over again.  Yea, I got tired of it too.  This is a linky. 

https://linux.die.net/man/1/cgexec

Since I can't see it, I bet it has some good info.  Isn't that they way
it works?  LOL 

This may not be as difficult as I thought.  You sharing the cgexec
command helped me to find a lot of info.  One even mentions Firefox
specifically. 

Thanks.

Dale

:-)  :-) 

Reply via email to