fault information Post: 302706077

9 More Discussions You Might Find Interesting

1. Programming

segmentation fault

hi all i'm trying to execute a c program under linux RH and it gives me segmentation fault, this program was running under unix at&t anybody kow what the problem could be? thanx in advance regards

2. AIX

I am tring to install Lotus Domino/Notes 5.0.5 on a AIX 4.3.3 server. I go to run the cdrom/ibmpow/install and I get the following error. Lotus Notes for Unix Install Program --------------------------------------------- ./install: 10088 Segmentation fault This had Lotus Notes installed...

3. Programming

segmentation fault

ive written my code in C for implementation of a simple lexical analyser using singly linked list hence am making use of dynamic allocation,but when run in linux it gives a segmentation fault is it cause of the malloc function that ive made use of????any suggestions as to what i could do??? thank...

4. Shell Programming and Scripting

guess the fault :)

I really cant understand whats wrong with this: File looks like this: 55 11 Code: cost=30 a= cut -c9-12 File let a=${a}+${cost} echo $a The answer echo should echo 11+30(cost) however the output looks like this: 11 30 And also is there anyway to grep $2 without awk? or maybe...

5. Linux

Segmentation fault

Hi, on a linux Red HAT(with Oracle DB 9.2.0.7) I have following error : RMAN> delete obsolete; RMAN retention policy will be applied to the command RMAN retention policy is set to redundancy 2 using channel ORA_DISK_1 Segmentation fault What does it mean ? And the solution ? Many thanks.

6. Programming

why segment fault,

I always get segment fault, why? can sb help me and modify it, I have spend on much time on #include <pthread.h> #include <stdio.h> #include <stdlib.h> #include <sys/time.h> #include <string.h> #define MAX 10 pthread_t thread; void *thread1() { int *a; int i, n; ...

7. Red Hat

Red Hat linux fault information

Hi, I want to do some fault association analysis in red hat linux. who can tell me where I can get all of the fault information, and the detailed description about this fault information. Thank you very much.

8. Programming

Using gdb, ignore beginning segmentation fault until reproduce environment segmentation fault

I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this : i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ...

9. Programming

C. To segmentation fault or not to segmentation fault, that is the question.

Oddities with gcc, 2.95.3 for the AMIGA and 4.2.1 for MY current OSX 10.14.1... I am creating a basic calculator for the AMIGA ADE *NIX emulator in C as it does not have one. Below are two very condensed snippets of which I have added the results inside the each code section. IMPORTANT!...

LEARN ABOUT SUSE

aulast

AULAST:(8)						  System Administration Utilities						AULAST:(8)

NAME

       aulast - a program similar to last

SYNOPSIS

       aulast [ options ] [ user ] [ tty ]

DESCRIPTION

       aulast  is  a  program  that prints out a listing of the last logged in users similarly to the program last and lastb. Aulast searches back
       through the audit logs or the given audit log file and displays a list of all users logged in (and out) based on the range of time  in  the
       audit  logs. Names of users and tty's can be given, in which case aulast will show only those entries matching the arguments. Names of ttys
       can be abbreviated, thus aulast 0 is the same as last tty0.

       The pseudo user reboot logs in each time the system is rebooted. Thus last reboot will show a log of all reboots since  the  log  file  was
       created.

       The  main  difference  that  a user will notice is that aulast print events from oldest to newest, while last prints records from newest to
       oldest. Also, the audit system is not notified each time a tty or pty is allocated, so you may not see quite  as  many  records	indicating
       users and their tty's.

OPTIONS

       --bad  Report on the bad logins.

       --extract
	      Write raw audit records used to create the displayed report into a file aulast.log in the current working directory.

       -f file
	      Use the file instead of the audit logs for input.

       --proof
	      Print out the audit event serial numbers used to determine the preceeding line of the report. A Serial number of 0 is a place holder
	      and not an actual event serial number. The serial numbers can be used to examine the actual audit records in more  detail.  Also	an
	      ausearch query is printed that will let you find the audit records associated with that session.

       --stdin
	      Take audit records from stdin.

EXAMPLES

       To see this month's logins
       ausearch --start this-month --raw | aulast --stdin

SEE ALSO

       last(1), lastb(1), ausearch(8), aureport(8).

AUTHOR

       Steve Grubb

Red Hat 							     Nov 2008								AULAST:(8)

9 More Discussions You Might Find Interesting

1. Programming

segmentation fault

Discussion started by: omran

2. AIX

Segmentation fault

Discussion started by: jshaulis

3. Programming

segmentation fault

Discussion started by: rockgal

4. Shell Programming and Scripting

guess the fault :)

Discussion started by: maskot

5. Linux

Segmentation fault

Discussion started by: big123456

6. Programming

why segment fault,

Discussion started by: yanglei_fage

7. Red Hat

Red Hat linux fault information

Discussion started by: zhaoyy

8. Programming

Using gdb, ignore beginning segmentation fault until reproduce environment segmentation fault

Discussion started by: pooyair

9. Programming

C. To segmentation fault or not to segmentation fault, that is the question.

Discussion started by: wisecracker

LEARN ABOUT SUSE

aulast