05-01-2015
File or Folder Efficiency?
I've got this program set up so that it creates files whose unique names specify the jobs their contents describe. In order to retrieve the information inside those files, I have to do a "grep" and awk or sed to extract it. I've just assumed that making a directory with that unique name that contains individual files for each type of information rather than lines inside the files I'm referring to would be wasteful of storage and slower to retrieve. I realize now that I've only assumed this and was not sure.
How would the method of having a thousand or so directories with individual files inside each to contain several types of information compare to my current method of files with those same unique names containing fields to be extracted from those files?
Would getting the file inside a directory be less resource/time intensive than having to extract each piece of info from a single file with that unique name?
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
how efficient is it, and how practical is it to call outside programs in a shell script (bash) for small tasks?
for example, say i have a script that might preform many tasks, one of those tasks may require root access; rather than implementing inside the script a method to use su or sudo to... (11 Replies)
Discussion started by: norsk hedensk
11 Replies
2. Shell Programming and Scripting
Oracle procedure create files on UNIX folder on a regular basis. I need to FTP files onto windows server and place the files, based on their name, in the corresponding folders. File name is as follows: ccyymmddfoldernamefile.txt; Folder Name length could be of any size; however, the prefix and... (3 Replies)
Discussion started by: MeganP
3 Replies
3. Shell Programming and Scripting
I have the following Perl snippet:
# get datetime
@dt = gmtime();
$strdate = 1900 + $dt . addleadingzero(++$dt) . addleadingzero($dt) . addleadingzero($dt) . addleadingzero($dt) . addleadingzero($dt);
# write to file
$outfile = $strdate . ".txt";
getstore($url, $outfile) or die "Error:... (3 Replies)
Discussion started by: figaro
3 Replies
4. Shell Programming and Scripting
Hi,
I have a requirement to move a file from one folder(a) to another folder(b) only when folder (b) have a write permission. Folder permission is 755
If the permission is otherthan 755 we need to come out of the loop
I will appreciate your help
Thanks
Soll (1 Reply)
Discussion started by: sollins
1 Replies
5. Shell Programming and Scripting
This is the file structure:
DESKTOP/Root of Photo Folders/Folder1qweqwasdfsd/*jpg
DESKTOP/Root of Photo Folders/Folder2asdasdasd/*jpg
DESKTOP/Root of Photo Folders/Folder3asdadfhgasdf/*jpg
DESKTOP/Root of Photo Folders/Folder4qwetwdfsdfg/*jpg
DESKTOP/Root of Photo... (4 Replies)
Discussion started by: guptaxpn
4 Replies
6. Shell Programming and Scripting
Hi !! I've finished an awk exercise. Here it is:
#!/bin/bash
function calcula
{
# Imprimimos el mayor tamaño de fichero
ls -l $1 | awk '
BEGIN {
max = $5; # Inicializamos la variable que nos guardará el máximo con el tamaño del primer archivo
}
{
if ($5 > max){ #... (8 Replies)
Discussion started by: Phass
8 Replies
7. Shell Programming and Scripting
Hello Everyone!
I am a newbie. I'd like to get key lines from a big txt file by Reg Exp, The file is nearly 22MB.
GREP or SED?which may be the best choice,more efficient way?
or any other best practise?
Thank you in advance.
Ever:) (5 Replies)
Discussion started by: ever
5 Replies
8. Shell Programming and Scripting
Hi all,
let me explain my requirments
i am having 5 folder with different name for eg) abc , cdf , efd, rtg, ead
each 5 folders contain 15 files
i want to move 10 files to some other folder, remain 5 files should be there in the same folder.
give me some suggestion on this. (6 Replies)
Discussion started by: natraj005
6 Replies
9. UNIX for Advanced & Expert Users
Hello, there.
I'm a new beginner to Linux kernel and curious about its memory management.
When multiple applications apply for memory space at the same time, how Linux kernel solve the resource contending problem for high performance?
I have known that there is a buddy system for allocating and... (4 Replies)
Discussion started by: blackwall
4 Replies
LEARN ABOUT POSIX
macstream
MACSTREAM(1) General Commands Manual MACSTREAM(1)
NAME
macstream - Convert a series of files to a MacBinary stream
SYNOPSIS
macstream [ - options ] files
DESCRIPTION
macstream takes the files specified in files and combines them to a MacBinary stream on standard output subject to the options specified.
If files also specifies directories they are followed recursively, and all files found will be put in the MacBinary stream, together with
directory information.
OPTIONS
In the absence of any options, macstream takes the specified files and silently combines them to a MacBinary stream, writing the result to
standard output. Directories named in files are followed recursively, all files found will be put in the MacBinary stream, together with
directory information. Files are assumed to be in MacBinary format. However, if the filename ends with .info the file is assumed to be
the info fork of a MacIntosh file split amongst more than one file. In that case the files with .data and .rsrc extension are also read
(if present). Also, if the info fork is mentioned in the parameter list, the names of data and resource forks can also be mentioned, but
those will be ignored (this is to allow wild-card expansion by the shell.) Further, if some form of AppleShare is supported by the
installed program, and if the current directory, or one of the directories found during recursive processing, is a directory in the format
of the supported version of AppleShare, those files will be handled according to the properties of AppleShare.
-r No intelligent file-processing is performed; all files named are assumed to be plain resource files, and are written as MacIntosh
resource files with creator "RSED" and type "RSRC", unless another creator and/or type are specified.
-d No intelligent file-processing is performed; all files named are assumed to be plain data files, and are written as MacIntosh data
files with creator "MACA" and type "TEXT", unless another creator and/or type are specified.
-u As -d, but the codes for CR and LF are interchanged.
-U Is a synonym for -u.
-c creator
Defines the creator name to be used if one of the previous options is specified.
-t type
Defines the type name to be used if one of the previous options is specified.
-l List every file and directory processed.
-i Do not output files, give information only (implies -l.)
-q Ask the user for every file/directory whether it should be visited (implies -l.)
-V Gives the patchlevel of the program, and other information. Other options are ignored and the program quits immediately.
-H Give short information about the options. Other options are ignored and the program quits immediately.
BUGS
As this is a beta release, there may still be some problems.
SEE ALSO
macutil(1)
AUTHOR
Dik T. Winter, CWI, Amsterdam, The Netherlands (dik@cwi.nl)
3rd Berkeley Distribution October 22, 1992 MACSTREAM(1)