How do you display the script command for a particular output result? Is there an editor that will allow for an echo or sysout of the script that causes an output result? We have hundreds of lines in the script, which we would like to see along with the output, and don't want to have to put in... (5 Replies)
Hello,
I've just finished my first script (about displaying open ports on the computer and who opened them) and everything is fine with it but I want to style it a little bit just for the sake of learning how to do this.
What I want to do is make the display like the one of ps, for example,... (6 Replies)
I'm writing a script to analyze the logs of an smtp relay machine and I'd like the final output to be displayed in columns showing results from the previous day, week, month, and 45 days. The problem I'm running into is that I can't figure out how to display the columns neatly so there is no... (1 Reply)
Hi
I am formatting informix isql output(vertical) to horizontal format. Suppose I have the following content in the flat file from isql output -
item_nbr 0
usfn_label Subscriber Class
usfn_name SBCLASS
usfn_value bl5
item_nbr 1
usfn_label Switch Name
usfn_name switchName... (2 Replies)
Hi all,
Below is my shell script that calls a stored procedure(with output parameter)
I have tried executing this script but it doesn't display the output parameter value. Can anyone help me ? :(
#!/bin/bash
###############################################################################... (7 Replies)
Hi All,
I have result log file which looks like this (below): from the content need to consolidate the result and put it in tabular form
1). Intercomponents Checking
Passed: All Server are passed.
======================================================================
2). OS version Checking... (9 Replies)
Hi All,
please help to achieve the desired output
Example: I have a file which contains the below data
empname
robert
empid
787
design
consultant
empname
alex
empid
898
design
advocate
Desired output should be
empname empid design
robert 787 consultant (19 Replies)
Discussion started by: rocky2013
19 Replies
LEARN ABOUT DEBIAN
go-packages
GO-PACKAGES(7) Miscellaneous Information Manual GO-PACKAGES(7)NAME
go - tool for managing Go source code
DESCRIPTION
Many commands apply to a set of packages:
go action [packages]
Usually, [packages] is a list of import paths.
An import path that is a rooted path or that begins with a . or .. element is interpreted as a file system path and denotes the package in
that directory.
Otherwise, the import path P denotes the package found in the directory DIR/src/P for some DIR listed in the GOPATH environment variable
(see 'go help gopath').
If no import paths are given, the action applies to the package in the current directory.
The special import path "all" expands to all package directories found in all the GOPATH trees. For example, 'go list all' lists all the
packages on the local system.
The special import path "std" is like all but expands to just the packages in the standard Go library.
An import path is a pattern if it includes one or more "..." wildcards, each of which can match any string, including the empty string and
strings containing slashes. Such a pattern expands to all package directories found in the GOPATH trees with names matching the patterns.
As a special case, x/... matches x as well as x's subdirectories. For example, net/... expands to net and packages in its subdirectories.
An import path can also name a package to be downloaded from a remote repository. Run 'go help remote' for details.
Every package in a program must have a unique import path. By convention, this is arranged by starting each path with a unique prefix that
belongs to you. For example, paths used internally at Google all begin with 'google', and paths denoting remote repositories begin with
the path to the code, such as 'code.google.com/p/project'.
As a special case, if the package list is a list of .go files from a single directory, the command is applied to a single synthesized pack-
age made up of exactly those files, ignoring any build constraints in those files and ignoring any other files in the directory.
AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).
2012-05-13 GO-PACKAGES(7)