Manpages

-h

Print a usage message and exit.

-D

Delete rows selected by the query. This is not reversible.

-l

Create a log entry. This option is mutually exclusive with the -F option, or with any relative specifications (see below).

-P path

Specify that path should be used as the PSEUDO_PREFIX value, overriding any environment setting.

-U

Restrict query output to unique rows. Rows will have members defined by the -F (format) option. If all members are the same between two rows, only one is displayed. Applies only to queries.

-v

Increase verbosity (debug level). Not useful except when debugging pseudo. Deprecated; use -x.

-xflags

Specify debugging flags of interest. Not useful except when debugging pseudo.

>

Greater than; true if the related field is greater than the provided value.

<

Less than; true if the related field is less than the provided value.

&

Bitwise and; true if the related field, bitwise-and the provided value, is non-zero. (This is useful primarily for permissions or modes.)

=

Equal to. (This is a no-op, as of this writing.)

!

Not equal to.

%

Similar to ~. This is valid only on text fields, and is equivalent to the SQL LIKE operator, with % patterns on the ends; it performs an unanchored, case-insensitive match.

~

Similar to %. This is valid only on text fields, and is equivalent to the SQL LIKE operator, but performs an anchored match. The match is case-insensitive. The specifier ~%foo% is equivalent to the specifier %foo.

^

Unlike. This is the inverse of ~; it specifies NOT LIKE.

Escape the string. This is useful if you want to have one of the other modifiers at the beginning of the string.

a

Access mode. This is an access mode specified in the form used by fopen(3), such as "r+" to indicate read/write access. Note that specifying a as an access mode will include non-append writes, as the "a" mode implies write and append both. This feature is slightly experimental and may not correctly identify the access type of every access. The string x may be specified to indicate execute access.

c

Client ID (the PID of a client).

d

Device number (from a stat buffer).

f

File descriptor. In some cases, messages have an associated file descriptor identified.

g

GID. The group ID associated with an entry.

G

Tag. This is a text field. In log entries created by pseudo, this field holds the value that the environment variable PSEUDO_TAG had in the client’s environment.

i

Inode number (from a stat buffer).

I

ID. This is the database row number. Normally these are assigned as monotonically increasing values as rows are inserted, making them a more reliable sorting mechanism than timestamps. The default ordering is by ID. m Permissions. These can be entered as an octal value or as a symbolic mode string, similar to the output of ls(1) -l. The file type component is ignored.

M

Mode. This can be entered as an octal value or as a symbolic mode string, similar to the output of ls(1) -l. This is tested against the whole file mode, including both the type and permissions bits. In general, it is more useful to use the m or t specifiers.

o

Operation. This is the name of the file system operation (e.g., "open" or "rename").

O

Order. This takes another specification character as the field on which to order results. A ’<’ implies a descending order sort, a ’>’ or no modifier specifies an ascending order sort. By default, records are sorted by ID.

p

File path. This is a text field.

r

Result. This is the pseudo result code, most often "fail" or "succeed". Note that "fail" doesn’t mean that an underlying operation failed; for instance, if a "stat" operation fails, it usually means that there was no entry in the pseudo database.

R

Program. This is the program name (as retrieved by glibc’s program_invocation_name variable), which has the full path if and only if the program was invoked by full path name.

s

Timestamp. The format of this field is controlled by the -E format string, which is used with strftime(3) when displaying entries, or with strptime(3) when interpreting command line values. There is a small selection of common default time formats understood by the parser. Time fields not specified default to the current time. Note that specifying a time stamp when creating a log entry may yield confusing results.

S

Severity. Log messages can have a severity, with the default for file operations being "info". t File type. This corresponds to the first letter of a mode string, or the values accepted by the -type option to find(1). This is compared only against the file type bits of a mode.

T

Text. This is an optional field available for user use when creating log entries, or to hold the text of an error message when an error is logged. It is, of course, a text field.

u

UID. The user ID associated with an entry.

y

Type. This is usually "op" for operations, or "ping" for the ping messages clients send to confirm server availability. Other types should rarely occur, but include "ack" and "nak" for server responses (which are never logged), and "halt" for shutdown messages (currently not logged).