[opensuse] Controlling zypper's Timedout when it is updating -- REPOST
When zypper is downloading upgrades in YaST2 (Online Update), a loss ofconnection to the internet can occur or some other hiccup where zypper either cannot connect to the URL or it cannot get the filename to download. When this occurs zypper sits around for seems like an eternity doing nothing and then announces that an error occurred; it expects a click of the mouse on the OK button after which another window comes up giving you the chance to Retry etc. In 99+% of cases simply clicking on Retry get zypper to get on with the job. This sitting around doing nothing is a PITA for 'hours' - and there is nothing that one can do except to wait until zypper decides to advise you that an error occurred. The ABORT button does not work so one just sits and waits. (Of course, there is always the drastic step of CTRL-ALT-ESC to exit zypper.) Somewhere there must be timer setting which controls how long zypper keeps trying to resume its task. Does anyone know where this setting is located so that the user can set the timeout period. Nothing I can see in zypper help and nothing shows up in /etc/zypp. Can anyone provide an answer, please? Ciao. -- Be nice to people on your way up - you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2008/11/25 14:30 (GMT+1100) Basil Chupin composed:
When zypper is downloading upgrades in YaST2 (Online Update), a loss ofconnection to the internet can occur or some other hiccup where zypper either cannot connect to the URL or it cannot get the filename to download.
When this occurs zypper sits around for seems like an eternity doing nothing and then announces that an error occurred; it expects a click of the mouse on the OK button after which another window comes up giving you the chance to Retry etc. In 99+% of cases simply clicking on Retry get zypper to get on with the job.
This sitting around doing nothing is a PITA for 'hours' - and there is nothing that one can do except to wait until zypper decides to advise you that an error occurred. The ABORT button does not work so one just sits and waits. (Of course, there is always the drastic step of CTRL-ALT-ESC to exit zypper.)
Somewhere there must be timer setting which controls how long zypper keeps trying to resume its task. Does anyone know where this setting is located so that the user can set the timeout period. Nothing I can see in zypper help and nothing shows up in /etc/zypp.
Can anyone provide an answer, please?
Dunno about 11.0. I've not run into the timeouts with it. In Factory, I run zypper from runlevel 3 as root. The timeouts happen _much_ more quickly there. If you're using download.opensuse.org for the standard repos, try switching to an alternate mirror for those, such as mirrors.kernel.org or gwdg.de. -- "Love is not easily angered. Love does not demand its own way." 1 Corinthians 13:5 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata wrote:
On 2008/11/25 14:30 (GMT+1100) Basil Chupin composed:
When zypper is downloading upgrades in YaST2 (Online Update), a loss ofconnection to the internet can occur or some other hiccup where zypper either cannot connect to the URL or it cannot get the filename to download.
When this occurs zypper sits around for seems like an eternity doing nothing and then announces that an error occurred; it expects a click of the mouse on the OK button after which another window comes up giving you the chance to Retry etc. In 99+% of cases simply clicking on Retry get zypper to get on with the job.
This sitting around doing nothing is a PITA for 'hours' - and there is nothing that one can do except to wait until zypper decides to advise you that an error occurred. The ABORT button does not work so one just sits and waits. (Of course, there is always the drastic step of CTRL-ALT-ESC to exit zypper.)
Somewhere there must be timer setting which controls how long zypper keeps trying to resume its task. Does anyone know where this setting is located so that the user can set the timeout period. Nothing I can see in zypper help and nothing shows up in /etc/zypp.
Can anyone provide an answer, please?
Dunno about 11.0. I've not run into the timeouts with it. In Factory, I run zypper from runlevel 3 as root. The timeouts happen _much_ more quickly there.
If you're using download.opensuse.org for the standard repos, try switching to an alternate mirror for those, such as mirrors.kernel.org or gwdg.de.
Thanks for this, but moving to some other source/mirror doesn't really solve the problem because if zypper strikes a problem with the download it will still "hang" for some prescribed period before announcing that there has been error. What I want to do is to reset the built-in timer from x minutes to something reasonable like 30 seconds or so because what has been happening in the past is that once zypper "wakes up" and comes up with the menu where one of the options is to Retry then doing so (Retry) will immediately download the file it was "hung" on. There has to be a control file where the timer for zypper is set and can, therefore, be altered -- but what is that control file? :-) Ciao. -- Be nice to people on your way up - you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I will add another zypper problem Also with "zypper dup" apparently openSuSE calls for "www.kernel.org" (which is a good site) and then zypper shows and error saying "URL not found" Basil Chupin wrote:
Felix Miata wrote:
On 2008/11/25 14:30 (GMT+1100) Basil Chupin composed:
When zypper is downloading upgrades in YaST2 (Online Update), a loss ofconnection to the internet can occur or some other hiccup where zypper either cannot connect to the URL or it cannot get the filename to download.
When this occurs zypper sits around for seems like an eternity doing nothing and then announces that an error occurred; it expects a click of the mouse on the OK button after which another window comes up giving you the chance to Retry etc. In 99+% of cases simply clicking on Retry get zypper to get on with the job.
This sitting around doing nothing is a PITA for 'hours' - and there is nothing that one can do except to wait until zypper decides to advise you that an error occurred. The ABORT button does not work so one just sits and waits. (Of course, there is always the drastic step of CTRL-ALT-ESC to exit zypper.)
Somewhere there must be timer setting which controls how long zypper keeps trying to resume its task. Does anyone know where this setting is located so that the user can set the timeout period. Nothing I can see in zypper help and nothing shows up in /etc/zypp.
Can anyone provide an answer, please?
Dunno about 11.0. I've not run into the timeouts with it. In Factory, I run zypper from runlevel 3 as root. The timeouts happen _much_ more quickly there.
If you're using download.opensuse.org for the standard repos, try switching to an alternate mirror for those, such as mirrors.kernel.org or gwdg.de.
Thanks for this, but moving to some other source/mirror doesn't really solve the problem because if zypper strikes a problem with the download it will still "hang" for some prescribed period before announcing that there has been error.
What I want to do is to reset the built-in timer from x minutes to something reasonable like 30 seconds or so because what has been happening in the past is that once zypper "wakes up" and comes up with the menu where one of the options is to Retry then doing so (Retry) will immediately download the file it was "hung" on.
There has to be a control file where the timer for zypper is set and can, therefore, be altered -- but what is that control file? :-)
Ciao.
- -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb@windstream.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb@arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkkst5sACgkQlSm9Y/Rhzd7X9ACfZN5oewLhD4yz/Q0ISXg/VLB8 43wAnjirq829/9dHgUCJKiN+0ELQ85fs =JvCl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2008/11/26 13:34 (GMT+1100) Basil Chupin composed:
Felix Miata wrote:
Dunno about 11.0. I've not run into the timeouts with it. In Factory, I run zypper from runlevel 3 as root. The timeouts happen _much_ more quickly there.
If you're using download.opensuse.org for the standard repos, try switching to an alternate mirror for those, such as mirrors.kernel.org or gwdg.de.
Thanks for this, but moving to some other source/mirror doesn't really solve the problem because if zypper strikes a problem with the download it will still "hang" for some prescribed period before announcing that there has been error.
What I was suggesting was a workaround for the problem of the openSUSE download redirector redirecting to servers that are missing files. When your repo configs specify one specific mirror that isn't missing files, you don't get the repeated timeouts. -- "Love is not easily angered. Love does not demand its own way." 1 Corinthians 13:5 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata wrote:
On 2008/11/26 13:34 (GMT+1100) Basil Chupin composed:
Felix Miata wrote:
Dunno about 11.0. I've not run into the timeouts with it. In Factory, I run zypper from runlevel 3 as root. The timeouts happen _much_ more quickly there.
If you're using download.opensuse.org for the standard repos, try switching to an alternate mirror for those, such as mirrors.kernel.org or gwdg.de.
Thanks for this, but moving to some other source/mirror doesn't really solve the problem because if zypper strikes a problem with the download it will still "hang" for some prescribed period before announcing that there has been error.
What I was suggesting was a workaround for the problem of the openSUSE download redirector redirecting to servers that are missing files. When your repo configs specify one specific mirror that isn't missing files, you don't get the repeated timeouts.
Yes, I understand this but I get disconnected from the Internet sometimes when zypper is doing upgrades so switching to different servers isn't going to solve my "problem". If I am downloading a file using Firefox and I get a glitch with my ISP I can continue with the download within seconds because I can Pause the download and then Resume as soon as the reconnection to my ISP occurs. There is no such capability using zypper but worse still zypper just remains in the "hung" state for ages before I am able to make it continue - which is why I want to alter its preconfigured timeout period. Ciao. -- Be nice to people on your way up - you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On the 25 November '08 I wrote (as a Reposted message): When zypper is downloading upgrades in YaST2 (Online Update), a loss of connection to the internet can occur, or some other hiccup, causing zypper not to complete the download. When this occurs zypper sits around for what seems like an eternity, doing nothing, and then announces that an error has occurred; it then expects some response from you and if you select Retry this gets (99.999% of the time) zypper to complete the download. This sitting around doing nothing "for hours" is a PITA - and there is nothing that one can do except to wait until zypper decides to advise you that an error has occurred. The ABORT button does not work so one just sits and waits. (Of course, there is always the drastic step of CTRL-ALT-ESC to exit zypper.) Somewhere there must be timer setting which controls how long zypper keeps trying to resume its task. Does anyone know where this setting is located so that the user can set the timeout period. Nothing I can see in zypper help and nothing shows up in /etc/zypp. Can anyone provide an answer, please? (I have posted this question twice now and while I did get several responses none provide the answer on where zypper's timeout timer is located and therefore can be reset to a lower figure.) Ciao. -- "With the portion of mankind that is above average one may speak of higher things; with those below it, one may not." Confucius -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Do you mean that your internet/networking shuts down by itself or that Zypper just freezes automatically by itself? "some other hiccup" is not very descriptive... Allen Zhu allen.jaloola@gmail.com G. Gordon Liddy - "Obviously crime pays, or there'd be no crime." On Fri, Jan 2, 2009 at 9:14 PM, Basil Chupin <blchupin@iinet.net.au> wrote:
On the 25 November '08 I wrote (as a Reposted message):
When zypper is downloading upgrades in YaST2 (Online Update), a loss of connection to the internet can occur, or some other hiccup, causing zypper not to complete the download.
When this occurs zypper sits around for what seems like an eternity, doing nothing, and then announces that an error has occurred; it then expects some response from you and if you select Retry this gets (99.999% of the time) zypper to complete the download.
This sitting around doing nothing "for hours" is a PITA - and there is nothing that one can do except to wait until zypper decides to advise you that an error has occurred.
The ABORT button does not work so one just sits and waits. (Of course, there is always the drastic step of CTRL-ALT-ESC to exit zypper.)
Somewhere there must be timer setting which controls how long zypper keeps trying to resume its task. Does anyone know where this setting is located so that the user can set the timeout period. Nothing I can see in zypper help and nothing shows up in /etc/zypp.
Can anyone provide an answer, please?
(I have posted this question twice now and while I did get several responses none provide the answer on where zypper's timeout timer is located and therefore can be reset to a lower figure.)
Ciao.
-- "With the portion of mankind that is above average one may speak of higher things; with those below it, one may not." Confucius
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-01-03 at 15:06 -0800, Allen Zhu wrote:
Do you mean that your internet/networking shuts down by itself or that Zypper just freezes automatically by itself?
For example, my adsl connection goes down now and then. It is my ISP fault, the copper lines, whatever. I can't do anything at all. It lasts for a minute, maybe less, maybe more... and i get a new external IP in the process. Telling zypper to retry works. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklf8twACgkQtTMYHG2NR9UYkQCgj/kIiwxbj8ZGWXdCTO1dSliO VukAn00oEcSgsmlP2Ojxghm4652qMACV =3Eln -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Yeah, what i'm saying is that is it a problem on your own side or is it zypper's? Allen Zhu allen.jaloola@gmail.com Eddie Izzard - "I grew up in Europe, where the history comes from." On Sat, Jan 3, 2009 at 3:20 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Saturday, 2009-01-03 at 15:06 -0800, Allen Zhu wrote:
Do you mean that your internet/networking shuts down by itself or that Zypper just freezes automatically by itself?
For example, my adsl connection goes down now and then. It is my ISP fault, the copper lines, whatever. I can't do anything at all. It lasts for a minute, maybe less, maybe more... and i get a new external IP in the process.
Telling zypper to retry works.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAklf8twACgkQtTMYHG2NR9UYkQCgj/kIiwxbj8ZGWXdCTO1dSliO VukAn00oEcSgsmlP2Ojxghm4652qMACV =3Eln -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Allen Zhu wrote:
Yeah, what i'm saying is that is it a problem on your own side or is it zypper's?
At this point in time *I* don't give a rat's because I have installed smart and will now use it; zypper, or whatever its side-kick is called, is now persona non grata on my system/s (in other words I've gone back to the future when "zypper" was a real PITA to use in openSUSE 10.3). Ciao. PS If you read my original post and the reposts I expect any reasonable person to conclude that the problem is not "on my side". -- "With the portion of mankind that is above average one may speak of higher things; with those below it, one may not." Confucius -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-01-03 at 19:01 -0800, Allen Zhu wrote:
Yeah, what i'm saying is that is it a problem on your own side or is it zypper's?
Both. There is a network problem, that affects some users, and zypper doesn't cope nicely with it. But notice that he talks of zypper and menus, so he is not using zypper. He is probably using YaST software module. Or rather, was, he had abandoned for smart, that has its own can of worms. The options to configure the different timeouts and retrying strategies zypper uses are unknown. Per Cristian's comment, you can configure the downloading behaviour in /root/.curlrc, but this is not even mentioned in zypper's man page. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklgmF4ACgkQtTMYHG2NR9WQ4wCfWHCXldWzD5wu7WsLzoSDaP/D tMcAn15XFV89+QRiVs+cxjGjx3X7STiY =QEhb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. escribió: Per Cristian's comment, you can configure the
downloading behaviour in /root/.curlrc, but this is not even mentioned in zypper's man page.
It is documented where it should , "man curl", zypper use libzypp that itself uses libcurl to access some remote resources like http and ftp, at startup, libcurl parses ~/.curlrc. So, this is neither a zypper nor libzypp feature, but a curl one :-) -- "We have art in order not to die of the truth" - Friedrich Nietzsche Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
Cristian Rodríguez wrote:
zypper use libzypp that itself uses libcurl
And that is documented _where_ in the manpage? There is a single mention of libcurl (together with perl and vi) but in a context that does not have to do with downloading. Regards nordi -- Spam protection: All mail to me that does not contain the string "suse" goes to /dev/null. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 04 January 2009 09:34:52 am nordi wrote:
Cristian Rodríguez wrote:
zypper use libzypp that itself uses libcurl
And that is documented _where_ in the manpage? There is a single mention of libcurl (together with perl and vi) but in a context that does not have to do with downloading.
When you have the error, it tells that curl can't download, find file etc. Also, there is few words on openSUSE wiki: http://en.opensuse.org/Libzypp/URI not really good sorted, but there is remark that it needs some work. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-01-04 at 11:52 -0300, Cristian Rodríguez wrote:
Carlos E. R. escribió: Per Cristian's comment, you can configure the
downloading behaviour in /root/.curlrc, but this is not even mentioned in zypper's man page.
It is documented where it should , "man curl", zypper use libzypp that itself uses libcurl to access some remote resources like http and ftp, at startup, libcurl parses ~/.curlrc.
So, this is neither a zypper nor libzypp feature, but a curl one :-)
A fact that you know because you are a dev, but not because you read it in the documentation. Zypper(8) doesn't mention that it uses libcurl to do the downloading, and even if we know that it does, there is no indication that it will read root's configuration file for curl, because normally a program reads configurations, and libraries are given the configuration by the caller program via function calls, I would assume. So no, this should be documented in zypper(8), not forgetting specifying whether it will accept all the configuration options in root's config file, or a subset. It is wrong to assume that even expert users will know all those details of a program, use their programs to their full potential, and be able to solve all problems in the manner designed by the designers. Devs know much more, its their job. And usually, devs are bad at documenting what they do. (and I'm not aiming this at you personally, mind, this is general) And, as has been commented that zypper now uses or will use aria2c or metalinks libs to do the downloading, I'm not sure if zypper in 11.1 still uses curl or not. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklg4k0ACgkQtTMYHG2NR9X+wgCggae/er5obkwhEpPU5Mpe4fo9 IrkAn2y38V2F+5fbhea3eJX6FTeT8/ui =s6uM -----END PGP SIGNATURE-----
Carlos E. R. escribió:
A fact that you know because you are a dev, but not because you read it in the documentation. Zypper(8) doesn't mention that it uses libcurl to do the downloading.
because zypper does not use libcurl to do the downloading.. :) it is libzypp that do,specifically, when MediaCurl interface is used, that depends on what kind of repository we are talking about.
And, as has been commented that zypper now uses or will use aria2c or metalinks libs to do the downloading, I'm not sure if zypper in 11.1 still uses curl or not.
libzypp uses libcurl unless ZYPP_ARIA2C environment variable is defined. -- "We have art in order not to die of the truth" - Friedrich Nietzsche Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-01-04 at 13:41 -0300, Cristian Rodríguez wrote:
Carlos E. R. escribió:
A fact that you know because you are a dev, but not because you read it in the documentation. Zypper(8) doesn't mention that it uses libcurl to do the downloading.
because zypper does not use libcurl to do the downloading.. :) it is libzypp that do,specifically, when MediaCurl interface is used, that depends on what kind of repository we are talking about.
Whatever :-) The fact remains that we users do not know what it uses to download and how can we adjust it, it is not documented what zyppers uses.
And, as has been commented that zypper now uses or will use aria2c or metalinks libs to do the downloading, I'm not sure if zypper in 11.1 still uses curl or not.
libzypp uses libcurl unless ZYPP_ARIA2C environment variable is defined.
One more little thing to note. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklhEOYACgkQtTMYHG2NR9VssACdHXo1ivNu7rii9Lw/0fTC/4hw 4zQAn2jNZ1zO62b2ovBTVyIzGDbKLxNr =ACYQ -----END PGP SIGNATURE-----
On Sunday 04 January 2009 10:41:39 am Cristian Rodríguez wrote:
Carlos E. R. escribió:
A fact that you know because you are a dev, but not because you read it in the documentation. Zypper(8) doesn't mention that it uses libcurl to do the downloading.
because zypper does not use libcurl to do the downloading.. :) it is libzypp that do,specifically, when MediaCurl interface is used, that depends on what kind of repository we are talking about.
And, as has been commented that zypper now uses or will use aria2c or metalinks libs to do the downloading, I'm not sure if zypper in 11.1 still uses curl or not.
libzypp uses libcurl unless ZYPP_ARIA2C environment variable is defined.
Can you help to update pages about: http://en.opensuse.org/Libzypp This one talks the most about curl. Is that the right one to explain how is libcurl used by libzypp? http://en.opensuse.org/Libzypp/URI -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin escribió:
Can anyone provide an answer, please?
echo "connect-timeout = number-of-seconds-you-want" >> /root/.curlrc -- "We have art in order not to die of the truth" - Friedrich Nietzsche Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
Cristian Rodríguez wrote:
Basil Chupin escribió:
Can anyone provide an answer, please?
echo "connect-timeout = number-of-seconds-you-want" >> /root/.curlrc
Thank you. I have created the .curlrc as per above and now await to test it the next time zypper "hangs" :-) - and will advise of the results. (If the above IS the workable solution then why can't this be made part of the zypper 'config'?) Ciao. -- "With the portion of mankind that is above average one may speak of higher things; with those below it, one may not." Confucius -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-01-03 at 17:10 +1100, Basil Chupin wrote:
Cristian Rodríguez wrote:
Basil Chupin escribió:
Can anyone provide an answer, please?
echo "connect-timeout = number-of-seconds-you-want" >> /root/.curlrc
Thank you.
I have created the .curlrc as per above and now await to test it the next time zypper "hangs" :-) - and will advise of the results.
(If the above IS the workable solution then why can't this be made part of the zypper 'config'?)
Notice that you are confusing zypper with YaST. You talk about clicking a button, selecting a menu... zypper doesn't have any of those, zypper is a command line utility. You are using "YOU", and the behaviour is slightly different. And I did open a Bugzilla about this problem, in zypper (not YaST). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklfHz4ACgkQtTMYHG2NR9XKpACggV7/do4fXyOFB1Y5Rm5mY5mF 0uMAoJPGKdSptW5cwrtw+2DTyDwJ/dwM =W+s0 -----END PGP SIGNATURE-----
Carlos E. R. wrote:
On Saturday, 2009-01-03 at 17:10 +1100, Basil Chupin wrote:
Cristian RodrÃguez wrote:
Basil Chupin escribió:
Can anyone provide an answer, please?
echo "connect-timeout = number-of-seconds-you-want" >> /root/.curlrc
Thank you.
I have created the .curlrc as per above and now await to test it the next time zypper "hangs" :-) - and will advise of the results.
(If the above IS the workable solution then why can't this be made part of the zypper 'config'?)
Notice that you are confusing zypper with YaST. You talk about clicking a button, selecting a menu... zypper doesn't have any of those, zypper is a command line utility. You are using "YOU", and the behaviour is slightly different.
And I did open a Bugzilla about this problem, in zypper (not YaST).
Thanks for your comment. I am absolutely fed up with "confusing" things when it comes to the applications used by oS to upgrade/update itself. I thought this sort of @#$* was done away with many months ago. Following your comment I have now installed the proper way of doing things on oS which is by using smart. Ciao. -- "With the portion of mankind that is above average one may speak of higher things; with those below it, one may not." Confucius -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 04 Jan 2009 18:54:19 +1100, you wrote:
Following your comment I have now installed the proper way of doing things on oS which is by using smart.
Which will trade one set of problems with another, so don't complain if you have problems. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Philipp Thomas wrote:
On Sun, 04 Jan 2009 18:54:19 +1100, you wrote:
Following your comment I have now installed the proper way of doing things on oS which is by using smart.
Which will trade one set of problems with another, so don't complain if you have problems.
Philipp
Nothing untoward has occurred since I switched over, therefore what cataclysmic and apocalyptic outcomes am I to expect by switching to smart? Ciao. -- "With the portion of mankind that is above average one may speak of higher things; with those below it, one may not." Confucius -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Basil Chupin <blchupin@iinet.net.au> [01-05-09 23:51]:
Nothing untoward has occurred since I switched over, therefore what cataclysmic and apocalyptic outcomes am I to expect by switching to smart?
The only problems I have noticed with smart is the need to watch architecture. It has a problem occasionally with trying to install 32 bit rpms as updates for 64 bit. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Patrick Shanahan wrote:
* Basil Chupin <blchupin@iinet.net.au> [01-05-09 23:51]:
Nothing untoward has occurred since I switched over, therefore what cataclysmic and apocalyptic outcomes am I to expect by switching to smart?
The only problems I have noticed with smart is the need to watch architecture. It has a problem occasionally with trying to install 32 bit rpms as updates for 64 bit.
Aha, many thanks for this Patrick. But it won't affect me because I do not have a 64-bit system. Ciao. -- "With the portion of mankind that is above average one may speak of higher things; with those below it, one may not." Confucius -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 05 January 2009 11:07:02 pm Basil Chupin wrote:
Patrick Shanahan wrote:
* Basil Chupin <blchupin@iinet.net.au> [01-05-09 23:51]:
Nothing untoward has occurred since I switched over, therefore what cataclysmic and apocalyptic outcomes am I to expect by switching to smart?
The only problems I have noticed with smart is the need to watch architecture. It has a problem occasionally with trying to install 32 bit rpms as updates for 64 bit.
Aha, many thanks for this Patrick.
But it won't affect me because I do not have a 64-bit system.
Did he mentioned "and vice versa" :-) Smart wasn't aware if architecture. You have chance to check is that fixed or not. Linux is about freedom of choice and everyone is free to choose his headache ;-) -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (10)
-
Allen Zhu -
Basil Chupin -
Carlos E. R. -
Cristian Rodríguez -
Donn Washburn -
Felix Miata -
nordi -
Patrick Shanahan -
Philipp Thomas -
Rajko M.