Sponsored Content
Full Discussion: One liners, quick rant...
The Lounge What is on Your Mind? One liners, quick rant... Post 302977420 by Scrutinizer on Monday 18th of July 2016 03:50:17 AM
Old 07-18-2016
I think one-liners tend to have a bad rep for the wrong reasons.

One-liners are typically used for programming on the command line, where a single line is your real estate. They are very useful as one-off, terse and personal small scripts for an ad-hoc parsing result, for example for general information, problem determination or security forensics. Developing such a small script is usually a lot quicker than editing a file, exiting, running it, re-editing, etc... Typically sysadmins use one-liners a lot for this purpose.

Once a one liner is working and if it proves to be useful for multiple occasions, then it can be turned into a script in a file and then vertical real estate can be used and short names can be replaced by mnemonic names and comments can be added for maintainability and it can be made fool-proof with error conditions. In a script file one-liners are to be a avoided.

These are just two different types of application.

If a one-liner is posted here, it shows the principle or mechanism that can be used to tackle a problem or create an application. The user is free to use it and turn it into a fully maintainable script if he so chooses, or execute it as such on the command line and get his/her result..

Last edited by Scrutinizer; 07-18-2016 at 06:31 AM..
This User Gave Thanks to Scrutinizer For This Post:
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Where can I rant?

First of all, apologies to the admins for not reading the rules totally and missing the bit about ranting off about other OSs. But that raises a question. Where do you go to have a good rant, to vent your disgust at various corporations and thier hideous behaviour? :confused: (2 Replies)
Discussion started by: u6ik
2 Replies

2. Shell Programming and Scripting

awk - one liners

Guys, I have a requirement like this. A file has >5K records always. Separated by "|", it has 30 fields for each line. In some lines, I am getting an odd field. say, the 15th field is supposed to be 2 characters but comes in as >2. In this case, for resolving this I need to copy the value of... (6 Replies)
Discussion started by: PikK45
6 Replies

3. What is on Your Mind?

Those simple one liners

I wanted to say LOL and punch my face when I saw post#11 (where Don_Cragun even reduced the string manipulation with a simple regex) in the thread https://www.unix.com/shell-programming-scripting/220553-add-0-start-filename-2.html I mean, when things can be done with just a one liner, sometimes I... (6 Replies)
Discussion started by: ahamed101
6 Replies

4. What is on Your Mind?

A rant...

Hi guys... (Apologies for any typos etc...) This is basically a rant. I have been doing kids level projects and writing code to suit since around 1982, for the uProfessor, for the Sinclair Spectrum and later for the QL, IBM-XT in MS-DOS and after that for a 386DX40 up to Windows 95, until I... (3 Replies)
Discussion started by: wisecracker
3 Replies
IO
::FILE=IO(0X103FE58)(8) User Contributed Perl Documentation IO::FILE=IO(0X103FE58)(8) NAME
send-uucp - Send Usenet articles via UUCP SYNOPSIS
send-uucp [SITE ...] DESCRIPTION
The send-uucp program processes batch files written by innd(8) to send Usenet articles to UUCP sites. It reads a configuration file to control how it behaves with various sites. Normally, it's run periodically out of cron to put together batches and send them to remote UUCP sites. OPTIONS
Any arguments provided to the program are interpreted as a list of sites specfied in send-uucp.cf for which batches should be generated. If no arguments are supplied then batches will be generated for all sites listed in that configuration file. CONFIGURATION
The sites to which articles are to be sent must be configured in the configuration file send-uucp.cf. Each site is specified with a line of the form: site[:host] [compressor [maxsize [batchtime]]] site The news site name being configured. This must match a site name from newsfeeds(5). host The UUCP host name to which batches should be sent for this site. If omitted, the news site name will be used as the UUCP host name. compressor The compression method to use for batches. This should be one of compress, gzip or none. Arguments for the compression command may be specified by using "_" instead of spaces. For example, "gzip_-9". The default value is "compress". maxsize The maximum size of a single batch before compression. The default value is 500,000 bytes. batchtime A comma separated list of hours during which batches should be generated for a given site. When send-uucp runs, a site will only be processed if the current hour matches one of the hours in batchtime. The default is no limitation on when to generate batches. Fields are seperated by spaces and only the site name needs to be specified, with defaults being used for unspecified values. If the first character on a line is a "#" then the rest of the line is ignored. EXAMPLE
Here is an example send-uucp.cf configuration file: zoetermeer gzip 1048576 5,18,22 hoofddorp gzip 1048576 5,18,22 pa3ebv gzip 1048576 5,18,22 drinkel gzip 1048576 5,6,18,20,22,0,2 manhole compress 1048576 5,18,22 owl compress 1048576 able This defines seven UUCP sites. The first four use gzip compression and the last three use compress. The first six use a batch size of 1MB, and the last site (able) uses the default of 500,000 bytes. The zoetermeer, hoofddorp, pa3ebv, and manhole sites will only have batches generated for them during the hours of 05:00, 18:00, and 22:00, and the drinkel site will only have batches generated during those hours and 20:00, 00:00, and 02:00. There are no restrictions on when batches will be generated for owl or able. FILES
pathetc/send-uucp.cf Configuration file specifying a list of sites to be processed. NOTES
The usual flags used for a UUCP feed in the newsfeeds file are "Tf,Wfb". SEE ALSO
innd(8), newsfeeds(5), uucp(8) AUTHOR
This program was originally written by Edvard Tuinder <ed@elm.net> and then maintained and extended by Miquel van Smoorenburg <miquels@cistron.nl>. Marco d'Itri <md@linux.it> cleaned up the code for inclusion in INN. This manual page was written by Mark Brown <broonie@sirena.org.uk>. perl v5.14.2 2012-06-29 IO::FILE=IO(0X103FE58)(8)
All times are GMT -4. The time now is 07:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy