{"id":64216,"date":"2024-07-16T03:01:00","date_gmt":"2024-07-15T17:01:00","guid":{"rendered":"https:\/\/65.254.95.247\/ITblog\/?p=64216"},"modified":"2024-07-25T13:00:23","modified_gmt":"2024-07-25T03:00:23","slug":"linux-find-and-or-locate-files-directories-application-extensions-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/linux-find-and-or-locate-files-directories-application-extensions-tutorial\/","title":{"rendered":"Linux Find and\/or Locate Files\/Directories Application Extensions Tutorial"},"content":{"rendered":"
\"Linux<\/a>

Linux Find and\/or Locate Files\/Directories Application Extensions Tutorial<\/p><\/div>\n

A lot of us have FOMO … ie. Fear of Missing Out … over something. One that worries us, running a web server, is the fear of missing out on the daily report we get regarding software on the RJM Programming website telling us …<\/p>\n

\nWhat, we term as “Application Executable” files<\/i>, changed on the RJM Programming web server within the last 5 days\n<\/p><\/blockquote>\n

Today’s nuanced change to our arrangements revolve around the file extension list covering “Application Executable” files<\/i>. We’d been covering …<\/p>\n

    \n
  1. *.htm*<\/li>\n
  2. *.html*<\/li>\n
  3. *.php* … but not, until today …<\/li>\n
  4. *.*htm*<\/li>\n<\/ol>\n

    Yes, read about the *.phtml<\/a> extension, and we’ve seen with error handling *.shtml<\/a> and *.dhtml<\/a> as well. So, yes, we’re definitely interested!<\/p>\n

    We’re hoping today’s tweaked<\/a> and changed Korn Shell script<\/a> called todays_list.ksh<\/a> called (regarding the report creation only) via crontab<\/a> …<\/p>\n


    \nmm hh * * * ksh \/etc\/init.d\/todays_list.ksh
    \n<\/code><\/p>\n

    … (mm represents minute of hour of day and hh represents hour of day) can ease the “FOMO within”, further to the previous Linux Find and\/or Locate Files\/Directories Double Quote Tutorial<\/a>.<\/p>\n

    \n

    \n

    Previous relevant Linux Find and\/or Locate Files\/Directories Double Quote Tutorial<\/a> is shown below.<\/p>\n

    \"Linux<\/a>

    Linux Find and\/or Locate Files\/Directories Double Quote Tutorial<\/p><\/div>\n

    When you write inhouse procedures that end in reports you can occasionally “get sideswiped” by peculiarities in the data that occurs. But it could be the cause of that irregularity that the report is meant to highlight. And so, if there is a problem showing the report, then what’s the point?!<\/p>\n

    This started happening to us the other day with the procedure that sends us information about “files changed in the last week” on this RJM Programming domain, whose blog you are reading now. This report gives a list of Linux web server files changed since the last week, roughly. We first talked about all this way back with Linux Find and\/or Locate Files\/Directories Primer Tutorial<\/a>.<\/p>\n

    Our research started because of an error message when bringing up the “files since” report …<\/p>\n

    \nParse error:<\/b> syntax error, unexpected ‘Z’ (T_STRING), expecting ‘,’ or ‘;’ in todaylist.php on line 155\n<\/p><\/blockquote>\n

    … making us think this was a PHP coding issue. Please don’t jump to conclusions though. Anyway, step 1 should be to go to “todaylist.php” (the “files since” report, we needed to be reminded) to its line 155. Doh?!?! Got us to see the record …<\/p>\n

    \n<br>.\/PHP\/x_f(now)=sysdate().sleep(3),0))XOR”Z.htm\n<\/p><\/blockquote>\n

    Huh?! Yes, you are not alone aghast about this form of filename! But it’s possible, so there are now two problem aspects …<\/p>\n