[opensuse] How do I turn off the modem
I have /usr/sbin/modem-manager started from somewhere. I know not where and I know not why. I don't want it not be - I have no use for this damn winmodem anyway. When I kill it, it restarts. In Yast2 -> Network Devices -> Modem it seems to have recognised my intel card (ICH6 AC97) and I can't delete the modem entry. Yes, its also cluttering up the log files trying to open it and restart. I think its gumming up my sound function too. How can I stop this? (OBTW: this is 11.1 - it didn't happen with 11.0) -- The only freedom which deserves the name, is that of pursuing our own good in our own way, so long as we do not attempt to deprive others of theirs, or impede their efforts to obtain it. --John Stuart Mill (On Liberty, 1859) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2009-01-05 at 19:35 -0500, Anton Aylward wrote:
I have /usr/sbin/modem-manager started from somewhere. I know not where and I know not why. I don't want it not be - I have no use for this damn winmodem anyway. When I kill it, it restarts.
Maybe "ps afx | less" can show who is the parent.
How can I stop this?
At worst, you might remove its rpm. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkli1WMACgkQtTMYHG2NR9XWjACfQTF8y7cY2sCcjc1qJXN/ZhAo vQsAnA/Sk6xl7MtHBk0XoP+zwPJEBfKQ =1ixx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. said the following on 01/05/2009 10:51 PM:
On Monday, 2009-01-05 at 19:35 -0500, Anton Aylward wrote:
I have /usr/sbin/modem-manager started from somewhere. I know not where and I know not why. I don't want it not be - I have no use for this damn winmodem anyway. 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"
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! Any suggestions has to how I can make YAST actually delete the entry? How about manually deleting some file from the command line? -- "Quality is not a sprint; it is a long-distance event." Daniel Hunt. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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"
Too bad. 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 modem-manager.
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. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkljbdsACgkQtTMYHG2NR9U3aACfdhSmRAOilsimCxt3dhxjdPuK RDoAniXV8f9MADDX5D9kUoBnfSbyp7a/ =rh9B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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"
Too bad.
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 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.
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@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-01-06 at 10:05 -0500, Anton Aylward wrote:
Too bad.
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 :-(
I was thinking of binaries.
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 ...
Exactly.
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.
When I have to use a modem I use wvdial on an xterm. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkljdSkACgkQtTMYHG2NR9VhGwCbBLkt2k0HaCvAaenl3bYMQaNs gqcAn2mM7CX6QjvyhEzLaJ3aQx/6IrOb =iZE2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. said the following on 01/06/2009 10:13 AM:
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 :-(
I was thinking of binaries.
Them too. Every G&%-d#$%^&ed .jar file linked in to /etc/alternatives and under /usr/lib GRRRRRR!
When I have to use a modem I use wvdial on an xterm.
I suppose some people use a ppp daemon. -- The greatest obstacle to discovery is not ignorance - it is the illusion of knowledge -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-01-06 at 10:23 -0500, Anton Aylward wrote:
Carlos E. R. said the following on 01/06/2009 10:13 AM:
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 :-(
I was thinking of binaries.
Them too. Every G&%-d#$%^&ed .jar file linked in to /etc/alternatives and under /usr/lib
GRRRRRR!
Oh, my. I use "midnight commander", ie, 'mc', to do those searches. It might be slower, but it allows viewing the files later (or during the search).
When I have to use a modem I use wvdial on an xterm.
I suppose some people use a ppp daemon.
Ah, no thanks! I'm not that daring :-) Actually, wvdial calls pppd, I think, and it does a very clever choice of options as needed, and you get a working connection. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklj/DEACgkQtTMYHG2NR9UonACeMS+tJElA5tg2K5UJzqehRQtW bZAAnjCwyH3xTFz79nNnp1aiyIr9gKlC =WmCK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anton Aylward schreef:
Carlos E. R. said the following on 01/05/2009 10:51 PM:
On Monday, 2009-01-05 at 19:35 -0500, Anton Aylward wrote:
I have /usr/sbin/modem-manager started from somewhere. I know not where and I know not why. I don't want it not be - I have no use for this damn winmodem anyway. 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"
Just a guess : can /etc/inittab have someting to do with it (the pid being 1) ? -- Met vriendelijke groeten, Koenraad Lelong
Koenraad Lelong said the following on 01/07/2009 04:38 AM:
Anton Aylward schreef:
Carlos E. R. said the following on 01/05/2009 10:51 PM:
On Monday, 2009-01-05 at 19:35 -0500, Anton Aylward wrote:
I have /usr/sbin/modem-manager started from somewhere. I know not where and I know not why. I don't want it not be - I have no use for this damn winmodem anyway. 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"
Just a guess : can /etc/inittab have someting to do with it (the pid being 1) ?
That's a creative idea, but no. -- recursion (n): See recursion. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 06 January 2009 06:22, Anton Aylward wrote:
Carlos E. R. said the following on 01/05/2009 10:51 PM:
On Monday, 2009-01-05 at 19:35 -0500, Anton Aylward wrote:
I have /usr/sbin/modem-manager started from somewhere. I know not where and I know not why. I don't want it not be - I have no use for this damn winmodem anyway. 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"
Any process whose parent is I (init) was either started directly by init, was the result of a (or a chain of) exec call(s) by a process started by init or one whose actual (non-init) parent exited before its child (init inherits all processes when their parent process dies). (That's slightly inaccurate in that a process is created in exactly one way: the fork(2) system call. Any process may exec(2) another program and that program may do the same, and on and on, indefinitely. Such a chain of programs each in turn execute in the same process.)
...
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Anton Aylward -
Carlos E. R. -
Koenraad Lelong -
Randall R Schulz