-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
By default, SuSEwatcher is configured for a dialup network. Through some
searching I found that the config file is located at
$HOME/.kde/share/config/susewatcherrc
While I was successful in changing network from dialup to lan, I was
wondering if there is a more appropriate place to set its configuration.
I looked through YaST and the KDE control panel and the only place I
found was the susewatcherrc file.
- --
Jerry Feldman
On Sunday 28 September 2003 09:29 am, Jerry Feldman wrote:
By default, SuSEwatcher is configured for a dialup network. Through some searching I found that the config file is located at $HOME/.kde/share/config/susewatcherrc
While I was successful in changing network from dialup to lan, I was wondering if there is a more appropriate place to set its configuration. I looked through YaST and the KDE control panel and the only place I found was the susewatcherrc file.
-- Jerry Feldman
==============
Jerry, If you have any luck getting it to stay on something else, let me know. Each time I tried changing it from dialup to network or cable connection, it resorted back to dialup. As far as I know, that is the only configuration file. There seems to be no documentation on the program and SuSE never responded to my questions about documentation or config files. Lee -- --- KMail v1.5.4 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 28 Sep 2003 11:57:33 -0400
BandiPat
On Sunday 28 September 2003 09:29 am, Jerry Feldman wrote:
By default, SuSEwatcher is configured for a dialup network. Through some searching I found that the config file is located at $HOME/.kde/share/config/susewatcherrc
While I was successful in changing network from dialup to lan, I was wondering if there is a more appropriate place to set its configuration. I looked through YaST and the KDE control panel and the only place I found was the susewatcherrc file.
-- Jerry Feldman
============== Jerry, If you have any luck getting it to stay on something else, let me know. Each time I tried changing it from dialup to network or cable connection, it resorted back to dialup. As far as I know, that is the
only configuration file. There seems to be no documentation on the program and SuSE never responded to my questions about documentation or config files. Here is my susewatcherrc: [General] FirstStart=false
[UpdateMessages]
LastChecked=2003,9,20,16,44,30
[YouWatcher]
CheckEnabled=true
LastCheckDate=2003,9,25,8,17,46
LastCheckResult=0
network=lan
[nBbg.hiesiyGZ943]
/dev/hda1=true
/dev/hda8=true
/dev/hda9=true
Try setting network=lan then resrtart it (or just logout and log in). It
seems to work.
- --
Jerry Feldman
On Sunday 28 September 2003 02:56 pm, Jerry Feldman wrote: [...]
==============
Jerry, If you have any luck getting it to stay on something else, let me know. Each time I tried changing it from dialup to network or cable connection, it resorted back to dialup. As far as I know, that is the
only configuration file. There seems to be no documentation on the program and SuSE never responded to my questions about documentation or config files.
Here is my susewatcherrc: [General] FirstStart=false
[UpdateMessages] LastChecked=2003,9,20,16,44,30
[YouWatcher] CheckEnabled=true LastCheckDate=2003,9,25,8,17,46 LastCheckResult=0 network=lan
[nBbg.hiesiyGZ943] /dev/hda1=true /dev/hda8=true /dev/hda9=true
Try setting network=lan then resrtart it (or just logout and log in). It seems to work. --
Thanks Jerry, Tried it and still didn't take. I suppose it's because I have a modem setup on the machine, I am not sure why it always resorts back to dialup. Either network=direct (for cable modem or dsl) should work or the network=lan should work and it actually does, in a manner of speaking. It will use the direct connection to do it's checking, when you ask it too, but it won't do the automatic checking because you are not connected via a modem (dialup). Maybe some clarification on the program will show up sometime in the future. For now, I'll do it the old fashion way and start the YOU up manually. Lee -- --- KMail v1.5.4 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 29 Sep 2003 00:58:40 -0400
BandiPat
Thanks Jerry, Tried it and still didn't take. I suppose it's because I have a modem
setup on the machine, I am not sure why it always resorts back to dialup. Either network=direct (for cable modem or dsl) should work or
the network=lan should work and it actually does, in a manner of speaking. It will use the direct connection to do it's checking, when
you ask it too, but it won't do the automatic checking because you are
not connected via a modem (dialup).
Maybe some clarification on the program will show up sometime in the future. For now, I'll do it the old fashion way and start the YOU up manually. One thing I did not mention is that you cannot have SuSEWatcher running when you update the file. Kelly's solution is to log out of KDE (which will stop SuSEWatcher), edit the file while in the console window, go back to KDM (CTRL-ALT-F7), then log back in. The problem is that if SuSEWatcher is running while you edit the file, it will overwrite your changes.
Another solution would be to switch to run level 3, edit the file,
switch back to run level 5 and relog in.
- --
Jerry Feldman
On Monday 29 September 2003 08:20 am, Jerry Feldman wrote: [...]
One thing I did not mention is that you cannot have SuSEWatcher running when you update the file. Kelly's solution is to log out of KDE (which will stop SuSEWatcher), edit the file while in the console window, go back to KDM (CTRL-ALT-F7), then log back in. The problem is that if SuSEWatcher is running while you edit the file, it will overwrite your changes.
Another solution would be to switch to run level 3, edit the file, switch back to run level 5 and relog in.
-- Jerry Feldman
=============
Thanks again Jerry for the hints and I wish they would work! ;o) I have already done what you and Kelly have mentioned. I always close SuSEwatcher down prior to changing the config file. It never fails to change it back though. In fact, once I click "check for updates", it immediately changes to dialup after checking. Of course, if you quit it at that point, it saves the changes to the config file. I am thinking there is another config file somewhere, we don't know about or having a modem configured throws it off and it defaults to that. Regards Lee -- --- KMail v1.5.4 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
On Sunday 28 September 2003 10:57, BandiPat wrote:
Jerry, If you have any luck getting it to stay on something else, let me know. Each time I tried changing it from dialup to network or cable connection, it resorted back to dialup. As far as I know, that is the only configuration file. There seems to be no documentation on the program and SuSE never responded to my questions about documentation or config files.
Lee
I believe that it has been determined that the best way to change it is to logout of KDE, change to a console windows <ctrl><alt><F1> and login as yourself. Then modify the file with a console editing tool (i.e. Vim, Emacs, etc.). Logout from the console window and change back to the KDM login console <ctrl><alt><F7> and login. All should be well. -- Kelly L. Fulks Home Account near Huntsville, AL
participants (3)
-
BandiPat
-
Jerry Feldman
-
Kelly Fulks