Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#3468 - Restart demons after upgrade

Attached to Project: Pacman
Opened by Gerwin Brill (brill) - Saturday, 12 November 2005, 19:39 GMT
Last edited by arjan timmerman (blaasvis) - Sunday, 13 November 2005, 09:55 GMT
Task Type Feature Request
Category
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I experienced that after a pacman upgrade of dbus the demon does not properly start on the next boot because of a leftover pid file! Please correct me if I am wrong but isn't it correct that pacman does not stop running demons like dbus bevor upgrading and restart it afterwards?! Inspecting the pacman source I saw that upgrading packages is just a remove and reinstall process. So I think it would be nice if pacman could check bevor upgrading if the current package is just running and if so, stop->remove->add->restart?! debians dpkg does things like that!

Greetings from germany,

Gerwin


This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 15 November 2005, 12:51 GMT
Reason for closing:  Fixed
Additional comments about closing:  Stale pidfile should be removed on start now
Comment by Rod (rodrigo) - Sunday, 13 November 2005, 17:42 GMT
I've also notice that. In fact the problem is not just happening when you upgrade dbus. Also when your system crashs, or by any means doesn't do a clean shutdown (stop the daemon dbus), you get the same problem: can't start dbus cause there's a lost pid file from the previous running.

Best regards,

Rodrigo

Comment by Gerwin Brill (brill) - Sunday, 13 November 2005, 19:09 GMT
Yes, you're right! I noticed that too! But I think it would be a good idea in general if a running demon gets stopped bevor upgrading und restarted afterwards! I don't realy know if Arch Linux is ready for use in productive server scenarios! I personaly use Arch as a desktop distribution that perfectly fits to my needs! A not-starting-demon is for that case no problem! But if I think of a productive server environment, the package management must take care about things like that to retain the current state!

Greetings,

Gerwin

Loading...