Relocating ~/.xsession-errors
Hi, I've recently installed FreeBSD 8.0RC1 on my Acer Aspire One netbook, and so far things are working out OK. I'm using the SSD model, and since these netbooks have a notoriously slow SSD write speed, I'm trying to get rid of as much writes as possible. Furthermore, reducing writes might make it live longer. One of the remaining issues is ~/.xsession-errors. I'm using GNOME, and many GNOME applications have the nasty habit of spamming .xsession-errors with a lot of debug assertions (which apparently aren't lethal, since noone ever bothered to fix them..), and I know from experience that this file can see a lot of activity. I'd like to relocate this file to a tmpfs ramdisk, if possible. It would be perfect if I could make it log through syslog, since that would allow me to use newsyslog for logrotation (and thus keep the size of the log at bay), but I suspect this is asking too much. In the past, on Fedora Core and older versions of Ubuntu, I used a dirty trick I picked up on a webforum: Have ~/.xsession-errors be owned by root:wheel, and mark it as system immutable. That caused the .xsession-errors to be moved to /tmp, which is exactly where I want it to be, but that doesn't seem to work anymore. Instead, it's writing the error log to ~/.xsession-errors., with a random string. Does anyone know an alternate way to move this logfile, or if everything else fails how to silence it? -- Martijn van Buul - p...@dohd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Relocating ~/.xsession-errors
* Martijn van Buul: Does anyone know an alternate way to move this logfile, or if everything else fails how to silence it? I forgot to mention that I'm using gdm, but I'm not opposed to changing that. -- Martijn van Buul - p...@dohd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Relocating ~/.xsession-errors
* Polytropon: On Tue, 13 Oct 2009 08:02:19 + (UTC), Martijn van Buul p...@dohd.org wrote: I'd like to relocate this file to a tmpfs ramdisk, if possible. Have you tried using a symlink? I'm not sure if this will work across partitions... Symlinks work across partitions, but the problem is that symlinks (or hardlinks for that matter..) won't work here. GDM is responsible for setting up the redirection, and before doing so it moves the existing .xsession-errors to .xsession-errors.old. This is intentional, so in case of a suddenly terminating X session the old logging of the previous session is still available. This means that the (symbolic) link will just end up being moved to .xsession-errors.old, thus defeating the purpose. Does anyone know an alternate way to move this logfile, or if everything else fails how to silence it? Symlink to /dev/null? :-) Alas :) Thanks for thinking along with me. -- Martijn van Buul - p...@dohd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Relocating ~/.xsession-errors
* Martijn van Buul: Hi, I've recently installed FreeBSD 8.0RC1 on my Acer Aspire One netbook, and so far things are working out OK. I'm using the SSD model, and since these netbooks have a notoriously slow SSD write speed, I'm trying to get rid of as much writes as possible. Furthermore, reducing writes might make it live longer. OK, I fixed my own problem, but I'm not overly happy with it. Apparently this filename and location are compile-time constants, so I had to revert to making a patch and compiling my own package. I would've loved to avoid this since it would make updating harder, but alas. It's a bit ironic to see that in a world littered of XML schemas, config files, gconf-voodoo and other configuration options you STILL end requiring a patched binary. Ah well :) -- Martijn van Buul - p...@dohd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
help! directories changed into regular files! :(
Hi, I remembered thinking, should i backup the directory tree before this chang? nah ;-) i used sed in a directory with subdirs, and it changed all directories into normal files :( the exact command: sed -i -e s/'pm_properties\([^a-z]\)/#__properties\1/g' * after which i discovered it had name the directories name-e and had turned into regular files. no warnings whatsoever. (btw, yes i know that it should have been -i.orig) weird thing is, i can't reproduce the bug, and the command history wasn't big enough to figure out what was so special about this particular situation... sed sais 'in-place editing only works for regular files' but this time it didn't my question though: is there _any_ way to flip the bit that marks the file being a directory? it would really be helpful to me because i've just lost a lot of work. any ideas? bye Martijn. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: help! directories changed into regular files! :(
Hello, Once upon a Tue, Dec 05 2006, Andrew Pantyukhin hit keys in the following order: The general idea is that kernel never permits *any* write access to directory files even if you have root privileges. well, it happened... i was root atm, in a jail, but i'll try to recreate the bug... Please check once again, what your problem might be. Try backing up your disk with dd and running fsck, or run fsck on a snapshot. too bad its on my live webserver... i can do all this and still get nowhere, reading from your answer i hit something that is not possible. so i won't be able to recreate it anyway.. my problem remains the same, no argueing about it, my directories _did_ turn into files. And please use shorter lines. sorry about that, i forgot to setup my textwith... 72 chars is okay right? bye martijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: help! directories changed into regular files! :(
Once upon a Tue, Dec 05 2006, martijn hit keys in the following order: Once upon a Tue, Dec 05 2006, Andrew Pantyukhin hit keys in the following order: The general idea is that kernel never permits *any* write access to directory files even if you have root privileges. well, it happened... i was root atm, in a jail, but i'll try to recreate the bug... One more thing, it happened on a nullfs mounted drive... Could that be the problem? martijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KINDA SOLVED: Re: help! directories changed into regular files! :(
Heheh, now i can reproduce it ;-) I did an in-place searchreplace with sed on a bunch of symlinks to directories, but i didn't remember they were symlinks. When you do that, the symlink gets backed up as a normal file. probably not the behauviour we want, but hey, thats live when you give stupid commands ;-) martijn. Once upon a Tue, Dec 05 2006, martijn hit keys in the following order: Hi, I remembered thinking, should i backup the directory tree before this chang? nah ;-) i used sed in a directory with subdirs, and it changed all directories into normal files :( the exact command: sed -i -e s/'pm_properties\([^a-z]\)/#__properties\1/g' * after which i discovered it had name the directories name-e and had turned into regular files. no warnings whatsoever. (btw, yes i know that it should have been -i.orig) weird thing is, i can't reproduce the bug, and the command history wasn't big enough to figure out what was so special about this particular situation... sed sais 'in-place editing only works for regular files' but this time it didn't my question though: is there _any_ way to flip the bit that marks the file being a directory? it would really be helpful to me because i've just lost a lot of work. any ideas? bye Martijn. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
freeBSD server
Hello, I am planning on running a BSD server with DNS and an apache server, maybe an dhcp server to. (No X). What would be the minimum requirements for this? Martijn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cdrom mount problem
Hi chris, You first have to unmount the cdrom before you can mount a new cd, you can do that by typing: umount /cdrom greets, Martijn On Thursday 18 March 2004 16:35, Chris wrote: *This message was transferred with a trial version of CommuniGate(tm) Pro* In summary: the only way to mount my cdrom after burning an ISO is to reboot first. Prior to 5.2.1-RC1, I was able to burn ISO imaged onto a CDRW using burncd, then later mount /cdrom to access the files I burned. With RC1 and now with 5.2.1-RELEASE, a strange thing happens: After a reboot, I can mount /cdrom and access files on the disc. But if I re-burn the ISO file, then try to mount /cdrom, I get this: cd9660: /dev/acd0: Input/output error BUT... if I reboot THEN try to access that same disk, it works fine. Thanks, Chris _ Email harvesters eat this: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
openSSL certificate key's
I was wondering if anyone could tell me how I can generate my openSSL certificate key's. Greets, Martijn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problems with interchange-4.8.7 on FreeBSD 5.1 RELEASE
Hi, I am trying to install and run interchange on my FreeBSD server. I first updated the ports directory- succesful. Then I did a make -DCHECK_FOR_IC_USER all install. This went all well. A new user and group (interch) is added and it seems that it is installed properly. Next thing to do is creating a new catalog for interchange. Therfor I did the following: % cd /usr/local % bin/makecat A wizzard starts and I accepted all the defaults. And somewhere the wizzard is asking for the location of vlink. As I did not know what the right thing to do was. I searched for this file and found it in /usr/local/interchange/src/ The above path is exactly what I typed in during the makecat. After the makecat has finished I started the interchange server. Via su interch. (first I had to change the shell of interch via chpass, otherwise it was not possible to su). All seemed to go well. But after all this I can see the file 'foundation' in cgi-bin but it will not run. Browsing to http://myIP/cgi-bin/foundation gives the following error in my /var/log/httpd-error.log. -/var/log/httpd-error.log - --- [Wed Feb 18 16:28:54 2004] [error] (8)Exec format error: exec of /usr/local/www/cgi-bin/foundation failed [Wed Feb 18 16:28:54 2004] [error] [client 192.168.1.3] Premature end of script headers: /usr/local/www/cgi-bin/foundation- I have tried the complet procedure from making the port till making the catalog for 4 times now. I even have rebuild my kernel with maxusers 256 as red somewhere this could be the problem with this type of error on an FreeBSD system running interchange. Can someone help me on this subject. output uname -a FreeBSD freebsd.tmenv.com 5.1-RELEASE FreeBSD 5.1-RELEASE #1: Wed Feb 18 13:34:02 CET 2004 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/FREEBSD i386 ---Best regards,Martijn Dekker. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
