During rpm upgrade of packages that have /etc/event.d/ files like initscripts, rhgb or upstart itself, it temporarily creates files with names like: /etc/event.d/serial;47d7dd72 before they are moved into their permanent locations. Apparently inotify sees the temporary file creation and tells upstart to do something with it. Then you get errors on the console like: init: /etc/event.d/serial;47d7dd72: unable to read: Invalid argument In addition to ignoring the .rpmsave/.rpmnew files, upstart should also ignore files with a semicolon in their names.
That's kind of a broad category, subject to user gotchas. Might be better to tell upstart not to watch inotify for a bit while the packages are upgraded. Why do these files have to be generated in this folder?
If they're generated anywhere else by rpm, they can't be atomically renamed in place.
Realistically how many times are files with semicolons in their names used? > Why do these files have to be generated in this folder? How do you propose we do this in a reliable way?
Match on ';<8 hex digits>' at the end of the file name, I suppose. It would be used for any file being laid down by rpm.
Ok. I'll look at a patch for this.
Fixed in upstart-0.3.9-13