how do i know i need a reboot after a console based "upgrade"?

when updating a system with the newest packages using the
desktop
tools like synaptic,
if a package is upgraded that requires a reboot to take
effect,
there is a little icon that shows up on the upper panel to
let me know
i need to reboot.


on a server system,  if i do a "sudo apt-get
upgrade" or "sudo aptitude upgrade"
is there anyway to know i need a reboot?

is there a file that is flagged?
or does the upgrade process return something that i can
catch using grep?
or better still is there a way to tell apt-get or aptitude
to reboot the system
after an upgrade when necessary?

TIA,
Tomoki Taniguchi

-- 
ubuntu-users mailing list
ubuntu-userslists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

* Tomoki Taniguchi wrote:
> when updating a system with the newest packages using
the desktop
> tools like synaptic,
> if a package is upgraded that requires a reboot to take
effect,
> there is a little icon that shows up on the upper panel
to let me know
> i need to reboot.
> 
> 
> on a server system,  if i do a "sudo apt-get
upgrade" or "sudo aptitude upgrade"
> is there anyway to know i need a reboot?
> 
> is there a file that is flagged?
> or does the upgrade process return something that i can
catch using grep?
> or better still is there a way to tell apt-get or
aptitude to reboot the system
> after an upgrade when necessary?

im not sure exactly where or what lets u know that you need
a reboot,
however your only really going to need to reboot on a server
when there is a
new kernel installed and your better off scheduling the
downtime
manually when you see a new kernel in the updates to
minimise the impact
+ in the event that the new kernel doesnt boot,  resolve the
issues.
rather than springing the reboot on you at any time and
having the concequences
that follow.

-- 
ben darby

-- 
ubuntu-users mailing list
ubuntu-userslists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

ben darby wrote:

> * Tomoki Taniguchi wrote:
>> when updating a system with the newest packages
using the desktop
>> tools like synaptic,
>> if a package is upgraded that requires a reboot to
take effect,
>> there is a little icon that shows up on the upper
panel to let me know
>> i need to reboot.
>> 
>> 
>> on a server system,  if i do a "sudo apt-get
upgrade" or "sudo aptitude
>> upgrade" is there anyway to know i need a
reboot?
>> 
>> is there a file that is flagged?
>> or does the upgrade process return something that i
can catch using grep?
>> or better still is there a way to tell apt-get or
aptitude to reboot the
>> system after an upgrade when necessary?
> 
> im not sure exactly where or what lets u know that you
need a reboot,
> however your only really going to need to reboot on a
server when there is
> a new kernel installed and your better off scheduling
the downtime
> manually when you see a new kernel in the updates to
minimise the impact
> + in the event that the new kernel doesnt boot, 
resolve the issues.
> rather than springing the reboot on you at any time and
having the
> concequences that follow.
> 
I agree.  I always do console-based upgrades, and I only
reboot for a new
kernel.  If synaptic is telling you you need to reboot it's
either being
ultraconservative (bah...) or it really does have a new
kernel.
-- 
derek


-- 
ubuntu-users mailing list
ubuntu-userslists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Tomoki Taniguchi wrote:
> when updating a system with the newest packages using
the desktop
> tools like synaptic,
> if a package is upgraded that requires a reboot to take
effect,
> there is a little icon that shows up on the upper panel
to let me know
> i need to reboot.
> 
> 
> on a server system,  if i do a "sudo apt-get
upgrade" or "sudo aptitude upgrade"
> is there anyway to know i need a reboot?
> 
> is there a file that is flagged?
> or does the upgrade process return something that i can
catch using grep?
> or better still is there a way to tell apt-get or
aptitude to reboot the system
> after an upgrade when necessary?
> 
> TIA,
> Tomoki Taniguchi
> 

AFAIK if you do 'upgrade' then you shouldn't need to restart
for the 
changes to take effect. If you do a 'dist-upgrade' then
generally you 
will need to restart for the changes to take effect. I'm not
aware of 
anything else that lets you know.


-- 
ubuntu-users mailing list
ubuntu-userslists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

On 4/17/07, Gabriel Dragffy <dragffyyandex.ru> wrote:
> Tomoki Taniguchi wrote:
> > when updating a system with the newest packages
using the desktop
> > tools like synaptic,
> > if a package is upgraded that requires a reboot to
take effect,
> > there is a little icon that shows up on the upper
panel to let me know
> > i need to reboot.
> >
> >
> > on a server system,  if i do a "sudo apt-get
upgrade" or "sudo aptitude upgrade"
> > is there anyway to know i need a reboot?
> >
> > is there a file that is flagged?
> > or does the upgrade process return something that
i can catch using grep?
> > or better still is there a way to tell apt-get or
aptitude to reboot the system
> > after an upgrade when necessary?
> >
> > TIA,
> > Tomoki Taniguchi
> >
>
> AFAIK if you do 'upgrade' then you shouldn't need to
restart for the
> changes to take effect. If you do a 'dist-upgrade' then
generally you
> will need to restart for the changes to take effect.
I'm not aware of
> anything else that lets you know.

I don't think dist-upgrade vs upgrade matters UNLESS there
has been a
change to a kernel or a kernel module.

If you install the package apticron (and get postfix set
correctly)
your server will generate an email message telling you what
to do. I
cannot recall now whether the apticron message told me to
reboot after
the recent kernel upgrade (I already knew I should). After
the more
recent update to a kdelibs package, apticron gave explicit
directions
(in the email message) describing how to test and implement
it.

The apticron package is highly recommended on any server,
especially a
"headless" one.

-- 
ubuntu-users mailing list
ubuntu-userslists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

On Tue, 2007-04-17 at 12:36 +0900, Tomoki Taniguchi wrote:
> on a server system,  if i do a "sudo apt-get
upgrade" or "sudo
> aptitude upgrade"
> is there anyway to know i need a reboot? 

If you subscribe to the security-announce mailing list
(which you should
do anyway if you run a server of even small importance),
then the
announcements will tell you what to do to effect the upgrade
(reboot,
restart service, etc)


-- 
ubuntu-users mailing list
ubuntu-userslists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

On Tue, 2007-04-17 at 15:33 +0100, Gabriel Dragffy wrote:
> if you do 'upgrade' then you shouldn't need to restart
for the 
> changes to take effect. If you do a 'dist-upgrade' then
generally you 
> will need to restart for the changes to take effect. 

No, the difference between upgrade and dist-upgrade is just
that upgrade
will never uninstall packages to resolve dependencies,
while
dist-upgrade will. See "man apt-get" or "man
aptitude"


-- 
ubuntu-users mailing list
ubuntu-userslists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

On Tue, 2007-04-17 at 22:10 +0100, Gabriel Dragffy wrote:
> But the few packages that do require a restart, 
> e.g. kernel updates, will only be installed when the
command 
> 'dist-upgrade' is issued. 

Hmmm. I seriously have never seen this and cannot imagine
what you
mean 
Can anyone shed light?


-- 
ubuntu-users mailing list
ubuntu-userslists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users