I ran into this issue and thanks to various postings in various forums, was
able to figure out the solution but didn't see one posting that laid the
whole issue out cleanly. So thought the following might help others ...
------------------------------------------------------------------------... (2 Replies)
Hi Experts,
I have written simple perl script, which assign the value to variable and print it. Following is the script:
$ cat 3.pl
#!/usr/bin/env ksh
#!/usr/bin/perl
print "Hello World";
$iputlne = 34;
print $iputlne;
The error output is:
$ /usr/bin/env perl 3.pl
Hello World... (9 Replies)
Hi everyone,
when executing this command in unix:
echo "WM7 Fatal Alerts:", $(cat query1.txt) > a.csvIt works fine, but running this command in a shell script gives an error saying that there's a syntax error.
here is content of my script:
tdbsrvr$ vi hc.sh
"hc.sh" 22 lines, 509... (4 Replies)
I have written a simple script to show battery life remaining. I would like to be able to quickly view it with a predefined keybinding or launcher.
xterm -e scriptname should do the trick but the xterm closes when the script finishes, not giving me chance to read the output. How can I keep... (3 Replies)
Hi,
I am trying to configure SEC - Simple Event Correlator to analyze the logs.
Just wondering if any of you have used this before? If yes, can you help by showing few of the rules you created?
Thanks. (1 Reply)
Hi,
I need to run a script whenever a user logs in to HP-UX unix server.
Please let me know how can i implement this.
I need to run this script on login for all users starting with 'X' ( x110,x112,x13545, etc).
Thanks a lot. (2 Replies)
Hi All,
How can i run a single command on multiple servers with or without giving credentials.
I have a file(servers.txt) which has got list of servers and i want to run a command lsb_release -dr on all these servers and get output of those servers against each server.
I tried below code... (9 Replies)
Discussion started by: darling
9 Replies
LEARN ABOUT PHP
systemd-cat
SYSTEMD-CAT(1) systemd-cat SYSTEMD-CAT(1)NAME
systemd-cat - Connect a pipeline or program's output with the journal
SYNOPSIS
systemd-cat [OPTIONS...] [COMMAND] [ARGUMENTS...]
systemd-cat [OPTIONS...]
DESCRIPTION
systemd-cat may be used to connect the standard input and output of a process to the journal, or as a filter tool in a shell pipeline to
pass the output the previous pipeline element generates to the journal.
If no parameter is passed, systemd-cat will write everything it reads from standard input (stdin) to the journal.
If parameters are passed, they are executed as command line with standard output (stdout) and standard error output (stderr) connected to
the journal, so that all it writes is stored in the journal.
OPTIONS
The following options are understood:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
-t, --identifier=
Specify a short string that is used to identify the logging tool. If not specified, no identification string is written to the journal.
-p, --priority=
Specify the default priority level for the logged messages. Pass one of "emerg", "alert", "crit", "err", "warning", "notice", "info",
"debug", or a value between 0 and 7 (corresponding to the same named levels). These priority values are the same as defined by
syslog(3). Defaults to "info". Note that this simply controls the default, individual lines may be logged with different levels if they
are prefixed accordingly. For details, see --level-prefix= below.
--level-prefix=
Controls whether lines read are parsed for syslog priority level prefixes. If enabled (the default), a line prefixed with a priority
prefix such as "<5>" is logged at priority 5 ("notice"), and similar for the other priority levels. Takes a boolean argument.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
EXAMPLES
Example 1. Invoke a program
This calls /bin/ls with standard output and error connected to the journal:
# systemd-cat ls
Example 2. Usage in a shell pipeline
This builds a shell pipeline also invoking /bin/ls and writes the output it generates to the journal:
# ls | systemd-cat
Even though the two examples have very similar effects the first is preferable since only one process is running at a time, and both stdout
and stderr are captured while in the second example, only stdout is captured.
SEE ALSO systemd(1), systemctl(1), logger(1)systemd 237SYSTEMD-CAT(1)