On 11/8/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
[...]
Note that rpm will only do that if the person who packaged the updated RPM
specified a 'postinstall' scriptlet requesting it. So RPM *can* restart a
daemon, but it's a function of the package, not of rpm.
[...]
Sorry for the late
On Mon, Nov 07, 2005 at 10:42:11PM +, Carlos Silva aka|Danger_Man| wrote:
Hello all,
Can someone explain how to apply security patches on the system without
rebooting the machine?
I guess that I cant patch the kernel without compiling and rebooting the
machine, so the only way is
Hello all,
Can someone explain how to apply security patches on the system without
rebooting the machine?
I guess that I cant patch the kernel without compiling and rebooting the
machine, so the only way is with iptables and keeping the daemons fresh?
Regards,
Carlos Silva,
Hey,
Can someone explain how to apply security patches on the system without
rebooting the machine?
I guess that I cant patch the kernel without compiling and rebooting the
machine, so the only way is with iptables and keeping the daemons fresh?
Well, if you have a customised kernel you'll
On Tue, 08 Nov 2005 09:03:32 +1000, Stuart Low said:
Well, if you have a customised kernel you'll probably find that your
need to reboot with a new kernel becomes fairly low (Kernel level
exploits are fairly rare, especially remote ones).
If you've upgraded services probably the easiest way
Carlos Silva aka |Danger_Man| wrote:
Can someone explain how to apply security patches on the system without
rebooting the machine?
If you are interested in Windows patches (I apologise for the market-speak):
http://www.determina.com/solutions/liveshield.html
On Linux you can just restart the
On Mon, 07 Nov 2005 18:05:11 PST, Alexander Sotirov said:
On Linux you can just restart the patched service of course. Most package
managers (i.e. dpkg and rpm) will do it for you after the update.
Note that rpm will only do that if the person who packaged the updated RPM
specified a
