On Sat, Feb 12, 2011 at 08:50:18AM -0800, Jameson Graef Rollins wrote: > When urxvtd is invoked with no options, it is supposed to run in the > foreground. However, I believe after the upgrade to 9.09, the daemon > is forking into the background and producing the following message: > > unable to lock into ram: Cannot allocate memory > > As mentioned, the daemon is not supposed to fork on it's own (that's > what the --fork option is for). Also, the message seems to indicate > that it is trying to lock itself in to ram, which is supposed to only > happen with the --mlock option. > > I'm wondering if for some reason all of the daemon startup options are > being applied automatically for some reason. I don't see the startup > message either, which is supposed to only be suppressed with the > - --quiet option.
It is a regression, fixed in 9.10. Emanuele -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
