Thunar Crashes running XFCE 4.10 on Sparc64 , OpenBSD 5.3 Post: 302853371

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Finding files through Thunar

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?

2. UNIX Desktop Questions & Answers

Automatic reload of Thunar

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?

3. BSD

Installing OpenJDK on a Netbsd Sparc64 Server

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...

4. Solaris

Server crashes when not in use.

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. Red Hat

7z crashes system

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.

6. Programming

C++ program crashes

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() :...

7. BSD

Compiling BOINC/Seti@Home for OpenBSD 5.3 Sparc64

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...

8. UNIX for Dummies Questions & Answers

[Solved] Custom actions in Thunar doesn't display at all.

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...

9. UNIX and Linux Applications

Apcupsd crashes

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....

10. Web Development

Apache2 Crashes

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...

LEARN ABOUT BSD

savecore

SAVECORE(8)						      System Manager's Manual						       SAVECORE(8)

NAME

       savecore - save a core dump of the operating system

SYNOPSIS

       savecore dirname [ system ]

DESCRIPTION

       Savecore  is  meant to be called at the end of the /etc/rc file.  Its function is to save the core dump of the system (if one was made) and
       to write a reboot message in the shutdown log.

       It saves the core image in the file dirname/core.n and its corresponding namelist in dirname/unix.n.  The second argument is  the  namelist
       for the system which made the core image; the current system is always assumed to be /unix.  The trailing ".n" in the pathnames is replaced
       by a number which grows every time savecore is run in that directory.

       Before savecore writes out a core image, it reads a number from the file dirname/minfree.  If there are fewer free blocks on the file  sys-
       tem  which contains dirname than the number obtained from the minfree file, the core dump is not done.  If the minfree file does not exist,
       savecore always writes out the core file (assuming that a core dump was taken).

       Savecore also writes a reboot message in the shut down log.  If the system crashed as a result of  a  panic,  savecore  records	the  panic
       string in the shut down log too.

       If  savecore detects that the system time is wrong because of a crash (the time in the core image is after the current time), it will reset
       the system time to its best estimate of the time, which is the time in the core image plus the elapsed time since the reboot.  It announces
       the time that it set when this occurs.

FILES

       /usr/adm/shutdownlogshutdown log
       /unix		   current UNIX

BUGS

       The method used to determine whether a dump is present, and to prevent the same core image from being saved multiple times, is not elegant.
       This information should be passed to init by the system; however, this is difficult because the system may have to  be  rebooted  a  second
       time if the root filesystem is patched.

3rd Berkeley Distribution													       SAVECORE(8)