I have a sles11sp2 (oes11sp1) box that has a fairly slow connection to
my SMT box compared to my other servers. Is there a way I can get the
updates to download without installing and I can install them at a
different time?
I’d like to have the updates downloaded to that server ahead of time,
then I can install them first thing in the morning before anyone at
this location logs in.
–
Stevo
Good question, and I think this related thread has the answer:
https://forums.suse.com/showthread.php?3418-Zypper-command
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
ab sounds like they ‘said’:
[color=blue]
Good question, and I think this related thread has the answer:
https://forums.suse.com/showthread.php?3418-Zypper-command[/color]
So my response to ab’s comment is…
Thanks for that.
On a side note, I’m wondering if zypper grabs updates that the
yast/online updates option does not.
One one of my servers that I updated & rebooted today, yast/online
updates shows nothing available, but I get the following:
zypper lp:
Loading repository data…
Reading installed packages…
Repository | Name | Version | Category | Status
-------------------±-------------------±--------±------------±------
SLES11-SP2-Updates | slessp2-nfs-client | 6222 | recommended | needed
SLES11-SP2-Updates | slessp2-nfs-client | 7286 | recommended | needed
SLES11-SP2-Updates | slessp2-nfs-client | 7382 | recommended | needed
v | SLES11-SP2-Updates | nfs-doc | 1.2.3-18.17.2 | 1.2.3-18.29.1
| x86_64
Also, my SMT server shows this server as up to date. What gives?
–
Stevo
Hi Stevo,
Also, my SMT server shows this server as up to date. What gives?
SMT depends on “update jobs” to run, which usually is done only periodically, i.e. every 6 hours or daily. So the status information displayed by smt-client may well be outdated.
As to your “YOU vs. zypper” question, I have no answer - I’m too used to zypper and have not used YOU in years 
Regards,
Jens
jmozdzen sounds like they ‘said’:
[color=blue]
SMT depends on “update jobs” to run, which usually is done only
periodically, i.e. every 6 hours or daily. So the status information
displayed by smt-client may well be outdated.[/color]
So my response to jmozdzen’s comment is…
Before I updated this server, I ran smt-mirror on my SMT box to get the
latest updates, since that only runs @ midnight.
–
Stevo
Hi Stevo,
Before I updated this server, I ran smt-mirror on my SMT box to get the latest updates, since that only runs @ midnight.
that’s not what I meant. I was talking about jobs issued by the SMT server against the client systems - the smtclient program is invoked periodically to “poll” these jobs and “executes” them. One of these job types is to check the package status, which will in turn update what SMT reports about the client system.
I had describe the details here: https://forums.suse.com/showthread.php?3399-SMT-Issue-Client-is-not-up-to-date&p=16602#post16602
Regards,
Jens
jmozdzen sounds like they ‘said’:
[color=blue]
that’s not what I meant. I was talking about jobs issued by the SMT
server against the client systems - the smtclient program is invoked
periodically to “poll” these jobs and “executes” them. One of these
job types is to check the package status, which will in turn update
what SMT reports about the client system.[/color]
So my response to jmozdzen’s comment is…
I already have cron jobs set up to automate that every 2 hrs (since the
ones generated by SMT don’t seem to work). According to SMT my servers
are up to date, but according to zypper on the client servers, they are
not.
–
Stevo
Hi Stevo,
(sorry for the late reply, it’s a busy season this year.)
I’ve run out of ideas - this might be a good time to open a service request to get a definite answer to your question. And if anyone needed that extra push to voice some knowledge here: Please, add your comments now 
Regards,
Jens