logfile appears in homedir since 1.6.4

Discussions related to using VirtualBox on Linux hosts.

logfile appears in homedir since 1.6.4

Postby Muts » 1. Aug 2008, 13:29

hi all

I upgraded to 1.6.4 today, and when I run VirtualBox the logfile suddenly appears in my homedir (each time I run it). I searched the forum, all config options in the GUI and also in the config files themselves, but I did not find a way to relocate these logfiles.

It would also be good if I could simply disable these logfiles, but perhaps that's not the best solution.

This might be important: I made a symlink from a seperate harddrive to ~/.VirtualBox, perhaps this has something to do with it? I don't have enough space on my root filesystem, and this way I can change/update my distro more easily.
Everything works fine like before, only those logfiles suddenly appear. :(
dependency hell? => /bin/there/done/that
Muts
 
Posts: 39
Joined: 20. Jul 2008, 16:55

Re: logfile appears in homedir since 1.6.4

Postby greenpossum » 1. Aug 2008, 15:56

Hmm, the logfiles have been under $HOME since previous versions for me. Since you are running Vbox as yourself, this is one place that's guaranteed to be writable. If you don't like them there, you could make symlinks for the Logs directories. They're not very large, what's the problem with them there?
greenpossum
Volunteer
 
Posts: 98
Joined: 11. Jul 2008, 08:10

Postby Muts » 1. Aug 2008, 16:13

I only have a few important files (and dirs) in my homedir, and I want it to stay uncluttered. When a new log is created each time I use VirtualBox, this gets out of hand very quickly.
Obviously I could manually delete all those logfiles once in a while, but I thought computers could be set up so that things work automatically. :D

But with the symlink, do you mean there normally is a directory for logs? Like ~/.VirtualBox/logs/ or something? I would guess that VirtualBox wil put logfiles there by default, if this is your suggested solution.
dependency hell? => /bin/there/done/that
Muts
 
Posts: 39
Joined: 20. Jul 2008, 16:55

Postby greenpossum » 1. Aug 2008, 17:07

Muts wrote:I only have a few important files (and dirs) in my homedir, and I want it to stay uncluttered. When a new log is created each time I use VirtualBox, this gets out of hand very quickly.
Obviously I could manually delete all those logfiles once in a while, but I thought computers could be set up so that things work automatically. :D


Hmm, $HOME is where I do most of my work and I back it up often. The system I can reinstall from media and from the net. So my home directories are "cluttered" because I use them a lot and that's the way I like it. :)

You could always use a cron job to trim the log files.

But with the symlink, do you mean there normally is a directory for logs? Like ~/.VirtualBox/logs/ or something? I would guess that VirtualBox wil put logfiles there by default, if this is your suggested solution.


Logfiles are under ~/.Virtualbox/Machines/<VMName>/Logs
greenpossum
Volunteer
 
Posts: 98
Joined: 11. Jul 2008, 08:10

Postby Muts » 1. Aug 2008, 17:10

Logfiles are under ~/.Virtualbox/Machines/<VMName>/Logs

I see.

But I still think it's odd that logfiles suddenly appear in my homedir. I really don't like that. :D
dependency hell? => /bin/there/done/that
Muts
 
Posts: 39
Joined: 20. Jul 2008, 16:55

Postby h1d » 1. Aug 2008, 17:15

Logs doesn't need to be put right under home directory and doesn't need to know if it's guaranteed to be writeable when it can just create a log directory if it isn't there. If it's not writeable, blame the user instead of cluttering the home directory without a way to change it.

what's the problem with them there?


Problem is, everyone doesn't think the same way as you do 8)

I guess it's a bug perhaps? They are supposed to go under the quoted directory usually.

I guess I semi duped the issue post.
h1d
Volunteer
 
Posts: 170
Joined: 3. Jul 2008, 02:10

Postby greenpossum » 2. Aug 2008, 02:00

h1d wrote:Logs doesn't need to be put right under home directory and doesn't need to know if it's guaranteed to be writeable when it can just create a log directory if it isn't there. If it's not writeable, blame the user instead of cluttering the home directory without a way to change it.


Sure you can put it in as an enhancement request I suppose, by all means do that. After all if the machines and VDI directory are settable...

But you have to remember that Vbox isn't your standard system daemon, it is started by a normal user. So it doesn't have the permissions to create a directory just anywhere. Usually the only other places writable by a normal user are /tmp and /var/tmp.
greenpossum
Volunteer
 
Posts: 98
Joined: 11. Jul 2008, 08:10

Postby greenpossum » 2. Aug 2008, 02:16

Muts wrote:But I still think it's odd that logfiles suddenly appear in my homedir. I really don't like that. :D


The logfiles were already under ~/.Virtualbox/Machines/<VMName>/Logs in my install of 1.6.2. Maybe you upgraded from an even older version so you were surprised and I was not.

Wait a moment, do you literally mean that you have logfiles in ~? That's never happened to me. I thought you meant somewhere under ~. Maybe your config came from an old version and didn't get migrated over to the currect locations.
greenpossum
Volunteer
 
Posts: 98
Joined: 11. Jul 2008, 08:10

Postby h1d » 2. Aug 2008, 03:12

Maybe you could try then? At least my observation under OS X host was the log files appeared right in the applications folder. (Equivalent to log files appearing right under "Program Files" for Windows. [I didn't check what would happen on Windows host yet]) This was right since 1.6.4, wasn't like it on 1.6.2.

It's supposedly just a debug log that isn't supposed to be there.
h1d
Volunteer
 
Posts: 170
Joined: 3. Jul 2008, 02:10

Postby greenpossum » 2. Aug 2008, 04:42

h1d wrote:Maybe you could try then?


Try what? I installed and ran 1.6.4 last night and the log was in ~/.Virtualbox/Machines/<VMName>/Logs/ just like they always were. Which is why I was puzzled why the OP was surprised since there was no change.
greenpossum
Volunteer
 
Posts: 98
Joined: 11. Jul 2008, 08:10

Postby Muts » 2. Aug 2008, 11:11

I had 1.6.2 and upgraded to 1.6.4, so I don't think the config was too old. :)
dependency hell? => /bin/there/done/that
Muts
 
Posts: 39
Joined: 20. Jul 2008, 16:55

Postby Peri_quete » 2. Aug 2008, 12:19

same problem
upgrade 1.6.2. to 1.6.4
Peri_quete
 
Posts: 14
Joined: 4. May 2008, 17:59

Postby TerryE » 2. Aug 2008, 12:50

Guys, guys, guys, (well mostly guys :roll: ), this is just an "oops" on the part the VBox team. Moral: never release a new kit on Friday if no one is in over the W/E. :lol:

I suspect a new 1.6.4 will be posted on Monday without this debug logging enabled.
Read the Forum Posting Guide
Google your Q site:VirtualBox.org or search for the answer before posting.
TerryE
Site Moderator
 
Posts: 3521
Joined: 28. May 2008, 08:40
Primary OS: Ubuntu 8.04
VBox Version: PUEL
Guest OSses: Ubuntu 8.04 JeOS, Ubuntu 8.04 Workstation, Debian Lenny, Windows XP

Postby suzuki » 3. Aug 2008, 11:46

By reading the source, I found a workaround: set the environment variable VBOX_LOG_DEST=nofile.

For Mac OS X, add<key>
    VBOX_LOG_DEST</key>
    <string>nofile</string>
in your ~/.MacOSX/environment.plist, or add
    <key>LSEnvironment</key>
    <dict><key>VBOX_LOG_DEST</key><string>nofile</string></dict>
in VirtualBox.app/Contents/Info.plist.
suzuki
 
Posts: 1
Joined: 3. Aug 2008, 11:17

Postby TerryE » 3. Aug 2008, 13:01

I confirm what suzuki says.
Read the Forum Posting Guide
Google your Q site:VirtualBox.org or search for the answer before posting.
TerryE
Site Moderator
 
Posts: 3521
Joined: 28. May 2008, 08:40
Primary OS: Ubuntu 8.04
VBox Version: PUEL
Guest OSses: Ubuntu 8.04 JeOS, Ubuntu 8.04 Workstation, Debian Lenny, Windows XP

Next

Return to VirtualBox on Linux Hosts

Who is online

Users browsing this forum: dr_smit, Yahoo [Bot] and 10 guests