Statistics doesn't show disk info for network shares

[UncleJohnsBand]

Ok.....I had to dig into this one....I was not the creator of this code and have not done much work in this area.

I determined that the code that is currently in place requires that the network drive actually be mapped to the local machine....kind of defeats the purpose of unc....

I did find a way to get the space values for a network drive without actually mapping the drive to the local machine running gbpvr. However.....for it to work I had to change the gbpvrrecordingservice to run using a local account that had access to the share rather than just using the local system account.

I think I am going to combine these two methods of access into one piece of code....first looking via the new approach and then falling into the existing approach if there is an access issue with the new method.

This means for space determination to work correctly the user will either need to run the gbpvrrecordingservice under a local account with the access rights to the network share (if the share is unprotected on a NAS the local system account would probably still work) or they will need to map the network drive locally.

I'll post a patch to test as soon as it is done.

[UncleJohnsBand]

Attached is a patch with the new coding....

You need to do one of the two following things to be able to see the space on the network drive.

• If the network drive is on a machine that needs access to get to the share then change the gbpvrrecordingservice to run under a local account that has access to the network share.
  • If no user credentials are required to access the share then then I do not believe you will need to do anything to the gbpvrrecordingservice account settings.
• Physically map the drive to the local gbpvr pc.

Let me know if this works and post the logs.

Thanks.

[mkenyon2]

Nice, didn't have to change the Service user. It's funny, since the \\ghz\Video share is actually D:\Video. But I mapped it so that \\ghz\Video is also V:\ and it's working.

[UncleJohnsBand]

Nice, didn't have to change the Service user. It's funny, since the \\ghz\Video share is actually D:\Video. But I mapped it so that \\ghz\Video is also V:\ and it's working.

Thats good....if you look in your log you should see a message as to what technique was used to render the space.

Since you have the share mapped it may have used the original technique....I coded it to use the new technique first then if there is an error fall back to the technique that was already in place.

Can you let me know what comes out in the log.

Thanks.

[mkenyon2]

Here ya go... thank you very much.

[UncleJohnsBand]

Here ya go... thank you very much.

Thanks....it is using the native call rather than the original mapped drive....so this seems to be working nicely.