Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades
Hi! 2013/8/22 Paul Wise p...@debian.org: On Thu, Aug 22, 2013 at 11:17 AM, Matthias Klumpp wrote: PackageKit can do that ;-) It has a plugin to check for shared libraries in use, I just haven't tested in yet. It should show the names of services which need to be restarted after a security update. Cool. This info is at least shown on the command line (and only for security updates). How does it know if an update fixes a security issue? Just checking if it comes from security.d.o would not be enough since updates to unstable often fix security issues. It just checks that - I wanted it to look for upload-priorities in Debian changelogs some time ago, but doing that was just way too slow. I guess it uses the debsecan/security-tracker data? That would be a nice feature to have! I think when this features was revised some time ago, these options where not yet available. It would just have to be fast enough, because PK needs the security status almost immediately (otherwise the updater UI will have very long loading times). Cheers, Matthias -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caknhny9iaur5bcsz5atvtk+awce4eip+ere6svmfytnebdv...@mail.gmail.com
Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades
On Tue, Oct 15, 2013 at 12:21 AM, Matthias Klumpp wrote: It just checks that - I wanted it to look for upload-priorities in Debian changelogs some time ago, but doing that was just way too slow. Higher upload priorities doesn't indicate a security fix. It could be an RC bug fix or certain people using higher priority without that being appropriate. That would be a nice feature to have! I think when this features was revised some time ago, these options where not yet available. It would just have to be fast enough, because PK needs the security status almost immediately (otherwise the updater UI will have very long loading times). debsecan and the security tracker has been around since before the etch release, so I guess it existed before PK. As to speed, it could update the debsecan data before every apt-get update. http://archive.debian.net/search?keywords=debsecan -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6EsSt342KHSvj_sE=8J+uPCFO8=4gq9cobddwyqxqk...@mail.gmail.com
Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades
2013/10/14 Paul Wise p...@debian.org: On Tue, Oct 15, 2013 at 12:21 AM, Matthias Klumpp wrote: It just checks that - I wanted it to look for upload-priorities in Debian changelogs some time ago, but doing that was just way too slow. Higher upload priorities doesn't indicate a security fix. It could be an RC bug fix or certain people using higher priority without that being appropriate. Yes, that was more like a hint, because I didn't know a better way to set update-priorities back then ;-) That would be a nice feature to have! I think when this features was revised some time ago, these options where not yet available. It would just have to be fast enough, because PK needs the security status almost immediately (otherwise the updater UI will have very long loading times). debsecan and the security tracker has been around since before the etch release, so I guess it existed before PK. As to speed, it could update the debsecan data before every apt-get update. http://archive.debian.net/search?keywords=debsecan Nice! I learned about debsecan just about 4 months ago, so I thought it was new... (this falls in the category of cool tools you should have been using for years, but didn't) If aptcc could gain support for this, it might even make sense to make PackageKit recommend it, so it gets pulled in by default. Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKNHny-ZFi4=qgvtz8ghhkjmi9u-iu49e7ra5v3htash1ch...@mail.gmail.com
Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades
]] Patrick Matthäi needrestart checks which daemons need to be restarted after library upgrades. It is inspired by checkrestart(1) from the debian-goodies package. It does not rely on lsof as checkrestart does. Why not just improve checkrestart rather than offering an alternative? -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/m2r4dm19a7@rahvafeir.err.no
Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades
On Thu, Aug 22, 2013 at 09:20:32AM +0200, Tollef Fog Heen wrote: ]] Patrick Matthäi needrestart checks which daemons need to be restarted after library upgrades. It is inspired by checkrestart(1) from the debian-goodies package. It does not rely on lsof as checkrestart does. Why not just improve checkrestart rather than offering an alternative? Why is not using lsof an improvement? -- Kind regards, Loong Jin signature.asc Description: Digital signature
Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades
On Thu, 22 Aug 2013 09:20:32 +0200 Tollef Fog Heen tfh...@err.no wrote: needrestart checks which daemons need to be restarted after library upgrades. It is inspired by checkrestart(1) from the debian-goodies package. It does not rely on lsof as checkrestart does. Why not just improve checkrestart rather than offering an alternative? checkrestart is a Python program, needrestart is a Perl program, so asking someone (who exactly, by the way?) touting an alternative to improve the original is not exactly correct in this particular case. By the way, I have always been puzzled with checkrestart being a part of the package containing a set of random tools. I mean, the discoverability of checkrestart is exactly zero, and one have to stumble on a random blog post to even know this useful tool exists. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130822115831.5da9b17fbbf3b2710ed89...@domain007.com
Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades
On Thu, Aug 22, 2013 at 9:58 AM, Konstantin Khomoutov wrote: By the way, I have always been puzzled with checkrestart being a part of the package containing a set of random tools. I mean, the discoverability of checkrestart is exactly zero, and one have to stumble on a random blog post to even know this useful tool exists. In an ideal world it would be part of PackageKit (and or apt). -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6fhmcgsiohmje8ddmxe+vburcdrm9kmz3j0eopepqd...@mail.gmail.com
Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades
2013/8/22 Paul Wise p...@debian.org: On Thu, Aug 22, 2013 at 9:58 AM, Konstantin Khomoutov wrote: By the way, I have always been puzzled with checkrestart being a part of the package containing a set of random tools. I mean, the discoverability of checkrestart is exactly zero, and one have to stumble on a random blog post to even know this useful tool exists. In an ideal world it would be part of PackageKit (and or apt). PackageKit can do that ;-) It has a plugin to check for shared libraries in use, I just haven't tested in yet. It should show the names of services which need to be restarted after a security update. This info is at least shown on the command line (and only for security updates). Cheers, Matthias 2013/8/22 Paul Wise p...@debian.org: On Thu, Aug 22, 2013 at 9:58 AM, Konstantin Khomoutov wrote: By the way, I have always been puzzled with checkrestart being a part of the package containing a set of random tools. I mean, the discoverability of checkrestart is exactly zero, and one have to stumble on a random blog post to even know this useful tool exists. In an ideal world it would be part of PackageKit (and or apt). -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6fhmcgsiohmje8ddmxe+vburcdrm9kmz3j0eopepqd...@mail.gmail.com -- Debian Developer | Freedesktop-Developer KDE-Developer| GNOME-Contributor I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caknhny9tifqwv93qevrn6ei2stus6f1gwjjxkxjt99f-wti...@mail.gmail.com
Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades
Am 2013-08-22 10:03, schrieb Paul Wise: On Thu, Aug 22, 2013 at 9:58 AM, Konstantin Khomoutov wrote: By the way, I have always been puzzled with checkrestart being a part of the package containing a set of random tools. I mean, the discoverability of checkrestart is exactly zero, and one have to stumble on a random blog post to even know this useful tool exists. In an ideal world it would be part of PackageKit (and or apt). FYI PackageKit already features a plugin that detects applications which should be restared because of updated shared librarys. @Paul: Sorry for the private reply. Cheers, Sebastian -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5b8a8e772b45ae1b379b96e90dfe3...@glatzor.de
Re: Bug#719673: ITP: needrestart -- needrestart checks which daemons need to be restarted after library upgrades
On Thu, Aug 22, 2013 at 11:17 AM, Matthias Klumpp wrote: PackageKit can do that ;-) It has a plugin to check for shared libraries in use, I just haven't tested in yet. It should show the names of services which need to be restarted after a security update. Cool. This info is at least shown on the command line (and only for security updates). How does it know if an update fixes a security issue? Just checking if it comes from security.d.o would not be enough since updates to unstable often fix security issues. I guess it uses the debsecan/security-tracker data? -- http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6gxh7ugh+lr6g4xk5alttevf-mj9ft1kvsy2nbqp1p...@mail.gmail.com
