Sponsored Content
Full Discussion: Prize of being an Admin
The Lounge War Stories Prize of being an Admin Post 302596932 by admin_xor on Wednesday 8th of February 2012 04:47:29 PM
Old 02-08-2012
Excellent point, bartus11.
Being a naive and over-enthusiastic one, I was only thinking about the problem on hand, not about the consequences. Looks like I have to work on so many things!! Smilie
 

6 More Discussions You Might Find Interesting

1. Solaris

fresh admin

hi everybody i'm just recreuted as UNIX system admin... please tell me from where do i have to begin... best regards (8 Replies)
Discussion started by: hmaiida
8 Replies

2. Solaris

Tape Admin

Tape: Need tape library help please. Need to configure a remote admin card in the L100. Anything helpful.....thxs (2 Replies)
Discussion started by: uwinix77
2 Replies

3. Post Here to Contact Site Administrators and Moderators

note for admin

i left a message for admin in the wrong thread.. it is in the what is on your mind thread since i can't move it or delete it.. i thought I would mention that I meant it to be in this thread.. sorry about the mistake.. thanx for your patience moxxx68 (3 Replies)
Discussion started by: moxxx68
3 Replies

4. What is on Your Mind?

Windows Admin switching to *nix Admin

I'm currently a Windows admin and have wanted to jump ship to the *nix side for a while now. I've been studying both through an lpic level 1 manual as I have time (focusing on debian), and a solaris 10 cert book. The problem is I only have a handful of hours a week to study, and my current job... (3 Replies)
Discussion started by: bobwilson
3 Replies

5. War Stories

Prize of being an Admin - Part 2

I was reading this thread of admin_xor Prize of being an Admin and thought will share this experience of mine which is kind of opposite to what he did - I didn't tell anybody what happened :D We were porting one of the subsystem from Solaris to Linux. As part of that we developed many wrapper... (23 Replies)
Discussion started by: ahamed101
23 Replies

6. What is on Your Mind?

Regarding Admin life either as DBA or UNIX Linux admin

I am planning to choose my career as Unix/Linux Admin or a DBA. But I have come to know from forums and few admins like the job will be 24/7. I have few questions on that. Can we get "DAY" shifts in any one of the admin Job ? Can't we have shift timings in any company ? Eventhough the... (7 Replies)
Discussion started by: Jacktts
7 Replies
divert(3)							     EN Tools								 divert(3)

NAME
Divert - Text Diversion Filter SYNOPSIS
divert [-o outputfile] [-q] [-v] [inputfile] DESCRIPTION
The divert program reads inputfile or from "stdin" and applies a 2-pass diversion filter to its contents. In pass 1 all diversion locations are accumulated and in pass 2 these locations are recursively expanded at their dump positions. The diversion filter is controlled by directives found in the input data: {#NAME#} (or <<NAME>>) This defines the dump position of the location NAME. All accumulated data which finally has to been diverted to NAME is inserted at this data position. Notice: the final data of a location NAME has not to be known at this point, because the expansion of such location dumps are done in pass 2. You can also dump a location more than once, but the contents is always the same, independent of the data position where the location dump tag stays. The NAME can be any symbolic name matching "[a-zA-Z][a-zA-Z0-9_]*". {#[!]NAME[!]#: (or ..[!]NAME[!]>>) This enters the location NAME (or diverts the data flow to it, hence the name for this filter). In other words: the data flow now goes on at location NAME. All following data (up to end of file or the next location leave tag) gets appended to location NAME. You can nest diversions by entering other locations at any point, because the locations are remembered on a stack. The default entered location is named ``"main"''. The top most location is named ``"null"'' which neither can be entered nor leaved explicitly. But of course the ``"null"'' diversion can be manually dumped, for instance when using it for error messages. There are two special features for diverting data which are controlled by the ""!"" characters preceding or following the NAME identifier: !NAME This sets the data flow position to the begin of location NAME, i.e. it actually discards the current (already diverted) contents of location NAME before entering it. Use this to overwrite a locations contents. NAME! This marks this location entry as overwritable, i.e. it enters location NAME but when the corresponding leave tag is found, the data-flow position for NAME gets automatically reset to its begin. Use this if you want to set the default contents for a location which only gets used if no other diversions occur to it (because any following diversions to this location will be overwrite the contents). This feature is usually used for a template scheme. !NAME! Just the combination of the above two features. Use this to both discard the current contents of location NAME and set a new default for it. :#[NAME]#} (or <<[NAME]..) This leaves the current location, i.e. enters again the location which was active when this location was entered. There is no need to leave all locations at the end of the input data. All still entered locations are automatically left at end of file because this is essential for a template scheme. Notice that there are two ways of using (and thinking) about the filtering mechanism this program provides: Macro Mechanism This is the "predefined" way of thinking here. Use it like this: FOO {#BAR#} QUUX {#BAR#: BAZ :##} Here you are thinking of the mechanism as a macro mechanism where you expand a macro at one data position while you define it via begin and end tags. Diversion Mechanism This is the alternative way of thinking. Use it like this: FOO <<BAR>> QUUX ..BAR>> BAZ <<.. In other words: You are thinking of the mechanism as a diversion mechanism where you dump a location at one data position while you divert to it by entering end leaving the location (here BAR) at other positions. You can even intermix both ways because both are just alternative syntax variants which are treated the same. EXAMPLE
{#HEAD#} {#BODY#} {#FOOT#} {#FOOT#: Quux :##} {#BODY#: Bar :##} {#HEAD#: Foo :##} OPTIONS
-o outputfile This redirects the output to outputfile. Usually the output will be send to stdout if no such option is specified or outputfile is ``"-"''. -q This sets quiet mode where warnings are suppressed. -v This sets verbose mode where some processing information will be given on stderr. AUTHORS
Ralf S. Engelschall rse@engelschall.com www.engelschall.com Denis Barbier barbier@engelschall.com EN Tools 2014-04-16 divert(3)
All times are GMT -4. The time now is 11:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy