10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hello all,
i am having problem in accessing a directory.I dont think its a permission issue.can anyone help me out. I am using korn sell
code:
$ ls -ltr sc*
lrwxrwxrwx 1 essbase essbase 21 Oct 8 2010 sc_ssp -> /work/nfs/nas2/sc_ssp
$ cd sc_ssp
ksh: sc_ssp: not found
$ (6 Replies)
Discussion started by: manid
6 Replies
2. Shell Programming and Scripting
Hi All,
I am encountering an unexpected problem while running my process, using daemon placed in /etc/init.d/.
I have a process that is opening shared library using dlopen.
When I run my process on the command line, it is able to open the library. But when I used daemon to run my process, I... (0 Replies)
Discussion started by: qwerty-1
0 Replies
3. Ubuntu
My PC (Esprimo, 3 yeas old) has one hard drive having 2 partitions C: (80 GB NTFS, XP) and D: (120 GB NTFS, empty) and and a 200 MB area that yet is not-partitioned.
I would like to try Ubuntu and to install Ubuntu on the not-partitioned area . The idea is to have the possibility to run... (7 Replies)
Discussion started by: C.Weidemann
7 Replies
4. Shell Programming and Scripting
Well, my script started off to do what i wanted. Now, i think its not recognizing the pattern so its not moving anything.
What i have to do is execute my script command for the move to take effect. So i did that and yayy it worked.
Strange thing is that my DESTDIR was empty to begin with.... (2 Replies)
Discussion started by: oxoxo
2 Replies
5. Solaris
I am attempting to install a new internal disk. System is running Solaris 9/05.
I did a touch /reconfigure and see the disk when I type format command. But the cxtxdx disk shows "drive not available".
Any idea if we are supposed to configure anything with this disk? I have not format the disk... (10 Replies)
Discussion started by: bluridge
10 Replies
6. Solaris
Hello,
I just bought a nice ultra 60 with 2x36gb scsi disks (fujitsu MAJ3364MC, sun partnr 540-4521).
If i do a probe-scsi-all in obp the disk anounces itself as SUN36G.
In a booted system however, I can only use 9 gb and the disk is seen in format as 9.0 gb.
My own wild uneducated... (4 Replies)
Discussion started by: poltergeist
4 Replies
7. Shell Programming and Scripting
I am using SunOS 5.9 and I don't know why all my commands are getting executed as if an extra 'enter' has been pressed.
What could be the reason and how to correct it?
Please help.
Asty (2 Replies)
Discussion started by: Asty
2 Replies
8. Linux
I have installed Fedora Core on a Toshiba Satellite Pro4600 laptop recently I have experienced a rather mysterious problem if I touch anything specially the keyboard or mouse I see this stuff “67yujhnmyyy” straight away some time it won't stop for while like this... (5 Replies)
Discussion started by: kemobyte
5 Replies
9. UNIX for Dummies Questions & Answers
Hi..
Some of my application were not running properly due to lack of virtual memory.....so wht i did add one free harddisk as swap file system...and increased the swap memory..
But since than my root file system is showing 100% full thr is no space left...is thr any link between these two..... (1 Reply)
Discussion started by: Prafulla
1 Replies
10. UNIX for Dummies Questions & Answers
I¡¯m a network operator, mine is an IBM PC server 320, operating system SCO unix 3.2v4.2, triton 3.1 of Baan. Recently, my server went dead every a few hours, no sign & signal shows malfunction suddenly. It looks like a sudden power failure, but the indicator of main power supply is on. Normal... (1 Reply)
Discussion started by: lyhsm
1 Replies
apport-cli(1) General Commands Manual apport-cli(1)
NAME
apport-cli, apport-gtk, apport-kde - Apport user interfaces for reporting problems
SYNOPSIS
apport-cli
apport-cli [ --save file ] symptom | pid | package | program path | .apport/.crash file
apport-cli -f
apport-cli -f -p package -P pid
apport-cli -u report-number
Same options/arguments for apport-gtk and apport-kde.
DESCRIPTION
apport automatically collects data from crashed processes and compiles a problem report in /var/crash/. This is a command line frontend for
reporting those crashes to the developers. It can also be used to report bugs about packages or running processes.
If symptom scripts are available, it can also be given the name of a symptom, or be called with just -f to display a list of known symp-
toms.
When being called without any options, it processes the pending crash reports and offers to report them one by one. You can also display
the entire report to see what is sent to the software developers.
When being called with exactly one argument and no option, apport-cli uses some heuristics to find out "what you mean" and reports a bug
against the given symptom name, package name, program path, or PID. If the argument is a .crash or .apport file, it uploads the stored
problem report to the bug tracking system.
For desktop systems with a graphical user interface, you should consider installing the GTK or KDE user interface (apport-gtk or apport-
kde). They accept the very same options and arguments. apport-cli is mainly intended to be used on servers.
OPTIONS
-f, --file-bug
Report a (non-crash) problem. If neither --package, --symptom, or --pid are specified, then it displays a list of available symp-
toms. If none are available, it aborts with an error.
This will automatically attach information about your operating system and the package version etc. to the bug report, so that the
developers have some important context.
-s symptom, --symptom=symptom
When being used in --file-bug mode, specify the symptom to report the problem about.
-p package, --package=package
When being used in --file-bug mode, specify the package to report the problem against.
-P pid, --pid=pid
When being used in --file-bug mode, specify the PID (process ID) of a running program to report the problem against. This can be
determined with e. g. ps -ux.
-c report, --crash-file=report
Upload a previously processed stored report in an arbitrary file location. This is useful for copying a crash report to a machine
with internet connection and reporting it from there. Files must end in .crash or .apport.
-u report-number, --update-report report-number
Run apport information collection on an already existing problem report. The affected package is taken from the report by default,
but you can explicitly specify one with --package to collect information for a different package (this is useful if the report is
assigned to the wrong package).
--save filename
In --file-bug mode, save the collected information into a file instead of reporting it. This file can then be reported with --crash-
file later on.
-w, --window
Point and click at the application window against which you wish to report the bug. Apport will automatically find the package name
and generate a report for you. This option can be specially useful in situations when you do not know the name of the package, or if
the application window has stopped responding and you cannot report the problem from the "Help" menu of the application.
ENVIRONMENT
APPORT_IGNORE_OBSOLETE_PACKAGES
Apport refuses to create bug reports if the package or any dependency is not current. If this environment variable is set, this
check is waived. Experts who will thoroughly check the situation before filing a bug report can define this in their ~/.bashrc or
temporarily when calling the apport frontend (-cli, -gtk, or -kde).
FILES
/usr/share/apport/symptoms/*.py
Symptom scripts. These ask a set of interactive questions to determine the package which is responsible for a particular problem.
(For some problems like sound or storage device related bugs there are many places where things can go wrong, and it's not immedi-
ately obvious for a bug reporter where the problem is.)
AUTHOR
apport and the accompanying tools are developed by Martin Pitt <martin.pitt@ubuntu.com>.
Martin Pitt August 01, 2007 apport-cli(1)