Can't run Linux after last patch

[hephasteus]

I'm not on linux now and can't remember the error but I went into system logger and it's spamming my audit file with unable to clone something something over and over like every second.

I think it's the same error that gave me a 20gb audit log during preview to release so don't want to run it right now.

[hephasteus]

Ok. The message i keep getting every 3 seconds is this.
not cloning cgroup for unused subsystem ns

The only thing i have found on that is a 9 month old kernel bug report that says it stops and starts when you stop and start visual editor proc?
Should i get back on linux and give that a go?

[stevea]

Next time you report a prblem - yo ushould include the details.

What release - F10 I assume
You said .... "spamming my audit file", but those message are NOT in an audit log. They are in the kernel dmesgs.

You waste a lot of time by using vague descriptions.

cgroups are a kernel means of creating a hierarchy of tasks/threads/processes. The message has already been removed from the kernel, but you won't see it till 2.6.28 unless Fedora adds a patch on some near-term kernel update. I suggest you bugzilla the problem which will increase the chance that a patch will appear in some kernel update.

[hephasteus]

Originally Posted by stevea

Next time you report a prblem - yo ushould include the details.

What release - F10 I assume
You said .... "spamming my audit file", but those message are NOT in an audit log. They are in the kernel dmesgs.

You waste a lot of time by using vague descriptions.

cgroups are a kernel means of creating a hierarchy of tasks/threads/processes. The message has already been removed from the kernel, but you won't see it till 2.6.28 unless Fedora adds a patch on some near-term kernel update. I suggest you bugzilla the problem which will increase the chance that a patch will appear in some kernel update.

Maybe i'm not being intentionally vague. Maybe I have no idea what cgroups are and maybe there's no information on the net about what they are. Maybe kernel dmesgs messages show up in the audit log under the audit log viewer. I'm not on linux right now but If I remember right looking through the log some kernels spam them and DON'T spam them depending on versions of other things. I'll poke around bugzilla. Thank you very much for the information and knowledge I needed stevea!!!

I'm back on windoze. I searched system thoroughly. It started december 21 with a pulse not responding and a spawn on libcanbera x86_64 that timed out. I can't figure out how to enter a new bug into system without a crash or a selinux violation. Even if i could I can't copy and paste from the log viewer and would have to open them in an editor to do it. My archive 1 log is 20mb and my recent log is at 14 megabytes growing to 15 megabytes while I was trying to bug report it. Every bug in the system doesn't bring in all the players in the problem. I think I could make a very good bug report on this if the system would allow it.