LIBXO(3) BSD Library Functions Manual LIBXO(3)NAME
xo_err -- emit errors and warnings in multiple formats
LIBRARY
library ``libxo''
SYNOPSIS
#include <libxo/xo.h>
void
xo_warn(const char *fmt, ...);
void
xo_warnx(const char *fmt, ...);
void
xo_warn_c(int code, const char *fmt, ...);
void
xo_warn_hc(xo_handle_t *xop, int code, const char *fmt, ...);
void
xo_err(int eval, const char *fmt, ...);
void
xo_errc(int eval, int code, const char *fmt, ...);
void
xo_errx(int eval, const char *fmt, ...);
void
xo_message(const char *fmt, ...);
void
xo_message_c(int code, const char *fmt, ...);
void
xo_message_hc(xo_handle_t *xop, int code, const char *fmt, ...);
void
xo_message_hcv(xo_handle_t *xop, int code, const char *fmt, va_list vap);
DESCRIPTION
Many programs make use of the standard library functions err(3) and warn(3) to generate errors and warnings for the user. libxo wants to
pass that information via the current output style, and provides compatible functions to allow this.
These functions display the program name, a colon, a formatted message based on the arguments, and then optionally a colon and an error mes-
sage associated with either errno or the code parameter.
EXAMPLE:
if (open(filename, O_RDONLY) < 0)
xo_err(1, "cannot open file '%s'", filename);
ADDITIONAL DOCUMENTATION
Complete documentation can be found on github:
http://juniper.github.io/libxo/libxo-manual.html
libxo lives on github as:
https://github.com/Juniper/libxo
The latest release of libxo is available at:
https://github.com/Juniper/libxo/releases
SEE ALSO xo_emit(3)HISTORY
The libxo library was added in FreeBSD 11.0.
AUTHOR
Phil Shafer
BSD December 4, 2014 BSD
Check Out this Related Man Page
LIBXO(3) BSD Library Functions Manual LIBXO(3)NAME
xo_err -- emit errors and warnings in multiple formats
LIBRARY
library ``libxo''
SYNOPSIS
#include <libxo/xo.h>
void
xo_warn(const char *fmt, ...);
void
xo_warnx(const char *fmt, ...);
void
xo_warn_c(int code, const char *fmt, ...);
void
xo_warn_hc(xo_handle_t *xop, int code, const char *fmt, ...);
void
xo_err(int eval, const char *fmt, ...);
void
xo_errc(int eval, int code, const char *fmt, ...);
void
xo_errx(int eval, const char *fmt, ...);
void
xo_message(const char *fmt, ...);
void
xo_message_c(int code, const char *fmt, ...);
void
xo_message_hc(xo_handle_t *xop, int code, const char *fmt, ...);
void
xo_message_hcv(xo_handle_t *xop, int code, const char *fmt, va_list vap);
DESCRIPTION
Many programs make use of the standard library functions err(3) and warn(3) to generate errors and warnings for the user. libxo wants to
pass that information via the current output style, and provides compatible functions to allow this.
These functions display the program name, a colon, a formatted message based on the arguments, and then optionally a colon and an error mes-
sage associated with either errno or the code parameter.
EXAMPLE:
if (open(filename, O_RDONLY) < 0)
xo_err(1, "cannot open file '%s'", filename);
ADDITIONAL DOCUMENTATION
Complete documentation can be found on github:
http://juniper.github.io/libxo/libxo-manual.html
libxo lives on github as:
https://github.com/Juniper/libxo
The latest release of libxo is available at:
https://github.com/Juniper/libxo/releases
SEE ALSO xo_emit(3)HISTORY
The libxo library was added in FreeBSD 11.0.
AUTHOR
Phil Shafer
BSD December 4, 2014 BSD
Introduction
Originally, we only had one shell on unix. When ran a command, the shell would attempt to invoke one of the exec() system calls on it. It the command was an executable, the exec would succeed and the command would run. If the exec() failed, the shell would not give up, instead it... (3 Replies)
FreeBSD Kernel Internals, Dr. Marshall Kirk McKusick
nwbqBdghh6E
The first hour of Marshall Kirk McKusick's course on FreeBSD kernel internals based on his book, The Design and Implementation of the FreeBSD Operating System. (0 Replies)
Introduction
I have seen some misinformation regarding Unix file permissions. I will try to set the record straight. Take a look at this example of some output from ls:
$ ls -ld /usr/bin /usr/bin/cat
drwxrwxr-x 3 root bin 8704 Sep 23 2004 /usr/bin
-r-xr-xr-x 1 bin bin ... (6 Replies)
Suppose I have a main() function with only one malloc statement allocating say some 1 gb memory. Also say my system has 1 gb of ram.
main()
{
malloc(1gb)
return(0)
}
The program above exits without freeing the memory.
In this case will the 1 gb of heap memory be returned... (9 Replies)
I see lot of ad-hoc shell scripts in our servers which don't have a shebang at the beginning .
Does this mean that it will run on any shell ?
Is it a good practice to create scripts (even ad-hoc ones) without shebang ? (16 Replies)
Hi everyone,
I know the following questions are noobish questions but I am asking them because I am confused about the basics of history behind UNIX and LINUX.
Ok onto business, my questions are-:
Was/Is UNIX ever an open source operating system ?
If UNIX was... (21 Replies)
A shout out to Scott who gave me a helping hand to turn a simple sample Vue.js app I wrote yesterday into a Vue.js component:
Vue.component("unix-time", {
template: `<div class="time">{{unixtime}}</div>`,
data() {
return {
unixtime: ""
};
},
methods: {
... (1 Reply)
i read here that linux provides no way to determine when a directory was created.
https://www.unix.com/shell-programming-and-scripting/157874-creation-date-directory.htmlI have a directory /home/andy/scripts that had a README file in it.
That file says
I put the script in that directory and... (3 Replies)
Hello.
I can use any particular (stupid or not) format when using bash date command.
Example :
~> date --date "now" '+%Y-%m-%d %H!%M!%S'
2019-06-03 12!55!33or
~> date --date "now" '+%Y£%m£%d %H¤%M¤%S'
2019£06£03 12¤57¤36
or
~> date --date "now" '+%Y-%m-%d %H-%M-%S'
2019-06-03 12-58-51
... (4 Replies)
Morning All
So, I am starting looking into the world of UNIX for a new job (luckily not my primary function!) and I am looking to get stared. Like anything I seem to learn best by trying things out first in an environment but I have a key question:
Currently I use Oracle VirtualBox, can... (8 Replies)
I've installed Slack 14.2 on /dev/sda1 (/dev/sda2 is swap) and FreeBSD 12 on /dev/sda3 and lilo is the boot manager.
FreeBSD slices are as follows;
/ on /dev/ada0S3a, swap on /dev/ada0s3e, /var on /dev/ada0s3b, /tmp on /dev/ada0s3d and /usr on /dev/ada0s3f.
I hesitate to install Solaris 10... (2 Replies)
I'm trying to use a bash script for a psych experiment that involves listening to sound files and responding. If I have something like the code below, how can I make sure that a key press is assigned to RESPONSE only after the second echo statement?
for i in 1 2 3; do
echo "Ready?"
sleep 2
... (10 Replies)