Well, the network devices works now, but on boot process I get now the message xargs environment too large for exec when trying cleaning of /var/run and /var/lock. It seems that the result is too large for xargs to handle with.
Same happens here. At least the network works now. Sticking with 1.8.6.7 for now.
i am getting this too the error is, *Cleaning /var/lock, /var/run.... xargs: environment is too large for exec i also have bootsplash and get this *Caching service dependancies.... *Services 'bootsplash' and 'local' have circular *dependancy of a type 'iafter'; continuing.....
Getting same error here, just install 1.4_rc4 from stage 1. No problems with networking though, just the xargs error...
Already fixed in cvs a few days back: ---------------------------------------------------- Index: init.d/bootmisc =================================================================== RCS file: /home/cvsroot/gentoo-src/rc-scripts/init.d/bootmisc,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- init.d/bootmisc 12 May 2003 21:23:05 -0000 1.29 +++ init.d/bootmisc 21 May 2003 18:55:58 -0000 1.30 @@ -1,7 +1,7 @@ #!/sbin/runscript # Copyright 1999-2003 Gentoo Technologies, Inc. # Distributed under the terms of the GNU General Public License v2 -# $Header: /home/cvsroot/gentoo-src/rc-scripts/init.d/bootmisc,v 1.29 2003/05/12 21:23:05 azarah Exp $ +# $Header: /home/cvsroot/gentoo-src/rc-scripts/init.d/bootmisc,v 1.30 2003/05/21 18:55:58 azarah Exp $ depend() { @@ -27,7 +27,7 @@ eend 0 fi - if [ -x /sbin/rc-envupdate.sh ] + if [ -x /sbin/env-update.sh ] then ebegin "Updating environment" /sbin/env-update.sh >/dev/null
It's not fixed. I just patched bootmisc, and I get the same message: *Cleaning /var/lock, /var/run.... xargs: environment is too large for exec
The xargs issue is still present on both my machines. It exists at bug 21827 and is assigned to kernel team which puzzles me as I thought it was a baselayout issue. Anyway, the following forum post discusses the problem very briefly. http://forums.gentoo.org/viewtopic.php?t=55496
the line ebegin "Cleaning /var/lock, /var/run" ( find /var/lock -type f -print0 | xargs -0 rm -f -- 1>&2 ) can be changed to: ebegin "Cleaning /var/lock, /var/run" ( find /var/lock -type f -exec rm -f {} \; ) so xargs is to involved and the warning is not displayed. can this patch be acceptable for you ? bye
Well, when the whole functionality keeps available, it should be good. I didn't try it, yet (because of lack of time).
Bleh, ok, I had it fixed local, sorry.
*** Bug 23268 has been marked as a duplicate of this bug. ***
*** Bug 22637 has been marked as a duplicate of this bug. ***
This is still not fixed in (in the meantime stable-marked) baselayout-1.8.6.8-r1!
Not fixed for me either with 2.4.20-r5 kernel. I suggest reopening it, and applying this patch to create a 4.1.7-r5 version of findutils: http://mail.gnu.org/archive/html/bug-findutils/2002-09/msg00004.html
*** Bug 21827 has been marked as a duplicate of this bug. ***
It's definitely not fixed. Installed rc4 from stage1 yesterday and it's still there.
the command $>find /var/lock -type f -exec rm -f -- {} \; 1>&2 will also delete files like ".keep", here is an example: $>find /var/lock -type f /var/lock/subsys/.keep /var/lock/.keep /var/lock/LCK..modem
find /tmp -type f -not -name .keep -exec rm -f {} \; would solve this.
This may provide a solution that allows us to keep using xargs, posted recently to the gentoo-user ML. On Tuesday 08 July 2003 21:37, James H. Cloos Jr. wrote: > >>>>> "Rex" == Rex Walters <rw@pobox.com> writes: > > Rex> This definitely fixes the error but I'm curious why the first > Rex> version doesn't work? Seems like a bug in gnu find or xargs to > Rex> me -- the fix is really more of a workaround. > > In xargs. One of the notes on that tree of bugzilla ids references > an email sent to one of the gnu mail lists. The bug is that xargs' > test for the size of the env comes before the args are parsed; the > arg -s allows the env to be elarged, but xargs fails to take that > into consideration before bailing out. > > The error only shows up at boot because the rc process must be > creating an env larger than 20k. Once booted your shell has a > much smaller env. (Mine is just under 3k.) > > -JimC > > > -- > gentoo-user@gentoo.org mailing list
Created attachment 14987 [details, diff] One of many numerous patches I added bug 24993 which accidently was a duplicate of this bug, but it contains an easir fix than some of the ones described here. For that reason patch was checked. Can someone please explain why this 20k limit is even needed on modern era pcs? Email ecyoung@speakeasy.net with an answer... I'm curious
The bug does still exist, why is this closed?
Baselayout was updated recently to 1.8.6.9. This was intended as a bugfix release I'm told and took care of many bugs including the xargs error. Please update, replace /etc/init.d/bootmisc using etc-update and test again. It worked for me.
closed, see bug #23569 for more details
*** Bug 28425 has been marked as a duplicate of this bug. ***
A diff between revisions 1.29 and 1.33 of bootmisc reveals: - ( find /var/lock -type f -print0 | xargs -0 rm -f -- 1>&2 ) + ( find /var/lock -type f -exec rm -f -- {} \; ) What happened to the comment about .keep? I decided to through my suggestion in here as well (I know it's fixed already, but I like the xargs pipe). - ( find /var/lock -type f -print0 | xargs -0 rm -f -- 1>&2 ) + ( find /var/lock -type f -print0 | env - xargs -0 rm -f -- 1>&2 )