Hi--
Ok. I have now found that:
find -x -ls
will do what I need as far as finding all files on a particular volume. Now I need to sort the results by the file's modification date/time.
Is there a way to do that?
Also, I notice that for many files, whereas the man for find says ls is... (8 Replies)
Here is the code, but the list is not sorted properly (alphabetically)?
<?php
function folderlist(){
$startdir = './';
$ignoredDirectory = '.';
$ignoredDirectory = '..';
if (is_dir($startdir)){
if ($dh = opendir($startdir)){
while (($folder = readdir($dh)) !== false){
if... (0 Replies)
Hi,
I have a problem with a shell script.
The script should find all .cpp and .h files and list them.
With:
for file in `find $src -name '*.h' -o -name '*.cpp'
it gives out this:
H:\FileList\A\E\F\G\newCppFile.cpp
H:\FileList\header01.h
H:\FileList\B\nextCppFile.cpp
... (4 Replies)
This is the question being asked: (Sort your data file by last name first, then by the first name second - save as first_last.) I am not quite sure of the type of sort I am being asked to perform. I have read the man pages of the sort command a few times, as well as searching online for possible... (10 Replies)
Hi,
I am having a text file with the following contents
###########
File1
###########
some
page1.txt
text
page.txt
When I sort this file on Red Hat 5, then I get the following output
###########
File1
###########
page1.txt
page.txt
some (3 Replies)
Hi Folks -
I have this file that looks like this:
outbox/logs/Client_1042.log
outbox/logs/Client_941.log
outbox/logs/Client_942.log
outbox/logs/Client_943.log
outbox/logs/Client_944.log
And this is my code:
#!/bin/bash
_OUTBOX_BIN="outbox/logs/"
_NAME="Client"
_TEMP="temp.txt"... (9 Replies)
Could you please advise on the following: I have two space-delimited files with 9 and 10 columns, respectively, with exactly the same values in column 1. However, the order of column 1 differs between the two files, so I want to sort both files by column 1, so that I can align them and... (6 Replies)
Discussion started by: aberg
6 Replies
LEARN ABOUT LINUX
script
script(5) Files script(5)NAME
script - Boot script
DESCRIPTION
The boot script describes how the Erlang runtime system is started. It contains instructions on which code to load and which processes and
applications to start.
The command erl -boot Name starts the system with a boot file called Name.boot , which is generated from the Name.script file, using sys-
tools:script2boot/1 .
The .script file is generated by systools from a .rel file and .app files.
FILE SYNTAX
The boot script is stored in a file with the extension .script
The file has the following syntax:
{script, {Name, Vsn},
[
{progress, loading},
{preLoaded, [Mod1, Mod2, ...]},
{path, [Dir1,"$ROOT/Dir",...]}.
{primLoad, [Mod1, Mod2, ...]},
...
{kernel_load_completed},
{progress, loaded},
{kernelProcess, Name, {Mod, Func, Args}},
...
{apply, {Mod, Func, Args}},
...
{progress, started}]}.
* Name = string() defines the name of the system.
* Vsn = string() defines the version of the system.
* {progress, Term} sets the "progress" of the initialization program. The function init:get_status() returns the current value of the
progress, which is {InternalStatus,Term} .
* {path, [Dir]} where Dir is a string. This argument sets the load path of the system to [Dir] . The load path used to load modules is
obtained from the initial load path, which is given in the script file, together with any path flags which were supplied in the command
line arguments. The command line arguments modify the path as follows:
* -pa Dir1 Dir2 ... DirN adds the directories Dir1, Dir2, ..., DirN to the front of the initial load path.
* -pz Dir1 Dir2 ... DirN adds the directories Dir1, Dir2, ..., DirN to the end of the initial load path.
* -path Dir1 Dir2 ... DirN defines a set of directories Dir1, Dir2, ..., DirN which replaces the search path given in the script file.
Directory names in the path are interpreted as follows:
* Directory names starting with / are assumed to be absolute path names.
* Directory names not starting with / are assumed to be relative the current working directory.
* The special $ROOT variable can only be used in the script, not as a command line argument. The given directory is relative the
Erlang installation directory.
* {primLoad, [Mod]} loads the modules [Mod] from the directories specified in Path . The script interpreter fetches the appropriate mod-
ule by calling the function erl_prim_loader:get_file(Mod) . A fatal error which terminates the system will occur if the module cannot
be located.
* {kernel_load_completed} indicates that all modules which must be loaded before any processes are started are loaded. In interactive
mode, all {primLoad,[Mod]} commands interpreted after this command are ignored, and these modules are loaded on demand. In embedded
mode, kernel_load_completed is ignored, and all modules are loaded during system start.
* {kernelProcess, Name, {Mod, Func, Args}} starts a "kernel process". The kernel process Name is started by evaluating apply(Mod, Func,
Args) which is expected to return {ok, Pid} or ignore . The init process monitors the behaviour of Pid and terminates the system if Pid
dies. Kernel processes are key components of the runtime system. Users do not normally add new kernel processes.
* {apply, {Mod, Func, Args}} . The init process simply evaluates apply(Mod, Func, Args) . The system terminates if this results in an
error. The boot procedure hangs if this function never returns.
Note:
In the interactive system the code loader provides demand driven code loading, but in the embedded system the code loader loads all the
code immediately. The same version of code is used in both cases. The code server calls init:get_argument(mode) to find out if it should
run in demand mode, or non-demand driven mode.
SEE ALSO systools(3erl)Ericsson AB sasl 2.1.9.3 script(5)