From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Description of problem:
When up2date has to update the up2date package itself,
it restarts the up2date after having updated itself.
However, this re-up2date is spawned off as a child process,
and the original up2date returns immediately, with the
child up2date running asynchronously.
This is particularly troublesome when up2date is used
in a script. The original command returns and the succeeding
script commands try to run, while the spawned up2date is
still running in the background, with packages as yet unupdated
and the rmp database locked.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. have the up2date package itself out of date
2. run something like " up2date -u ; echo 'returned, but not done' "
Actual Results: A child up2date is still running after the 'returned, but not done'
message is printed.
Expected Results: The parent up2date should have waited for the child up2date to
complete before returning.
This should be considered a high severity,
as it breaks system installation and maintainance scripts.
kickstart related? if not, this needs to be aligned to rhel3 u8 and rhel4 u4.
kickstart isn't a required factor to reproduce this bug.
Fix in subversion now.
Fixed in up2date-4.5.0-1
QA Verified, child process no longer stays running
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.