Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I have a question that I believe is perl enough oriented to justify posting (and I'm not looking for an answer, but more for advice).

Up until recently, I've had to lead my perl/web/programming life in an environment that offered what many would consider "crippled shell access". Now that I have full/typical access, my administrative life has changed ...

For years, I watched and noted as others talked about "one-liners", knowing that I was unable to take advantage of this aspect of box management. Now that the one-liner option is available to me, I'm looking for advice on resources that will bring me up to speed on this new tool.

Many times, I've looked at posts that offer one-liners, and my jaw drops at the amount of work that is performed from just one line of a command. But just about every time my jaw drops, I also realize that I have no clue how to interpret the one-liner. Resources that help me understand these types of one-liners is what I'm looking for.

I figure that since system calls like:

system "(nice /usr/local/bin/zip -r -q $storage_path $copy_path)";
are part of how I'd use the one-liners, my question qualifies as an appropriate perl question for the Monks.

Any and all suggestions are appreciated.


In reply to Resource for command line "one-liner" interpretation by Hagbone

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others wandering the Monastery: (5)
As of 2024-04-25 10:50 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found