On Fri, Jan 21, 2005 at 10:18:44AM -0800, Ken Bloom wrote:
> So I dist-upgrade, and it upgrades 12 packages. Your postinst runs before
> any of the other 11. The computer reboots immediately in your postinst.
Even worse: One of those other 11 was a kernel-image package, and this
machine uses lilo
Op ma, 24-01-2005 te 16:39 +1100, schreef Brian May:
> > "Wouter" == Wouter Verhelst <[EMAIL PROTECTED]> writes:
>
> Wouter> lsof +L 1
>
> rebooting is the only way to make sure rebooting will work if a reboot
> is required for some reason during peak usage, e.g. power failure,
> etc...
>
Brian May wrote:
"Wouter" == Wouter Verhelst <[EMAIL PROTECTED]> writes:
Wouter> lsof +L 1
rebooting is the only way to make sure rebooting will work if a reboot
is required for some reason during peak usage, e.g. power failure,
etc...
In some situations it might be better to test rebooting fi
On Fri, 21 Jan 2005 13:21:36 +0100, Adeodato Simó <[EMAIL PROTECTED]>
wrote:
>* Andreas Barth [Fri, 21 Jan 2005 13:13:51 +0100]:
>> using old libs. E.g.
>> lsof | grep dpkg- | awk '{print $1, $8}' | sort +0
>> helps you to find out which ones.
>
> There is also checkrestart from the debian-goodi
> "Wouter" == Wouter Verhelst <[EMAIL PROTECTED]> writes:
Wouter> lsof +L 1
rebooting is the only way to make sure rebooting will work if a reboot
is required for some reason during peak usage, e.g. power failure,
etc...
In some situations it might be better to test rebooting first at
lo
Op zo, 23-01-2005 te 10:30 +0100, schreef Marc Haber:
> I haven't been asked to re-start any services by glibc updates for
> quite some time, and back in the days when glibc asked to restart
> services, it always failed.
>
> So, rebooting seems to be the only way to be sure after a library
> updat
On Fri, 21 Jan 2005 13:34:51 -0500, Joey Hess <[EMAIL PROTECTED]>
wrote:
>Roberto Sanchez wrote:
>> If the system is that important to the admin, he will pay attention to such
>> things. Imagine that you are upgrading ssh for some security update over the
>> weekend. If your system is in some col
On Fri, 21 Jan 2005 13:06:55 +0100, Andreas Barth
<[EMAIL PROTECTED]> wrote:
>I disagree. You should warn the administrator that he has to do that.
>Especially just restarting ssh is _very_ wrong IMHO, because it can
>easily kill the only access to a remote computer. Take a look how glibc
>does it,
Henrique de Moraes Holschuh wrote:
Never mind the very idea of using anything Microsoft in such a scenario.
^
You meant Micros~1 ?
:-)
Anurag
--
---
__ __
gnu /n
On Fri, Jan 21, 2005 at 01:34:51PM -0500, Joey Hess wrote:
> If your system is in a colo, it would be wise to have a backup login
> method besides ssh.
Oh yes, especially since my ssh regularly beaks because of 2UsePam yes" and
"ListenAddress ::" while switching between stable and testing versio
Em Sex, 2005-01-21 Ãs 14:56 +0100, Andreas Barth escreveu:
> Yes. But I prefer verifying that I can login again after each ssh
> restart. So, I want to do that _only_ if I explicitly do it. (Others may
> disagree.)
I always do test I can still login after restarting ssh. The trick is
using a difer
Roberto Sanchez wrote:
> If the system is that important to the admin, he will pay attention to such
> things. Imagine that you are upgrading ssh for some security update over the
> weekend. If your system is in some colo or other remote location where you
> are unable to access it until Monday m
On Thu, 20 Jan 2005 15:09:46 -0300, Diogo Kollross wrote:
> Is there a problem in using something like
>
> shutdown -r now
>
> inside a postinst script of a package?
So I dist-upgrade, and it upgrades 12 packages. Your postinst runs before
any of the other 11. The computer reboots immediately
On Fri, 21 Jan 2005, Petter Reinholdtsen wrote:
> [David Sawyer]
> > Moral of the story: NEVER SHUTDOWN OR REBOOT WITHOUT ASKING.
No. Never handle serious business like you'd handle your home's gateway
machine.
> Another moral might be to always test the stuff you plan to do on a
> production se
[David Sawyer]
> Moral of the story: NEVER SHUTDOWN OR REBOOT WITHOUT ASKING.
Another moral might be to always test the stuff you plan to do on a
production server on a test-server first. I fail to see how it is
sensible to browse the net on a production server. And I fail to see
how it is smar
This reminds me of a horror story at a place I used to work. I was
browsing the 'Net on one of our production servers (this thing served
hundreds of banks around the world). I was looking for some fix or SP
for NT. I came across this site that started installing Flash Player.
It installed it, t
On Fri, Jan 21, 2005 at 11:00:49AM +0100, Marc Haber wrote:
> On Thu, 20 Jan 2005 21:27:46 +0100, Osamu Aoki <[EMAIL PROTECTED]>
> wrote:
> >Relax, he did not say "rm -rf /" in postinst.
>
> That would be postrm.
or, prerm, since it hasn't been rm'd yet. postrm would be run after, if
only it sti
Quoting Henrique de Moraes Holschuh <[EMAIL PROTECTED]>:
> On Fri, 21 Jan 2005, Andreas Barth wrote:
> > Yes. But I prefer verifying that I can login again after each ssh
> > restart. So, I want to do that _only_ if I explicitly do it. (Others may
> > disagree.)
>
> I disagree ;-) The way it is
On Fri, 21 Jan 2005, David Schmitt wrote:
> On Friday 21 January 2005 11:03, Marc Haber wrote:
> > This prompts a question I have been wanting to ask for ages: When a
> > security update for, say, libc6, libssl or libz is installed, do I
> > need to restart services or not? That's one of the questi
On Fri, 21 Jan 2005, Andreas Barth wrote:
> Yes. But I prefer verifying that I can login again after each ssh
> restart. So, I want to do that _only_ if I explicitly do it. (Others may
> disagree.)
I disagree ;-) The way it is done now, punishes lack of attention *IF* a
ssh bug breaks it, with a
* Marc Haber:
> This prompts a question I have been wanting to ask for ages: When a
> security update for, say, libc6, libssl or libz is installed, do I
> need to restart services or not? That's one of the question you ask
> three people and get five different answers.
It depends. If the bug is
* Colin Watson ([EMAIL PROTECTED]) [050121 14:50]:
> On Fri, Jan 21, 2005 at 01:06:55PM +0100, Andreas Barth wrote:
> > I disagree. You should warn the administrator that he has to do that.
> > Especially just restarting ssh is _very_ wrong IMHO, because it can
> > easily kill the only access to a
Op do, 20-01-2005 te 21:27 +0100, schreef Osamu Aoki:
> On Thu, Jan 20, 2005 at 07:35:42PM +0100, Wouter Verhelst wrote:
> > Op do, 20-01-2005 te 15:09 -0300, schreef Diogo Kollross:
> > > Is there a problem in using something like
> > >
> > > shutdown -r now
> > >
> > > inside a postinst scrip
On Fri, Jan 21, 2005 at 01:06:55PM +0100, Andreas Barth wrote:
> I disagree. You should warn the administrator that he has to do that.
> Especially just restarting ssh is _very_ wrong IMHO, because it can
> easily kill the only access to a remote computer.
Restarting sshd doesn't kill existing ses
On Friday 21 January 2005 11:03, Marc Haber wrote:
> This prompts a question I have been wanting to ask for ages: When a
> security update for, say, libc6, libssl or libz is installed, do I
> need to restart services or not? That's one of the question you ask
> three people and get five different a
* Andreas Barth [Fri, 21 Jan 2005 13:13:51 +0100]:
> using old libs. E.g.
> lsof | grep dpkg- | awk '{print $1, $8}' | sort +0
> helps you to find out which ones.
There is also checkrestart from the debian-goodies package. Seems to
do some more stuff, but don't know how much better it is.
* Andreas Barth ([EMAIL PROTECTED]) [050121 13:10]:
> * Tino Keitel ([EMAIL PROTECTED]) [050121 13:02]:
> > On Fri, Jan 21, 2005 at 11:03:08 +0100, Marc Haber wrote:
> > > On 20 Jan 2005 14:45:52 -0800, Thomas Bushnell BSG <[EMAIL PROTECTED]>
> > > wrote:
> > > >Yes. Debian packages are supposed t
* Tino Keitel ([EMAIL PROTECTED]) [050121 13:02]:
> On Fri, Jan 21, 2005 at 11:03:08 +0100, Marc Haber wrote:
> > On 20 Jan 2005 14:45:52 -0800, Thomas Bushnell BSG <[EMAIL PROTECTED]>
> > wrote:
> > >Yes. Debian packages are supposed to be able to be installed and
> > >start working without requi
On Fri, 2005-01-21 at 11:03 +0100, Marc Haber wrote:
> On 20 Jan 2005 14:45:52 -0800, Thomas Bushnell BSG <[EMAIL PROTECTED]>
> wrote:
> >Yes. Debian packages are supposed to be able to be installed and
> >start working without requiring any reboots. We've made this work
> >pretty well for libc
On Fri, Jan 21, 2005 at 11:03:08 +0100, Marc Haber wrote:
> On 20 Jan 2005 14:45:52 -0800, Thomas Bushnell BSG <[EMAIL PROTECTED]>
> wrote:
> >Yes. Debian packages are supposed to be able to be installed and
> >start working without requiring any reboots. We've made this work
> >pretty well for l
On 20 Jan 2005 14:45:52 -0800, Thomas Bushnell BSG <[EMAIL PROTECTED]>
wrote:
>Yes. Debian packages are supposed to be able to be installed and
>start working without requiring any reboots. We've made this work
>pretty well for libc and all kinds of hard cases; you can make it work
>for yours too
On Thu, 20 Jan 2005 21:27:46 +0100, Osamu Aoki <[EMAIL PROTECTED]>
wrote:
>Relax, he did not say "rm -rf /" in postinst.
That would be postrm.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mai
In article <[EMAIL PROTECTED]>,
Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote:
>Diogo Kollross writes:
>
>> shutdown -r now
>>
>> inside a postinst script of a package?
>
>If you're going do that, you may want to replace /bin/init temporarily
>to finish the post-reboot part of the installation.
T
Diogo Kollross <[EMAIL PROTECTED]> writes:
> Is there a problem in using something like
>
> shutdown -r now
>
> inside a postinst script of a package?
Yes. Debian packages are supposed to be able to be installed and
start working without requiring any reboots. We've made this work
pretty we
Diogo Kollross writes:
> shutdown -r now
>
> inside a postinst script of a package?
If you're going do that, you may want to replace /bin/init temporarily
to finish the post-reboot part of the installation.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
h
[Diogo Kollross]
> Is there a problem in using something like
>
> shutdown -r now
>
> inside a postinst script of a package?
It will probably not do what you want, as the package installation
process might be interrupted, and packages might be left half-way
installed. Besides, it is a very ba
On Thu, Jan 20, 2005 at 07:35:42PM +0100, Wouter Verhelst wrote:
> Op do, 20-01-2005 te 15:09 -0300, schreef Diogo Kollross:
> > Is there a problem in using something like
> >
> > shutdown -r now
> >
> > inside a postinst script of a package?
>
> I was going to say something smart and funny, b
Op do, 20-01-2005 te 15:09 -0300, schreef Diogo Kollross:
> Is there a problem in using something like
>
> shutdown -r now
>
> inside a postinst script of a package?
I was going to say something smart and funny, but it isn't coming.
What the hell have you been smoking?
Hint: this isn't Windo
On Thu, Jan 20, 2005 at 03:09:46PM -0300, Diogo Kollross wrote:
> Is there a problem in using something like
>
> shutdown -r now
>
> inside a postinst script of a package?
Definately.
Even if the package requires a reboot to work you should let the
administrator choose when that should b
Is there a problem in using something like
shutdown -r now
inside a postinst script of a package?
--
Diogo Kollross
___
Yahoo! Acesso Grátis - Instale o discador do Yahoo! agora.
http://br.acesso.yahoo.
40 matches
Mail list logo
