Bug 155337 - Error messages from find when starting xfs
Error messages from find when starting xfs
Status: CLOSED DUPLICATE of bug 154056
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
4
i386 Linux
medium Severity low
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
: EasyFix
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-19 05:40 EDT by Göran Uddeborg
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-19 06:19:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Göran Uddeborg 2005-04-19 05:40:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050309 Fedora/1.7.6-0.cvs.20050309

Description of problem:
When booting (and not hiding things with a graphical boot) there comes error messages from find when starting xfs.  In C locale, they read like this:

find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it).  Please specify options before other arguments.

Version-Release number of selected component (if applicable):
xorg-x11-xfs-6.8.2-19

How reproducible:
Always

Steps to Reproduce:
1. Boot, looking at the messages

Additional info:

Line 39 in the xfs init script reads

         if [ ! -e fonts.dir -o -n "$(find . -type f -maxdepth 1 -cnewer fonts.dir -not -name 'fonts.cache*')" ]; then

Obviously, the fix is to put "-maxdepth 1" before "-type f".
Comment 1 Mike A. Harris 2005-04-19 06:19:03 EDT

*** This bug has been marked as a duplicate of 154056 ***
Comment 2 Göran Uddeborg 2005-04-19 07:35:24 EDT
Ah, I missed to include "devel" in the versions I searched in, before I filed my
own bug.

Note You need to log in before you can comment on or make changes to this bug.