{
    "mode": "man",
    "parameter": "ausearch",
    "section": "8",
    "url": "https://www.chedong.com/phpMan.php/man/ausearch/8/json",
    "generated": "2026-09-16T07:00:16Z",
    "synopsis": "ausearch [options]",
    "sections": {
        "NAME": {
            "content": "ausearch - a tool to query audit daemon logs\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "ausearch [options]\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "ausearch  is  a tool that can query the audit daemon logs based for events based on different\nsearch criteria. The ausearch utility can also take input from stdin as long as the input  is\nthe  raw  log  data.  Each  commandline  option  given forms an \"and\" statement. For example,\nsearching with -m and -ui means return events that have both the requested type and match the\nuser id given. An exception is the -m  and -n options; multiple record types  and  nodes  are\nallowed in a search which will return any matching node and record.\n\nIt  should also be noted that each syscall excursion from user space into the kernel and back\ninto user space has one event ID that is unique. Any auditable event that is triggered during\nthis trip share this ID so that they may be correlated.\n\nDifferent parts of the kernel may add supplemental records. For example, an  audit  event  on\nthe  syscall  \"open\" will also cause the kernel to emit a PATH record with the file name. The\nausearch utility will present all records that make up one event together.  This  could  mean\nthat  even  though you search for a specific kind of record, the resulting events may contain\nSYSCALL records.\n\nAlso be aware that not all record types have the requested information. For example,  a  PATH\nrecord does not have a hostname or a loginuid.\n\n",
            "subsections": []
        },
        "OPTIONS": {
            "content": "",
            "subsections": [
                {
                    "name": "-a --event _",
                    "content": "Search  for an event based on the given event ID. Messages always start with something\nlike msg=audit(1116360555.329:2401771). The event ID is the number after the ':'.  All\naudit  events  that  are  recorded  from one application's syscall have the same audit\nevent ID. A second syscall made by the same application will have  a  different  event\nID. This way they are unique.\n\n--arch CPU\nSearch  for  events based on a specific CPU architecture.  If you do not know the arch\nof your machine but you want to use the 32 bit syscall table and your machine supports\n32 bits, you can also use b32 for the arch. The same applies to the 64 bit syscall ta‐\nble, you can use b64.  The arch of your machine can be found by doing 'uname -m'.\n",
                    "flag": "-a",
                    "long": "--event"
                },
                {
                    "name": "-c --comm _",
                    "content": "Search for an event based on the given comm name. The comm name  is  the  executable's\nname from the task structure.\n",
                    "flag": "-c",
                    "long": "--comm"
                },
                {
                    "name": "--debug",
                    "content": "Write malformed events that are skipped to stderr.\n\n--checkpoint checkpoint-file\nCheckpoint the output between successive invocations of ausearch such that only events\nnot previously output will print in subsequent invocations.\n\nAn  auditd  event  is made up of one or more records. When processing events, ausearch\ndefines events as either complete or in-complete.  A complete event is either a single\nrecord event or one whose event time occurred 2 seconds in the past  compared  to  the\nevent being currently processed.\n\nA  checkpoint  is achieved by recording the last completed event output along with the\ndevice number and inode of the file the last completed event appeared  in  checkpoint-\nfile.  On  a  subsequent invocation, ausearch will load this checkpoint data and as it\nprocesses the log files, it will discard all complete  events  until  it  matches  the\ncheckpointed one. At this point, it will start outputting complete events.\n\nShould the file or the last checkpointed event not be found, one of a number of errors\nwill result and ausearch will terminate. See EXIT STATUS for detail.\n\n\n--eoe-timeout seconds\nSet  the  end of event parsing timeout. See endofeventtimeout in auditd.conf(5) for\ndetails. Note that setting this value will override  any  configured  value  found  in\n/etc/auditd/auditd.conf.\n",
                    "long": "--debug"
                },
                {
                    "name": "-e,",
                    "content": "Search for an event based on the given syscall exit code or errno.\n\n--escape option\nThis  option determines if the output is escaped to make the content safer for certain\nuses. The options are raw , tty , shell , and  shellquote.  Each  mode  includes  the\ncharacters of the preceding mode and escapes more characters. That is to say shell in‐\ncludes all characters escaped by tty and adds more. tty is the default.\n",
                    "flag": "-e"
                },
                {
                    "name": "--extra-keys",
                    "content": "When  the format mode is csv, this option will add a final column with key information\nif its exists for the event. This would only occur on SYSCALL records which  were  the\nresult of triggering an audit rule that defines a key.\n",
                    "long": "--extra-keys"
                },
                {
                    "name": "--extra-labels",
                    "content": "When the format mode is csv, this option will add columns of information about subject\nand object labels when they exist.\n",
                    "long": "--extra-labels"
                },
                {
                    "name": "--extra-obj2",
                    "content": "When  the format mode is csv, this option will add columns of information about a sec‐\nond object when it exists. It's rare that a second object is part of  a  record.  Some\nexamples  are  when  a  file  is  renamed from one name to another or when a device is\nmounted to a path.\n",
                    "long": "--extra-obj2"
                },
                {
                    "name": "--extra-time",
                    "content": "When the format mode is csv, this option will add columns of information about  broken\ndown time to make subsetting easier.\n",
                    "long": "--extra-time"
                },
                {
                    "name": "-f --file _",
                    "content": "Search  for an event based on the given filename. The argument will match normal files\nas well as afunix sockets.\n\n--format option\nEvents that match the search criteria are formatted using this option.  The  supported\nformats are: raw, default, interpret, csv, and text. The raw option is described under\nthe  --raw  command line option. The default option is what you get when no formatting\noptions are passed. It includes one line as a visual  separator  which  indicates  the\ntime stamp and then the records of the event follow. The interpret option is explained\nunder  the -i command line option. The csv option outputs the results of the search as\na normalized event in comma separated value (CSV) format suitable for import into ana‐\nlytical programs. The text option turns the event into an  English  sentence  that  is\neasier  to  understand  than other options, but it comes at the expense of loss of de‐\ntail. In most cases this is perfectly fine since the original event still retains  all\nthe original information.\n",
                    "flag": "-f",
                    "long": "--file"
                },
                {
                    "name": "-ga --gid-all _",
                    "content": "Search  for  an  event  with  either effective group ID or group ID matching the given\ngroup ID.\n",
                    "long": "--gid-all"
                },
                {
                    "name": "-ge --gid-effective _",
                    "content": "Search for an event with the given effective group ID or group name.\n",
                    "long": "--gid-effective"
                },
                {
                    "name": "-gi --gid _",
                    "content": "Search for an event with the given group ID or group name.\n",
                    "long": "--gid"
                },
                {
                    "name": "-h --help",
                    "content": "Help\n",
                    "flag": "-h",
                    "long": "--help"
                },
                {
                    "name": "-hn --host _",
                    "content": "Search for an event with the given host name. The hostname can be either  a  hostname,\nfully qualified domain name, or numeric network address. No attempt is made to resolve\nnumeric  addresses to domain names or aliases. This search typically correlates to the\naddr or host field of audit events. Also see the --node  command  which  searches  the\nnode field.\n",
                    "long": "--host"
                },
                {
                    "name": "-i --interpret",
                    "content": "Interpret  numeric  entities into text. For example, uid is converted to account name.\nIf the audit logs are unenriched, the conversion is done using the  current  resources\nof  the  machine  where  the search is being run. If you have renamed the accounts, or\ndon't have the same accounts on your machine, you could get misleading results. If the\nlogs are enriched, it uses the supplemental data to do the conversion. This allows ac‐\ncurate log reporting even when run on a different machine than the original logs  came\nfrom.\n",
                    "flag": "-i",
                    "long": "--interpret"
                },
                {
                    "name": "-if --input _",
                    "content": "Use the given file or directory instead of the logs. This is to aid analysis where the\nlogs  have  been  moved  to  another machine or only part of a log was saved. The path\nlength is limited to 4064 bytes.\n",
                    "long": "--input"
                },
                {
                    "name": "--input-logs",
                    "content": "Use the log file location from auditd.conf as input for searching. This is  needed  if\nyou are using ausearch from a cron job.\n",
                    "long": "--input-logs"
                },
                {
                    "name": "--just-one",
                    "content": "Stop after emitting the first event that matches the search criteria.\n",
                    "long": "--just-one"
                },
                {
                    "name": "-k --key _",
                    "content": "Search for an event based on the given key string.\n",
                    "flag": "-k",
                    "long": "--key"
                },
                {
                    "name": "-l --line-buffered",
                    "content": "Flush output on every line. Most useful when stdout is connected to a pipe and the de‐\nfault block buffering strategy is undesirable. May impose a performance penalty.\n",
                    "flag": "-l",
                    "long": "--line-buffered"
                },
                {
                    "name": "-m --message _",
                    "content": "Search  for an event matching the given message type. (Message types are also known as\nrecord types.) You may also enter a comma separated list of message types or  multiple\nindividual  message  types  each  with its own -m option. There is an ALL message type\nthat doesn't exist in the actual logs. It allows you to get all messages in  the  sys‐\ntem. The list of valid messages types is long. The program will display the list when‐\never  no  message  type  is passed with this parameter. The message type can be either\ntext or numeric. If you enter a list, there can be only commas and no spaces  separat‐\ning the list.\n",
                    "flag": "-m",
                    "long": "--message"
                },
                {
                    "name": "-n --node",
                    "content": "Search for events originating from a specific machine. Multiple nodes are allowed, and\nif  any  nodes  match,  the event is matched. This search uses the node field in audit\nevents. Also see the --host command which search for events related to  host  informa‐\ntion in the audit trail.\n",
                    "flag": "-n",
                    "long": "--node"
                },
                {
                    "name": "-o --object _",
                    "content": "Search for event with tcontext (object) matching the string.\n",
                    "flag": "-o",
                    "long": "--object"
                },
                {
                    "name": "-p --pid _",
                    "content": "Search for an event matching the given process ID.\n",
                    "flag": "-p",
                    "long": "--pid"
                },
                {
                    "name": "-pp --ppid _",
                    "content": "Search for an event matching the given parent process ID.\n",
                    "long": "--ppid"
                },
                {
                    "name": "-r --raw",
                    "content": "Output is completely unformatted. This is useful for extracting records to a file that\ncan still be interpreted by audit tools or when piping to other audit tools.\n",
                    "flag": "-r",
                    "long": "--raw"
                },
                {
                    "name": "-sc --syscall _",
                    "content": "Search  for  an  event  matching  the  given  syscall. You may either give the numeric\nsyscall value or the syscall name. If you give the  syscall  name,  it  will  use  the\nsyscall table for the machine that you are using.\n",
                    "long": "--syscall"
                },
                {
                    "name": "-se --context _",
                    "content": "Search  for  events with either scontext/subject or tcontext/object matching the given\nstring.\n\n--session Login-Session-ID\nSearch for events matching the given Login Session ID. This process attribute  is  set\nwhen a user logs in and can tie any process to a particular user login.\n",
                    "long": "--context"
                },
                {
                    "name": "-su --subject _",
                    "content": "Search for event with scontext (subject) matching the string.\n",
                    "long": "--subject"
                },
                {
                    "name": "-sv --success _",
                    "content": "Search for an event matching the given success value. Legal values are yes and no.\n",
                    "long": "--success"
                },
                {
                    "name": "-te --end",
                    "content": "Search  for  events with time stamps equal to or before the given end time. The format\nof end time depends on your locale. You can check the format of your locale by running\ndate '+%x'.  If the date is omitted, today is assumed. If the time is omitted, now  is\nassumed.  Use 24 hour clock time rather than AM or PM to specify time. An example date\nusing the enUS.utf8 locale is 09/03/2009. An example of time is  18:00:00.  The  date\nformat accepted is influenced by the LCTIME environmental variable.\n\nYou  may also use the word: now, recent, this-hour, boot, today, yesterday, this-week,\nweek-ago, this-month, or this-year. Now means starting now. Recent is 10 minutes  ago.\nBoot means the time of day to the second when the system last booted. Today means now.\nYesterday is 1 second after midnight the previous day. This-week means starting 1 sec‐\nond  after  midnight  on  day 0 of the week determined by your locale (see localtime).\nWeek-ago means 1 second after midnight exactly 7 days ago. This-month means  1  second\nafter  midnight  on day 1 of the month. This-year means the 1 second after midnight on\nthe first day of the first month.\n",
                    "long": "--end"
                },
                {
                    "name": "-ts --start",
                    "content": "Search for events with time stamps equal to or after the given start time. The  format\nof  start time depends on your locale. You can check the format of your locale by run‐\nning date '+%x'.  If the date is omitted, today is assumed. If the  time  is  omitted,\nmidnight  is  assumed. Use 24 hour clock time rather than AM or PM to specify time. An\nexample date using the  enUS.utf8  locale  is  09/03/2009.  An  example  of  time  is\n18:00:00.  The  date  format accepted is influenced by the LCTIME environmental vari‐\nable.\n\nYou may also use the word: now, recent, this-hour, boot, today, yesterday,  this-week,\nweek-ago, this-month, this-year, or checkpoint. Boot means the time of day to the sec‐\nond  when the system last booted. Today means starting at 1 second after midnight. Re‐\ncent is 10 minutes ago. Yesterday  is  1  second  after  midnight  the  previous  day.\nThis-week  means  starting  1 second after midnight on day 0 of the week determined by\nyour locale (see localtime). Week-ago means starting 1 second after midnight exactly 7\ndays ago. This-month means 1 second after midnight on day 1 of  the  month.  This-year\nmeans the 1 second after midnight on the first day of the first month.\n\ncheckpoint  means ausearch will use the timestamp found within a valid checkpoint file\nignoring the recorded inode, device, serial, node and event type also found  within  a\ncheckpoint  file.  Essentially,  this  is  the recovery action should an invocation of\nausearch with a checkpoint option fail with an exit status of 10, 11 or 12.  It  could\nbe used in a shell script something like:\n\nausearch --checkpoint /etc/audit/auditdcheckpoint.txt -i\naustatus=$?\nif test ${austatus} eq 10 -o ${austatus} eq 11 -o ${austatus} eq 12\nthen\nausearch --checkpoint /etc/audit/auditdcheckpoint.txt --start checkpoint -i\nfi\n",
                    "long": "--start"
                },
                {
                    "name": "-tm --terminal _",
                    "content": "Search  for  an event matching the given terminal value. Some daemons such as cron and\natd use the daemon name for the terminal.\n",
                    "long": "--terminal"
                },
                {
                    "name": "-ua --uid-all _",
                    "content": "Search for an event with either user ID, effective user ID, or login  user  ID  (auid)\nmatching the given user ID.\n",
                    "long": "--uid-all"
                },
                {
                    "name": "-ue --uid-effective _",
                    "content": "Search for an event with the given effective user ID.\n",
                    "long": "--uid-effective"
                },
                {
                    "name": "-ui --uid _",
                    "content": "Search for an event with the given user ID.\n",
                    "long": "--uid"
                },
                {
                    "name": "-ul --loginuid _",
                    "content": "Search  for  an  event with the given login user ID. All entry point programs that are\nPAMified need to be configured with pamloginuid required for the session for  search‐\ning on loginuid (auid) to be accurate.\n",
                    "long": "--loginuid"
                },
                {
                    "name": "-uu --uuid _",
                    "content": "Search for an event with the given guest UUID.\n",
                    "long": "--uuid"
                },
                {
                    "name": "-v --version",
                    "content": "Print the version and exit\n",
                    "flag": "-v",
                    "long": "--version"
                },
                {
                    "name": "-vm --vm-name _",
                    "content": "Search for an event with the given guest name.\n",
                    "long": "--vm-name"
                },
                {
                    "name": "-w --word",
                    "content": "String  based  matches  must  match  the whole word. This category of matches include:\nfilename, hostname, terminal, keys, and SE Linux context.\n",
                    "flag": "-w",
                    "long": "--word"
                },
                {
                    "name": "-x --executable _",
                    "content": "Search for an event matching the given executable name.\n\n",
                    "flag": "-x",
                    "long": "--executable"
                }
            ]
        },
        "EXIT STATUS": {
            "content": "0    if OK,\n\n1    if nothing found, or argument errors or minor file access/read errors,\n\n10   invalid checkpoint data found in checkpoint file,\n\n11   checkpoint processing error\n\n12   checkpoint event not found in matching log file\n",
            "subsections": []
        },
        "NOTE": {
            "content": "The boot time option is a convenience function and has limitations. The time it calculates is\nbased on time now minus /proc/uptime. If after boot the system clock has been adjusted,  per‐\nhaps by ntp, then the calculation may be wrong. In that case you'll need to fully specify the\ntime. You can check the time it would use by running:\n\ndate -d \"`cut -f1 -d. /proc/uptime` seconds ago\"\n\n",
            "subsections": []
        },
        "EXAMPLES": {
            "content": "Search for a specific user:\n# ausearch --start today --loginuid john -i\n\nCheck the SELinux log for any denials today\n# ausearch --start today -m avc -i\n\nOutput logs in text format\n# ausearch --start today --format text\n\nOutput TTY events interpreted and shell escaped\n# ausearch --start today -m TTY -i --escape shellquote\n\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "auditd(8), auditd.conf(5), aureport(8), pamloginuid(8).\n\nRed Hat                                       July 2023                                  AUSEARCH(8)",
            "subsections": []
        }
    },
    "summary": "ausearch - a tool to query audit daemon logs",
    "flags": [
        {
            "flag": "-a",
            "long": "--event",
            "arg": null,
            "description": "Search for an event based on the given event ID. Messages always start with something like msg=audit(1116360555.329:2401771). The event ID is the number after the ':'. All audit events that are recorded from one application's syscall have the same audit event ID. A second syscall made by the same application will have a different event ID. This way they are unique. --arch CPU Search for events based on a specific CPU architecture. If you do not know the arch of your machine but you want to use the 32 bit syscall table and your machine supports 32 bits, you can also use b32 for the arch. The same applies to the 64 bit syscall ta‐ ble, you can use b64. The arch of your machine can be found by doing 'uname -m'."
        },
        {
            "flag": "-c",
            "long": "--comm",
            "arg": null,
            "description": "Search for an event based on the given comm name. The comm name is the executable's name from the task structure."
        },
        {
            "flag": "",
            "long": "--debug",
            "arg": null,
            "description": "Write malformed events that are skipped to stderr. --checkpoint checkpoint-file Checkpoint the output between successive invocations of ausearch such that only events not previously output will print in subsequent invocations. An auditd event is made up of one or more records. When processing events, ausearch defines events as either complete or in-complete. A complete event is either a single record event or one whose event time occurred 2 seconds in the past compared to the event being currently processed. A checkpoint is achieved by recording the last completed event output along with the device number and inode of the file the last completed event appeared in checkpoint- file. On a subsequent invocation, ausearch will load this checkpoint data and as it processes the log files, it will discard all complete events until it matches the checkpointed one. At this point, it will start outputting complete events. Should the file or the last checkpointed event not be found, one of a number of errors will result and ausearch will terminate. See EXIT STATUS for detail. --eoe-timeout seconds Set the end of event parsing timeout. See endofeventtimeout in auditd.conf(5) for details. Note that setting this value will override any configured value found in /etc/auditd/auditd.conf."
        },
        {
            "flag": "-e",
            "long": null,
            "arg": null,
            "description": "Search for an event based on the given syscall exit code or errno. --escape option This option determines if the output is escaped to make the content safer for certain uses. The options are raw , tty , shell , and shellquote. Each mode includes the characters of the preceding mode and escapes more characters. That is to say shell in‐ cludes all characters escaped by tty and adds more. tty is the default."
        },
        {
            "flag": "",
            "long": "--extra-keys",
            "arg": null,
            "description": "When the format mode is csv, this option will add a final column with key information if its exists for the event. This would only occur on SYSCALL records which were the result of triggering an audit rule that defines a key."
        },
        {
            "flag": "",
            "long": "--extra-labels",
            "arg": null,
            "description": "When the format mode is csv, this option will add columns of information about subject and object labels when they exist."
        },
        {
            "flag": "",
            "long": "--extra-obj2",
            "arg": null,
            "description": "When the format mode is csv, this option will add columns of information about a sec‐ ond object when it exists. It's rare that a second object is part of a record. Some examples are when a file is renamed from one name to another or when a device is mounted to a path."
        },
        {
            "flag": "",
            "long": "--extra-time",
            "arg": null,
            "description": "When the format mode is csv, this option will add columns of information about broken down time to make subsetting easier."
        },
        {
            "flag": "-f",
            "long": "--file",
            "arg": null,
            "description": "Search for an event based on the given filename. The argument will match normal files as well as afunix sockets. --format option Events that match the search criteria are formatted using this option. The supported formats are: raw, default, interpret, csv, and text. The raw option is described under the --raw command line option. The default option is what you get when no formatting options are passed. It includes one line as a visual separator which indicates the time stamp and then the records of the event follow. The interpret option is explained under the -i command line option. The csv option outputs the results of the search as a normalized event in comma separated value (CSV) format suitable for import into ana‐ lytical programs. The text option turns the event into an English sentence that is easier to understand than other options, but it comes at the expense of loss of de‐ tail. In most cases this is perfectly fine since the original event still retains all the original information."
        },
        {
            "flag": "",
            "long": "--gid-all",
            "arg": null,
            "description": "Search for an event with either effective group ID or group ID matching the given group ID."
        },
        {
            "flag": "",
            "long": "--gid-effective",
            "arg": null,
            "description": "Search for an event with the given effective group ID or group name."
        },
        {
            "flag": "",
            "long": "--gid",
            "arg": null,
            "description": "Search for an event with the given group ID or group name."
        },
        {
            "flag": "-h",
            "long": "--help",
            "arg": null,
            "description": "Help"
        },
        {
            "flag": "",
            "long": "--host",
            "arg": null,
            "description": "Search for an event with the given host name. The hostname can be either a hostname, fully qualified domain name, or numeric network address. No attempt is made to resolve numeric addresses to domain names or aliases. This search typically correlates to the addr or host field of audit events. Also see the --node command which searches the node field."
        },
        {
            "flag": "-i",
            "long": "--interpret",
            "arg": null,
            "description": "Interpret numeric entities into text. For example, uid is converted to account name. If the audit logs are unenriched, the conversion is done using the current resources of the machine where the search is being run. If you have renamed the accounts, or don't have the same accounts on your machine, you could get misleading results. If the logs are enriched, it uses the supplemental data to do the conversion. This allows ac‐ curate log reporting even when run on a different machine than the original logs came from."
        },
        {
            "flag": "",
            "long": "--input",
            "arg": null,
            "description": "Use the given file or directory instead of the logs. This is to aid analysis where the logs have been moved to another machine or only part of a log was saved. The path length is limited to 4064 bytes."
        },
        {
            "flag": "",
            "long": "--input-logs",
            "arg": null,
            "description": "Use the log file location from auditd.conf as input for searching. This is needed if you are using ausearch from a cron job."
        },
        {
            "flag": "",
            "long": "--just-one",
            "arg": null,
            "description": "Stop after emitting the first event that matches the search criteria."
        },
        {
            "flag": "-k",
            "long": "--key",
            "arg": null,
            "description": "Search for an event based on the given key string."
        },
        {
            "flag": "-l",
            "long": "--line-buffered",
            "arg": null,
            "description": "Flush output on every line. Most useful when stdout is connected to a pipe and the de‐ fault block buffering strategy is undesirable. May impose a performance penalty."
        },
        {
            "flag": "-m",
            "long": "--message",
            "arg": null,
            "description": "Search for an event matching the given message type. (Message types are also known as record types.) You may also enter a comma separated list of message types or multiple individual message types each with its own -m option. There is an ALL message type that doesn't exist in the actual logs. It allows you to get all messages in the sys‐ tem. The list of valid messages types is long. The program will display the list when‐ ever no message type is passed with this parameter. The message type can be either text or numeric. If you enter a list, there can be only commas and no spaces separat‐ ing the list."
        },
        {
            "flag": "-n",
            "long": "--node",
            "arg": null,
            "description": "Search for events originating from a specific machine. Multiple nodes are allowed, and if any nodes match, the event is matched. This search uses the node field in audit events. Also see the --host command which search for events related to host informa‐ tion in the audit trail."
        },
        {
            "flag": "-o",
            "long": "--object",
            "arg": null,
            "description": "Search for event with tcontext (object) matching the string."
        },
        {
            "flag": "-p",
            "long": "--pid",
            "arg": null,
            "description": "Search for an event matching the given process ID."
        },
        {
            "flag": "",
            "long": "--ppid",
            "arg": null,
            "description": "Search for an event matching the given parent process ID."
        },
        {
            "flag": "-r",
            "long": "--raw",
            "arg": null,
            "description": "Output is completely unformatted. This is useful for extracting records to a file that can still be interpreted by audit tools or when piping to other audit tools."
        },
        {
            "flag": "",
            "long": "--syscall",
            "arg": null,
            "description": "Search for an event matching the given syscall. You may either give the numeric syscall value or the syscall name. If you give the syscall name, it will use the syscall table for the machine that you are using."
        },
        {
            "flag": "",
            "long": "--context",
            "arg": null,
            "description": "Search for events with either scontext/subject or tcontext/object matching the given string. --session Login-Session-ID Search for events matching the given Login Session ID. This process attribute is set when a user logs in and can tie any process to a particular user login."
        },
        {
            "flag": "",
            "long": "--subject",
            "arg": null,
            "description": "Search for event with scontext (subject) matching the string."
        },
        {
            "flag": "",
            "long": "--success",
            "arg": null,
            "description": "Search for an event matching the given success value. Legal values are yes and no."
        },
        {
            "flag": "",
            "long": "--end",
            "arg": null,
            "description": "Search for events with time stamps equal to or before the given end time. The format of end time depends on your locale. You can check the format of your locale by running date '+%x'. If the date is omitted, today is assumed. If the time is omitted, now is assumed. Use 24 hour clock time rather than AM or PM to specify time. An example date using the enUS.utf8 locale is 09/03/2009. An example of time is 18:00:00. The date format accepted is influenced by the LCTIME environmental variable. You may also use the word: now, recent, this-hour, boot, today, yesterday, this-week, week-ago, this-month, or this-year. Now means starting now. Recent is 10 minutes ago. Boot means the time of day to the second when the system last booted. Today means now. Yesterday is 1 second after midnight the previous day. This-week means starting 1 sec‐ ond after midnight on day 0 of the week determined by your locale (see localtime). Week-ago means 1 second after midnight exactly 7 days ago. This-month means 1 second after midnight on day 1 of the month. This-year means the 1 second after midnight on the first day of the first month."
        },
        {
            "flag": "",
            "long": "--start",
            "arg": null,
            "description": "Search for events with time stamps equal to or after the given start time. The format of start time depends on your locale. You can check the format of your locale by run‐ ning date '+%x'. If the date is omitted, today is assumed. If the time is omitted, midnight is assumed. Use 24 hour clock time rather than AM or PM to specify time. An example date using the enUS.utf8 locale is 09/03/2009. An example of time is 18:00:00. The date format accepted is influenced by the LCTIME environmental vari‐ able. You may also use the word: now, recent, this-hour, boot, today, yesterday, this-week, week-ago, this-month, this-year, or checkpoint. Boot means the time of day to the sec‐ ond when the system last booted. Today means starting at 1 second after midnight. Re‐ cent is 10 minutes ago. Yesterday is 1 second after midnight the previous day. This-week means starting 1 second after midnight on day 0 of the week determined by your locale (see localtime). Week-ago means starting 1 second after midnight exactly 7 days ago. This-month means 1 second after midnight on day 1 of the month. This-year means the 1 second after midnight on the first day of the first month. checkpoint means ausearch will use the timestamp found within a valid checkpoint file ignoring the recorded inode, device, serial, node and event type also found within a checkpoint file. Essentially, this is the recovery action should an invocation of ausearch with a checkpoint option fail with an exit status of 10, 11 or 12. It could be used in a shell script something like: ausearch --checkpoint /etc/audit/auditdcheckpoint.txt -i austatus=$? if test ${austatus} eq 10 -o ${austatus} eq 11 -o ${austatus} eq 12 then ausearch --checkpoint /etc/audit/auditdcheckpoint.txt --start checkpoint -i fi"
        },
        {
            "flag": "",
            "long": "--terminal",
            "arg": null,
            "description": "Search for an event matching the given terminal value. Some daemons such as cron and atd use the daemon name for the terminal."
        },
        {
            "flag": "",
            "long": "--uid-all",
            "arg": null,
            "description": "Search for an event with either user ID, effective user ID, or login user ID (auid) matching the given user ID."
        },
        {
            "flag": "",
            "long": "--uid-effective",
            "arg": null,
            "description": "Search for an event with the given effective user ID."
        },
        {
            "flag": "",
            "long": "--uid",
            "arg": null,
            "description": "Search for an event with the given user ID."
        },
        {
            "flag": "",
            "long": "--loginuid",
            "arg": null,
            "description": "Search for an event with the given login user ID. All entry point programs that are PAMified need to be configured with pamloginuid required for the session for search‐ ing on loginuid (auid) to be accurate."
        },
        {
            "flag": "",
            "long": "--uuid",
            "arg": null,
            "description": "Search for an event with the given guest UUID."
        },
        {
            "flag": "-v",
            "long": "--version",
            "arg": null,
            "description": "Print the version and exit"
        },
        {
            "flag": "",
            "long": "--vm-name",
            "arg": null,
            "description": "Search for an event with the given guest name."
        },
        {
            "flag": "-w",
            "long": "--word",
            "arg": null,
            "description": "String based matches must match the whole word. This category of matches include: filename, hostname, terminal, keys, and SE Linux context."
        },
        {
            "flag": "-x",
            "long": "--executable",
            "arg": null,
            "description": "Search for an event matching the given executable name."
        }
    ],
    "examples": [
        "Search for a specific user:",
        "# ausearch --start today --loginuid john -i",
        "Check the SELinux log for any denials today",
        "# ausearch --start today -m avc -i",
        "Output logs in text format",
        "# ausearch --start today --format text",
        "Output TTY events interpreted and shell escaped",
        "# ausearch --start today -m TTY -i --escape shellquote"
    ],
    "see_also": [
        {
            "name": "auditd",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/auditd/8/json"
        },
        {
            "name": "auditd.conf",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/auditd.conf/5/json"
        },
        {
            "name": "aureport",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/aureport/8/json"
        },
        {
            "name": "pamloginuid",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/pamloginuid/8/json"
        }
    ]
}