On Sat, Apr 29, 2023 at 5:38 AM Jeffrey Walton wrote:
>
> I have a script that fully updates a machine each night around 4:00
> AM. It also reboots the machine as required.
>
> I noticed Debian has checkrestart. The man page is at
> https://manpages.debian.org/bullseye/debian-go
On Sat, 29 Apr 2023 05:38:05 -0400
Jeffrey Walton wrote:
> I have a script that fully updates a machine each night around 4:00
> AM. It also reboots the machine as required.
You might look at the unattended-upgrades package, which does exactly
this. (Except for the 4:00 AM, but you can adjust th
Hi Everyone,
I have a script that fully updates a machine each night around 4:00
AM. It also reboots the machine as required.
I noticed Debian has checkrestart. The man page is at
https://manpages.debian.org/bullseye/debian-goodies/checkrestart.8.en.html.
I want to ensure I understand "
What I do for perl when I remember is to run cpanp and do a s selfupdate
all command inside of cpanp. That may help Arnold's perl problem I hope.
---
jude Microsoft, windows is accessible. why do
blind people need scree
That's interesting since I have perl on this system checkrestart didn't
mention it. What checkrestart did mention was:
These processes do not seem to have an associated init script to restart
them:
postgresql-9.1:
2578/usr/lib/postgresql/9.1/bin/postgres
2582
Hi,
On 18/11/2011 1:41 PM, Bob Proulx wrote:
Andrew McGlashan wrote:
They are back, after the reboot, but not right away... looks like
I'll have to report a bug. Now, how to tell which "old files" are
the problem
How is your python scripting? The checkrestart script is
Andrew McGlashan wrote:
> They are back, after the reboot, but not right away... looks like
> I'll have to report a bug. Now, how to tell which "old files" are
> the problem
How is your python scripting? The checkrestart script is simply a
python script. If you
rsisted. So ... I've done a full reboot now. I still expect to see the
problem later today, let's see ;-)
# uptime
01:40:15 up 0 min, 1 user, load average: 0.97, 0.22, 0.07
# checkrestart
Found 0 processes using old versions of upgraded files
...
# checkrestart
Found 3 processes
Hi,
On 16/11/2011 10:27 PM, Eduardo M KALINOWSKI wrote:
I believe these are the worker processes spawned by the main dovecot
server, one for each connection a user makes. They only go away when the
user disconnects, even if the main server is restarted, in order not to
forcedly disconnect users.
On Ter, 15 Nov 2011, Andrew McGlashan wrote:
Andrew McGlashan wrote:
# checkrestart
Found 2 processes using old versions of upgraded files
(1 distinct program)
(1 distinct packages)
These processes do not seem to have an associated init script to
restart them:
dovecot-imapd:
18981
and restarted dovecot. New processes *later*
> come up as flagged by checkrestart as using old versions of upgraded
> files. So, something is still getting old files somehow. with no
> further system changes whatsoever
Hmm...Stop the service. Double check that the above listed
P
Hi,
On 15/11/2011 7:31 PM, Bob Proulx wrote:
Andrew McGlashan wrote:
# checkrestart
Found 2 processes using old versions of upgraded files
(1 distinct program)
(1 distinct packages)
These processes do not seem to have an associated init script to
restart them:
dovecot-imapd:
18981
Andrew McGlashan wrote:
> # checkrestart
> Found 2 processes using old versions of upgraded files
> (1 distinct program)
> (1 distinct packages)
> These processes do not seem to have an associated init script to
> restart them:
> dovecot-imapd:
> 18981
Hi,
I've got the following:
# checkrestart
Found 2 processes using old versions of upgraded files
(1 distinct program)
(1 distinct packages)
These processes do not seem to have an associated init script to restart
them:
dovecot-imapd:
18981 /usr/lib/dovecot/imap
14795
On Wed, 02 Mar 2011, Steven Ayre wrote:
> Great, thanks! Perhaps checkrestart could be updated to check that file too?
Please file a wishlist bug. It will depend on whether the maintainer thinks
it is something the tool should warn you about or not.
checkrestart is commonly used to *av
Great, thanks! Perhaps checkrestart could be updated to check that file too?
-Steve
On 2 March 2011 17:11, Darac Marjal wrote:
> On Wed, Mar 02, 2011 at 04:08:15PM +, Steven Ayre wrote:
>> I just upgraded the linux kernel package on a Lenny server and then
>> ran checkresta
On Wed, Mar 02, 2011 at 04:08:15PM +, Steven Ayre wrote:
> I just upgraded the linux kernel package on a Lenny server and then
> ran checkrestart. It reported a few services that needed restarting
> because the openssl package had also been updated, but it didn't say
> anythi
I just upgraded the linux kernel package on a Lenny server and then
ran checkrestart. It reported a few services that needed restarting
because the openssl package had also been updated, but it didn't say
anything about the fact that I was running an earlier kernel than the
one installed.
ip]
>>>> as root. This should list all processes that hang on to stale files. The
>>>> checkrestart command from "debian-goodies" is supposed to do the same
>>>> thing more comfortably, but this does not work for me at the moment (see
>>>>
On Fri, Jul 18, 2008 at 12:20:34 -0500, Ron Johnson wrote:
> On 07/18/08 11:50, Thomas Preud'homme wrote:
> > The Friday 18 July 2008 18:07:41 Florian Kulzer, you wrote :
> [snip]
> >>
> >> as root. This should list all processes that hang on to stale files.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/18/08 11:50, Thomas Preud'homme wrote:
> The Friday 18 July 2008 18:07:41 Florian Kulzer, you wrote :
[snip]
>>
>> as root. This should list all processes that hang on to stale files. The
>> checkrestart command from &q
3,3
>>> 2070470 /usr/lib/libsmbclient.so.0.1 (path inode=2070469)
>>>
>>> I suggest that that is a more reliable method of getting the
>>> information you require.
>> This command returns nothing. The point is that I get these
>> checkrestart me
t; >
> > I suggest that that is a more reliable method of getting the
> > information you require.
>
> This command returns nothing. The point is that I get these
> checkrestart messages even after a reboot, when actually no process
> could run 'old versi
;path inode'
> gnome-cup 4794 otoolel mem REG3,3
> 2070470 /usr/lib/libsmbclient.so.0.1 (path inode=2070469)
>
> I suggest that that is a more reliable method of getting the
> information you require.
This command returns nothing. The point is that I
On Tue, 22 May 2007 11:34:53 +0200
Johannes Wiedersich <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> After some security updates on etch, checkrestart complains about
> processes that should be restarted. However, these particular pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After some security updates on etch, checkrestart complains about
processes that should be restarted. However, these particular packages
haven't been upgraded at all.
Even a reboot doesn't make those go away. Something wrong?
Johann
26 matches
Mail list logo
