Hi,
I just noticed that I have over 100 processes running in the sandbox_web_client_t domain, although I closed all my sandbox windows.
ps auxZ|grep sandbox_web_client_t|grep -c /usr/libexec/gvfsd 52
ps auxZ|grep sandbox_web_client_t|grep -c '/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session' 51
Shouldn't they be killed after I closed all sandbox windows?
Kind regards, Christoph
On Thu, Aug 19, 2010 at 12:32 PM, Christoph A. casmls@gmail.com wrote:
Hi,
I just noticed that I have over 100 processes running in the sandbox_web_client_t domain, although I closed all my sandbox windows.
ps auxZ|grep sandbox_web_client_t|grep -c /usr/libexec/gvfsd 52
ps auxZ|grep sandbox_web_client_t|grep -c '/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session' 51
Shouldn't they be killed after I closed all sandbox windows?
Kind regards, Christoph
I see this too.
Could pulseaudio not be shutting down gracefully? Just a guess....
tom
On Thu, 2010-08-19 at 13:38 -0700, Tom London wrote:
On Thu, Aug 19, 2010 at 12:32 PM, Christoph A. casmls@gmail.com wrote:
Hi,
I just noticed that I have over 100 processes running in the sandbox_web_client_t domain, although I closed all my sandbox windows.
ps auxZ|grep sandbox_web_client_t|grep -c /usr/libexec/gvfsd 52
ps auxZ|grep sandbox_web_client_t|grep -c '/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session' 51
Shouldn't they be killed after I closed all sandbox windows?
Kind regards, Christoph
I see this too.
Could pulseaudio not be shutting down gracefully? Just a guess....
tom
I don't believe this has anything to do with the sandbox. I am getting similar problems at home on F13 when I use xming to do x forwarding between my Windows and Linux machines. I was using it on virt-manager on that machine and was still having the problems.
Dave
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 08/19/2010 04:48 PM, David P. Quigley wrote:
On Thu, 2010-08-19 at 13:38 -0700, Tom London wrote:
On Thu, Aug 19, 2010 at 12:32 PM, Christoph A. casmls@gmail.com wrote:
Hi,
I just noticed that I have over 100 processes running in the sandbox_web_client_t domain, although I closed all my sandbox windows.
ps auxZ|grep sandbox_web_client_t|grep -c /usr/libexec/gvfsd 52
ps auxZ|grep sandbox_web_client_t|grep -c '/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session' 51
Shouldn't they be killed after I closed all sandbox windows?
Kind regards, Christoph
I see this too.
Could pulseaudio not be shutting down gracefully? Just a guess....
tom
I don't believe this has anything to do with the sandbox. I am getting similar problems at home on F13 when I use xming to do x forwarding between my Windows and Linux machines. I was using it on virt-manager on that machine and was still having the problems.
Dave
-- selinux mailing list selinux@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/selinux
I wish there was a way to setup a different cgroup for each sandbox. then we could do a killall on the cgroup.
On 08/21/2010 01:23 PM, Daniel J Walsh wrote:
On 08/19/2010 04:48 PM, David P. Quigley wrote:
On Thu, 2010-08-19 at 13:38 -0700, Tom London wrote:
On Thu, Aug 19, 2010 at 12:32 PM, Christoph A. casmls@gmail.com wrote:
Hi,
I just noticed that I have over 100 processes running in the sandbox_web_client_t domain, although I closed all my sandbox windows.
ps auxZ|grep sandbox_web_client_t|grep -c /usr/libexec/gvfsd 52
ps auxZ|grep sandbox_web_client_t|grep -c '/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session' 51
Shouldn't they be killed after I closed all sandbox windows?
Kind regards, Christoph
I see this too.
Could pulseaudio not be shutting down gracefully? Just a guess....
tom
I don't believe this has anything to do with the sandbox. I am getting similar problems at home on F13 when I use xming to do x forwarding between my Windows and Linux machines. I was using it on virt-manager on that machine and was still having the problems.
Dave
-- selinux mailing list selinux@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/selinux
I wish there was a way to setup a different cgroup for each sandbox. then we could do a killall on the cgroup.
I am not sure but could cgexec (man cgexec) help here? That is how initrc puts services in a defined cgroup.
-- selinux mailing list selinux@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/selinux
On 08/21/2010 01:23 PM, Daniel J Walsh wrote:
I wish there was a way to setup a different cgroup for each sandbox. then we could do a killall on the cgroup.
Is it ok if I file the bugreport against policycoreutils-python, or is this issue not sandbox specific?
kind regards, Christoph
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 08/21/2010 04:40 PM, Christoph A. wrote:
On 08/21/2010 01:23 PM, Daniel J Walsh wrote:
I wish there was a way to setup a different cgroup for each sandbox. then we could do a killall on the cgroup.
Is it ok if I file the bugreport against policycoreutils-python, or is this issue not sandbox specific?
kind regards, Christoph
-- selinux mailing list selinux@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/selinux
You can file it against policycoreutils.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Christoph A. wrote:
Hi,
I just noticed that I have over 100 processes running in the sandbox_web_client_t domain, although I closed all my sandbox windows.
ps auxZ|grep sandbox_web_client_t|grep -c /usr/libexec/gvfsd 52
ps auxZ|grep sandbox_web_client_t|grep -c '/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session' 51
Shouldn't they be killed after I closed all sandbox windows?
Same problem with these processes:
/usr/bin/pulseaudio --start --log-target=syslog /usr/libexec/pulse/gconf-helper
(running in sandbox_web_client_t)
I have lots of them.. Christoph
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/16/2011 05:10 PM, Christoph A. wrote:
Christoph A. wrote:
Hi,
I just noticed that I have over 100 processes running in the sandbox_web_client_t domain, although I closed all my sandbox windows.
ps auxZ|grep sandbox_web_client_t|grep -c /usr/libexec/gvfsd 52
ps auxZ|grep sandbox_web_client_t|grep -c '/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session' 51
Shouldn't they be killed after I closed all sandbox windows?
Same problem with these processes:
/usr/bin/pulseaudio --start --log-target=syslog /usr/libexec/pulse/gconf-helper
(running in sandbox_web_client_t)
I have lots of them.. Christoph
- -- selinux mailing list selinux@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/selinux
Please open a bug with policycoreutils including version of packages.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Daniel J Walsh wrote:
Please open a bug with policycoreutils including version of packages.
https://bugzilla.redhat.com/show_bug.cgi?id=714152
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Christoph A. wrote:
Daniel J Walsh wrote:
Please open a bug with policycoreutils including version of packages.
https://admin.fedoraproject.org/updates/policycoreutils-2.0.85-30.1.fc14
Status: pending Requested: testing Pushed: False Date Submitted: 2011-06-17 17:21:15
Seams to take a while. I thought updates are pushed to testing once a day..
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/20/2011 06:48 AM, Christoph A. wrote:
Christoph A. wrote:
Daniel J Walsh wrote:
Please open a bug with policycoreutils including version of packages.
https://admin.fedoraproject.org/updates/policycoreutils-2.0.85-30.1.fc14
Status: pending Requested: testing Pushed: False Date Submitted: 2011-06-17 17:21:15
Seams to take a while. I thought updates are pushed to testing once a day..
- -- selinux mailing list selinux@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/selinux
No a Human has to push it. So It is somewhat arbitrary.
selinux@lists.fedoraproject.org
-
Christoph A. -
Daniel J Walsh -
David P. Quigley -
Dominick Grift -
Tom London