09-13-2013
Thunar works when I run the amd64 version of OpenBSD with xfce, but when I run my Sparc box, an old Blade 100, then Thunar no longer works properly. It's probably an OpenBSD issue, guess I will live with it, by not clicking on it! Or go FreeBSD, which on Sparc is all text based, cause xorg is not installed by default and the compiling from ports takes too many days on the old machine, and nothing is gained by it.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have xfce installed with thunar as the file manager. It would be very productive to have a tool that allows the user to find files, similar to catfish (which seems to have been developed by the Ubuntu team). Does such a utility exist for non-Ubuntu OS's? (0 Replies)
Discussion started by: figaro
0 Replies
2. UNIX Desktop Questions & Answers
I am using Thunar on FreeBSD 7.1 and XFCE. I would like the thunar window to reload automatically when a file has been added or deleted. Currently I press Ctrl-R, but perhaps a setting that I dont know of will do this automatically? (0 Replies)
Discussion started by: figaro
0 Replies
3. BSD
I am currently working on a project that involves running the lift framework on a sun sparc64 architecture. Due to limited support from more popular unix distros, I am running NetBSD 64-bit on the system.
Before i can even tackle trying to install lift, I have to be able to install... (1 Reply)
Discussion started by: techen
1 Replies
4. Solaris
Production server crashes when there is no traffic on it. Can only recover by going to ALOM and reboot the server. This seems to happen about the same time every month. The only good thing is the server is not in production at the time of the crash.
I have been unable to locate any information in... (5 Replies)
Discussion started by: Joeentech
5 Replies
5. Red Hat
Can someone tell my why every time I try to use 7z it freezes my system? I can't move my mouse, I can't type, I can't kill my xsession. I then restart my system and everything returns to normal. When I try to use 7z my system again freezes. (11 Replies)
Discussion started by: cokedude
11 Replies
6. Programming
Hi,
Can anyone tell me why the below program is crashing? and where exactly it is crashing. What is the corrective measure to be taken to make it work fine?
#include <iostream>
#include <cstring>
using namespace std;
class CString {
char* m_data;
public:
CString() :... (6 Replies)
Discussion started by: royalibrahim
6 Replies
7. BSD
I used to use x86 Linux clients for this years ago, but ceased all activity until last night. I have resurrected an old Sun Blade 100, which used to run Solaris 9, when I first owned it, in the 2003 period, but now is very much alive with 2 gig of new ram, and and extra 10 gig of drive space... (0 Replies)
Discussion started by: RichardET
0 Replies
8. UNIX for Dummies Questions & Answers
I have came across a few websites stating some custom actions for Thunar -
crunchbang
ubuntu
I tried inputting the stated commands to Thunar, but it doesn't display at all in mine.
I tried "gksu thunar %f" ( Opens current folder with root permissions.) , but when I right click in a... (0 Replies)
Discussion started by: Hijanoqu
0 Replies
9. UNIX and Linux Applications
I am trying to run apcupsd, but it will not retain contact the UPS
root@meow:/home/ethan/UPS/gapcmon-0.8.9# /etc/init.d/apcupsd start
Starting UPS power management:
A copy of the daemon is still running. If you just stopped it,
please wait about 5 seconds for it to shut down.... (0 Replies)
Discussion started by: Meow613
0 Replies
10. Web Development
The Apache server suddenly stops. I am running Debian Jessie
Here are some diagnostics:
root@meow:/var/www# apachectl configtest
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress... (4 Replies)
Discussion started by: Meow613
4 Replies
LEARN ABOUT ULTRIX
savecore
savecore(8) System Manager's Manual savecore(8)
Name
savecore - save a core dump of the operating system
Syntax
/etc/savecore [ options ] dirname [ system ] [ corename ]
Description
The command is meant to be called near the end of the file. The command saves the core dump of the system (assuming one was made) and
writes a reboot message in the shutdown log.
The command checks the core dump to be certain it corresponds with the current running ULTRIX. If it does, it saves the core image in the
file dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n. The trailing .n in the pathnames is replaced by a number which
increments each time is run in that directory.
After saving the core and namelist images, will save the error logger buffer into a predetermined file. The error logger buffer contains
information about why the crash occurred. After completes, the daemon will extract the error logger file and translate its contents into a
form familiar to the program.
Before writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the filesystem that
contains dirname than the number obtained from the file, a core dump is not done. If the file does not exist, savecore always writes out
the core file (assuming that a core dump was taken).
The command also writes a reboot message in the shut down log. If the system crashed as a result of a panic, also records the panic string
in the shut down log.
For partial crash dumps, creates a sparse core image file in dirname/vmcore.n. If this sparse core image file is copied or moved to
another location, the file expands to its true size which can take too much file system space. Hence, to copy or move sparse core image
files, you must use the command. The command has a conversion option to create sparse output files.
Options
-c Clears the core dump. This option is useful when the core dump is corrupted in a way that will not allow to save it safely. Use the
option with caution, because once it clears the core dump, the core dump cannot be retrieved.
-d dumpdev dumplo
Specifies the dump device and the dump offset when running on a system image other than the currently running system image. The pro-
gram assumes that the running system image is and it reads the dump device and dump device offset are different in the system image
that crashed, the option provides the correct dump device and dump device offset.
-e Saves only the error logger buffer into a file. If used, core or namelist images are not saved.
-f corename
Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device. This option
is used only for diskless workstations.
If the core dump was from a system other than /vmunix, the name of that system must be supplied as system. The program assumes that the
running image is
After successful completion, the core dump is cleared. Also, a message is written in the file which tells whether the dump succeeded or
failed.
Files
Shut down log
Current running ULTRIX system
See Also
dd(1), uerf(8)
savecore(8)