Hello Roland,
In Debian Squeeze deleting /tmp is supposedly controlled by setting TMPTIME=x
in /etc/default/rcS. "0" means - delete /tmp, a negative number means don't
ever delete it, while a positive number indicates the number of days till
deletion.
By the way - even though I reverted to using the odbc-connection to MySQL (it
works just fine), I tried to install libreoffice-mysql-connector. In doing
so, it "broke" my LibreOffice system (I couldn't open ANY files anymore!).
The reason seems to be the Libre..-connector goes together with 3.3.2,
while I had 3.4.0 installed. I obiously ended up with a "mixed-up" system.
So, for me - it's odbc for the moment...
Thanks for your help
Regards
H
On Mon, 06 Jun 2011 16:23:53 +0200, Roland Hughes <roland@logikalsolutions.com> wrote:
There are flags that you need to set. Do a search on-line. In OpenSuSE
you set them with YAST, I forget where you set them with Ubuntu. /tmp
is only cleaned at system boot, when it "should" be empty.
Ubuntu has a lot of bugs with respect to cleaning of /tmp at system
boot. It basically doesn't work if /tmp is on a different disk drive
than the system disk.
On Sun, 2011-06-05 at 21:25 +0200, Heinrich Stoellinger wrote:
Hi Roland,
I use Debian-Squeeze at the moment. Having spent too much time already doing
things where I don't understand all the possible ramifications - I hesitate
to delete /tmp. Is it o.k. for sure to do so or might I "hurt" something
in doing so down in the depth of Linux?
Regards
H
On Sun, 05 Jun 2011 19:58:52 +0200, Roland Hughes <roland@logikalsolutions.com> wrote:
> I don't think it is a bug...I'm willing to bet the "connector" you have
> is for a different version of MySQL or a different version of the
> client.
>
> What distribution are you using? Not all Linux distros delete /tmp on
> boot. You need to ensure that your distro is deleting /tmp on boot,
> delete the user directory, REBOOT, then try your MySQL thing. OpenSuSE
> does not delete /tmp by default to speed booting. Ubuntu has a lot of
> bugs and only deletes it randomly under certain situations. A lot of
> stuff, especially for uno it appears, gets left out in /tmp.
>
>
> On Sun, 2011-06-05 at 18:57 +0200, Heinrich Stoellinger wrote:
>
>> Hi Tom,
>> For me, the suggestion to delete the user directory did not work. The weird
>> thing is that when downloading and then trying to activate the mysql-connector,
>> I get the message that loading "mysqlc.uno.so" failed. That module is present
>> in the directory mentioned in the message.
>> As I mentioned before - I have gone over to usinge odbc and I am quite happy
>> doing so. I hope that some time in the future somebody cleverer than me will
>> fix the bug...
>> Regards
>> H
>>
>>
>> On Sun, 05 Jun 2011 16:27:06 +0200, Tom Davies <tomdavies04@yahoo.co.uk> wrote:
>>
>> > /home/user/.libreoffice/3/user
>>
>>
>> --
>> Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
>>
>
>
--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
In case of problems unsubscribing, write to postmaster@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-users] Re: Native MySQL-connection (continued)
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.