Hi, today I applied the usual updates, some X updates and a new Liquorix kernel being the ones that stuck out.
Now, whenever I open a terminal I get the following message:
bash: /dev/cgroup/cpu/user/3282/tasks: No such file or directory
bash: /dev/cgroup/cpu/user/3282/notify_on_release: No such file or directory
Each time I open a terminal the number (3282) is different. It is a non-fatal error, I can continue to use the terminal without issues.
However, anyone know of a fix I can apply to get rid of these messages?
Thank you in advance,
Bill.
bash error on entering terminal.
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
LMDE 2 has reached end of support as of 1-1-2019
bash error on entering terminal.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: bash error on entering terminal.
Apparently it is to do with the "200 lines" patch to the kernel which improves latency.
The liquorix kernel update is likely the cause of this situation.
Any advice?
The liquorix kernel update is likely the cause of this situation.
Any advice?
Re: bash error on entering terminal.
i got same problem here, after i update my kernel to 2.6.38-2.dmz.2-liquorix-686.
This error appears when i started shell / terminal
The number was automatically generated. Anyone know how to remove this error message?
This error appears when i started shell / terminal
Code: Select all
bash: /dev/cgroup/cpu/user/17599/tasks: No such file or directory
bash: /dev/cgroup/cpu/user/17599/notify_on_release: No such file or directory
Re: bash error on entering terminal.
Same here!
(newest liquorix kernel)
NOTE:
"headcase" and I also have a similar problem in that "Mark all Upgrades" is missing now in Synaptic.
These issues must be related.
(newest liquorix kernel)
This error appears when i started shell / terminal
Code: Select all
bash: /dev/cgroup/cpu/user/17599/tasks: No such file or directory bash: /dev/cgroup/cpu/user/17599/notify_on_release: No such file or directory
NOTE:
"headcase" and I also have a similar problem in that "Mark all Upgrades" is missing now in Synaptic.
These issues must be related.
Re: bash error on entering terminal.
If you select the first, scroll down and shift+select the last , then right click you can mark all of them."headcase" and I also have a similar problem in that "Mark all Upgrades" is missing now in Synaptic.
These issues must be related.
Re: bash error on entering terminal.
Same problem + solution here:
http://forums.linuxmint.com/viewtopic.p ... 50#p408450
http://forums.linuxmint.com/viewtopic.p ... 50#p408450
Re: bash error on entering terminal.
The problem is with the so-called "200-line patch" to the kernel, which enables process groups called "cgroups". The Liquorix kernel includes this patch, and it also includes these lines in your /etc/bash.bashrc:
This is not really appropriate for the shared /etc/bash.bashrc file, which is shared by all users, because only root has access to write to /dev/cgroup.
Just comment those lines out, and you won't see the cgroup error.
Alan Porter
Code: Select all
if [ "$PS1" ] ; then
mkdir -p -m 0700 /dev/cgroup/cpu/user/$$ > /dev/null 2>&1
echo $$ > /dev/cgroup/cpu/user/$$/tasks
echo "1" > /dev/cgroup/cpu/user/$$/notify_on_release
fi
Just comment those lines out, and you won't see the cgroup error.
Alan Porter
Re: bash error on entering terminal.
Actually, the Liquorix kernel cannot use cgroups because it does not use the mainline process scheduler, CFS.
However, I need to make a decision soon to temporarily use CFS in the next kernel package because 2.6.39.4 came out recently and Greg Kroah marked this branch as end-of-life. I'll see what Con does over the next week and move forward if he does not port BFS to 3.0.
However, I need to make a decision soon to temporarily use CFS in the next kernel package because 2.6.39.4 came out recently and Greg Kroah marked this branch as end-of-life. I'll see what Con does over the next week and move forward if he does not port BFS to 3.0.