Carlos E. R. said the following on 01/06/2009 09:42 AM:
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.
I started with /etc and found nothing relevant.
Trying /usr/share/doc wasn't relevant either :-(
How can I stop
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-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.
Hm. Sounds better. At least that might give me some error logs that I
can trace back through ...
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 trouble is I can't pin one down.
The best I've found is one with the modem strings, but since the modem
isn't configured anyway the settings in there are all empty. Deleting
that didn't help.
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.
Makes sense, yes, but so far my 'hacking' (and guesswork-driven at
that!) hasn't hit on it. I was hoping someone who actually used dial-up
(I have cable the far side of my switch and firewall) might know.
Experience teaches only the teachable.
Aldous Huxley (1894 - 1963)
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org