Sponsored Content
Top Forums UNIX for Dummies Questions & Answers **HELP** how to do a listing of dirs and all sub dirs only Post 302547764 by bbraml on Tuesday 16th of August 2011 01:53:28 PM
Old 08-16-2011
awesome, thanks!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

dirs & colors

hi @all question from an absolute beginner: I want directory listings to be displayed with different colors... what do I have to do and where can I find the settings? thx (4 Replies)
Discussion started by: tk876
4 Replies

2. UNIX for Dummies Questions & Answers

I need to ls all files in 4-6 deep dirs

I need to print to file , a listing of all files below a certain directory. Example: I need to print to file a listing of all files below the etc dir (including the subdirectories) with their full path. Any ideas on how to do this with one command. Or is this something I need to do on all... (4 Replies)
Discussion started by: gforty
4 Replies

3. UNIX for Dummies Questions & Answers

Combining Two Dirs

I have two Directories, foo and foobar. I want to combine the contents of foo into foobar. There is probably a simple command for this, but I have yet to find it. Thanks in advance, Robert (2 Replies)
Discussion started by: Phobos
2 Replies

4. UNIX for Dummies Questions & Answers

Making dirs in a partition

I am setting up a design tools server on a machine running Solaris9. I want to setup a partition that contains a number of design tools. If I go to / and type mkdir "tools" then I am on the root partition. How do I get "/tools" to be on a separate partition? (I also have the same problem... (2 Replies)
Discussion started by: smo59
2 Replies

5. Shell Programming and Scripting

how to synchronize different dirs

I have 4 directory Dir1 file1 file2 file3 file4 Dir2 file3 file5 file6 file8 Dir3 file1 file2 file6 file9 file10 Dir4 file3 file6 file12 file15 and all the 4 dirs are having couple of files. Few of the files are common to other directory/ies and few... (1 Reply)
Discussion started by: reldb
1 Replies

6. Shell Programming and Scripting

monitoring dirs

Hi there, Presently using du -ks and storing all directory summaries manually. Is there any other way or easier way to accomplish monitoring directories and check everyday/week for updates on particular dirs that I am interested in. Automation of this functionality maybe? (1 Reply)
Discussion started by: da-seot
1 Replies

7. Solaris

Why are so many dirs used in solaris hierarchy?

Hi all, I would like to know the difference between the different dir structures present in solaris!!! Meaning what does /usr contain, /etc ,/opt/ ,so on... I know what /usr and /etc are used for. But why are /opt /bin /sbin /var and many more that i have missed I would appreciate if... (1 Reply)
Discussion started by: wrapster
1 Replies

8. UNIX for Dummies Questions & Answers

Move directory + sub dirs

Hi Im quite new at this so I will try to explain what need to do and I hope you can give me some pointers & tips. On this scenario I have 3 users AriStar Userno1 Userno2 Userno1 has one directory (with sub dirs), all directories have certain files with different restrictions. What I... (1 Reply)
Discussion started by: AriStar
1 Replies

9. Emergency UNIX and Linux Support

df command for listing 90% + dirs and hostname condition

df -k | grep -v dcs |grep -v Filesystem| awk -F" " '{if(substr($5,0,length($5)-1)>87)print $5" " $6}' >> sms.txt 1) Is it the correct way to list all the filesystems > 90% 2) Is there any way to print hostname in this command ? The hostname should get printed in sms.txt file only when there... (9 Replies)
Discussion started by: ajaypatil_am
9 Replies

10. Emergency UNIX and Linux Support

find all the dirs starting with particular name

Hi Experts, I want to find all the dirs , subdirs on the sever which start with "sr". Can anyone let me know command for the same. find . -type d -name sr* I tried this but it is not working. Thanks, Ajay (4 Replies)
Discussion started by: ajaypatil_am
4 Replies
Config::INI::Writer(3pm)				User Contributed Perl Documentation				  Config::INI::Writer(3pm)

NAME
Config::INI::Writer - a subclassable .ini-file emitter VERSION
version 0.019 SYNOPSIS
If <$hash> contains: { '_' => { admin => 'rjbs' }, rjbs => { awesome => 'yes', height => q{5' 10"}, }, mj => { awesome => 'totally', height => '23"', }, } Then when your program contains: Config::INI::Writer->write_file($hash, 'family.ini'); family.ini will contains: admin = rjbs [rjbs] awesome = yes height = 5' 10" [mj] awesome = totally height = 23" DESCRIPTION
Config::INI::Writer is yet another config module implementing yet another slightly different take on the undeniably easy to read ".ini" file format. Its default behavior is quite similar to that of Config::Tiny, on which it is based. The chief difference is that Config::INI::Writer is designed to be subclassed to allow for side-effects and self-reconfiguration to occur during the course of reading its input. METHODS FOR WRITING CONFIG
There are three writer methods, "write_string", "write_file", and "write_handle". The first two are implemented in terms of the third. It iterates over a collection of data, emitting lines to the filehandle as it goes. The lines are generated by events produced by iterating over the data. Those events are detailed below in the "METHODS FOR SUBCLASSING" section. The given data should be a hashref of hashrefs: { section_name_1 => { prop1 => 'value1', prop2 => 'value2' }, section_name_2 => ... } ...or an arrayref of section name and arrayref pairs: [ section_name_1 => [ prop1 => 'value1', prop2 => 'value2' ], section_name_2 => ... ] ...or a combination of those: [ section_name_1 => { prop1 => 'value1', prop2 => 'value2' }, section_name_2 => [ prop3 => 'value3', prop4 => 'value4' ], section_name_3 => ... ] All the reader methods throw an exception when they encounter an error. write_file Config::INI::Writer->write_file($input, $filename); This method writes out the configuration represented by $data to the file named by $filename. If a file by that name exists, it is overwritten. This method will either succeed or raise an exception. (Its return value is not defined.) write_string my $string = Config::INI::Writer->write_string($input); This method returns a string containing the INI content describing the given data. write_handle Config::INI::Writer->write_handle($input, $handle); This method writes the data in $data to the IO::Handle-like object in $handle. This method should either succeed or throw an exception. METHODS FOR SUBCLASSING
These are the methods you need to understand and possibly change when subclassing Config::INI::Reader to handle a different format of input. preprocess_input my $processed_input = $writer->preprocess_input($input_data); This method is called to ensure that the data given to the "write_*" methods are in a canonical form for processing and emitting. The default implementation converts hashrefs to arrayrefs and, if the input is a hashref, moves the "starting_section" to the beginning of the produced arrayref. In other words, given: { section_1 => { a => 1, b => 2 }, section_2 => { c => 3, c => 4 }, _ => { d => 5, e => 6 }, } This method will return: [ _ => [ d => 5, e => 6 ], section_2 => [ c => 3, c => 4 ], section_1 => [ a => 1, b => 2 ], ] The only guaranteed ordering when hashes are provided as input is that the starting section will appear first. validate_input $writer->validate_input($input); This method is called on the input data once they've been preprocessed by "preprocess_input". It ensures that the processed input is structurally sound before beginning to output it. For example, it ensures that no property is ever assigned more than once in a given section. This method either raises an exception or it doesn't. change_section $writer->change_section($section_name); This method is called each time a new section is going to be written out. If the same section appears twice in a row in the input, this method will still be called between instances of that section. In other words, given this input: [ section_1 => [ a => 1 ], section_1 => [ b => 2 ], ] "change_section" will be called twice: once before the first "section_1" and once before the second "section_1". current_section $writer->current_section This method returns the section currently being written out. finish_section $writer->finish_section This method is called after all of the current section's properties have been written. done_sections my @names = $writer->done_sections; This method returns a list of all sections that have been written out and finished. The fact that a section name is returned by "done_sections" does not mean that there will be no more data for that section, but that at least one entire set of data has been written out for it. stringify_section my $string = $writer->stringify_section($props); This method returns a string assigning all the properties set in the given data. This still will include the section header, if needed. (The only case in which it is not needed is when the "explicit_starting_header" method returns false, no other sections have been done, and the section about to be stringified is the "starting_section". This method is implemented in terms of "stringify_section_header" and "stringify_section_data". stringify_section_data my $string = $writer->stringify_section_data($props) This method returns a string containing a series of lines, each containing a value assignment for the given properties. stringify_value_assignment my $string = $writer->stringify_value_assignment($name => $value); This method returns a string that assigns a value to a named property. If the value is undefined, an empty string is returned. stringify_value my $string = $writer->stringify_value($value); This method returns the string that will represent the given value in a property assignment. stringify_section_header my $string = $writer->stringify_section_header($section_name); This method returns the string (a line) that represents the given section name. Basically, this returns: [section_name] starting_section This method returns the name of the starting section. If this section appears first (as it will, when given a hashref as input) and if "explicit_starting_header" returns false, its section header can be omitted. explicit_starting_header If this method returns true (which it does not, by default), then the section header for the starting section will be emitted, even if it appears first. new my $reader = Config::INI::Writer->new; This method returns a new writer. This generally does not need to be called by anything but the various "write_*" methods, which create a writer object only ephemerally. AUTHOR
Ricardo Signes <rjbs@cpan.org> COPYRIGHT AND LICENSE
This software is copyright (c) 2007 by Ricardo Signes. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.14.2 2011-12-15 Config::INI::Writer(3pm)
All times are GMT -4. The time now is 08:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy