-----BEGIN PGP SIGNED MESSAGE-----
On Tuesday, 2009-01-06 at 09:22 -0500, Anton Aylward wrote:
When I kill it, it restarts.
Maybe "ps afx | less" can show who is the parent.
BTDT - first thing I thought of.
Its PID is "1"
Then, you could do a grep on the entire disk (except your home and data)
to find the string.
How can I stop this?
At worst, you might remove its rpm.
Sort of like pulling at the tread on the jumper, what else gets unravelled?
Removing that leads to the deinstallation of NetworkManager and
NetworkManager-KDE. No doubt that will lead to other operational problems!
Don't use YaST to remove it: use rpm --nodeps. Hopefully, some program
will complain that some thing is missing. Who cares.
Or chmod the binary to not be executable.
Once I created an empty rpm to keep YaST from complaining that a
dependency had not been fulfilled. You could create instead a dummy
Any suggestions has to how I can make YAST actually
delete the entry?
How about manually deleting some file from the command line?
Yes, you can remove or rename the modem-manager file. Something else will
complain or crash, I suppose - and hope };-)
The ideal would be knowing what configuration can change that behavior,
but I have no idea. By making it crash, you might learn which app is
responsible, at least.
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org