opendir failure

[Jerry Schwartz]

Hello, Scott...

Dec 15, 2010 at 10:19, Scott Little wrote to Jerry Schwartz:

SL> [ On 2010-12-14 at 10:05:26, Jerry Schwartz wrote to Ross Cassell ]

RC>>> On a non linux box, shouldnt you be specifying g:\\bink
JS>> I am!!!

SL> Try a forward slash.

SL> It's been a supported path separator since the DOS days, but "clever"
SL> programs that try to validate paths don't always recognise it.

I think my original comments got lost somewhere.

BinkD has no problem actually finding my outbound and inbound directories, both
of which are on the G: drive. So far as I can tell, everything works just fine
in that regard.

I was looking at my logs for a totally unrelated reason, and I spotted those
messages.

I repeat, everything works -- so I think the punctuation in my config file is
okay.

Regards,

Jerry Schwartz

mailto:***@comfortable.com
http://www.writebynight.com

[Mike Tripp]

Hello Jerry!

14 Dec 10 21:51, Jerry Schwartz wrote to Scott Little:

JS> BinkD has no problem actually finding my outbound and inbound
JS> directories, both of which are on the G: drive. So far as I can tell,
JS> everything works just fine in that regard.

JS> I was looking at my logs for a totally unrelated reason, and I spotted
JS> those messages.

JS> I repeat, everything works -- so I think the punctuation in my config
JS> file is okay.

I think it just means that the share drive was temporarily inaccessible due to
an issue with the network or the server system (sharing violation, busy, error,
rebooting). BinkD will just look for the drive again on the next access
attempt and display the error rather than puke and quit.

My Netware server takes a little manual work to recover from a power outage due
to its age, and I see these errors in the daemon window until the server comes
back up. Of course they are on the screen and not in the log files, for
obvious reasons.<g>

.\\ike

[Jerry Schwartz]

Hello, Mike...

Dec 15, 2010 at 08:19, Mike Tripp wrote to Jerry Schwartz:

MT> I think it just means that the share drive was temporarily
MT> inaccessible due to an issue with the network or the server system
MT> (sharing violation, busy, error, rebooting). BinkD will just look
MT> for the drive again on the next access attempt and display the error
MT> rather than puke and quit.

Well, much of that doesn't apply in this case. The two "machines" are actually
one physical machine, using a network share is just the way the virtual machine
and the host machine can use the same disk.

I don't know, I may not care.

Regards,

Jerry Schwartz

mailto:***@comfortable.com
http://www.writebynight.com

[Scott Little]

[ On 2010-12-14 at 21:51:42, Jerry Schwartz wrote to Scott Little ]

JS> BinkD has no problem actually finding my outbound and inbound
JS> directories, both of which are on the G: drive. So far as I can tell,
JS> everything works just fine in that regard.

Does the message appear at any particular interval?

It's possible that one part of the program is OK with blackslash and another
isn't, so most of it works but still generates an error from somewhere not too
important. As for network share availability... the last version or two (or
three) of VirtualBox had some nasty packet loss under load, so that might be
it.


-- Scott Little [fidonet#3:712/848 / ***@sysgod.org]

[Jerry Schwartz]

Hello, Scott...

Dec 17, 2010 at 19:58, Scott Little wrote to Jerry Schwartz:

SL> [ On 2010-12-14 at 21:51:42, Jerry Schwartz wrote to Scott Little ]

JS>> BinkD has no problem actually finding my outbound and inbound
JS>> directories, both of which are on the G: drive. So far as I can tell,
JS>> everything works just fine in that regard.

SL> Does the message appear at any particular interval?

Actually, it seems to happen at one-minute intervals when there's nothing going
on.

Regards,

Jerry Schwartz

mailto:***@comfortable.com
http://www.writebynight.com

[Paul Quinn]

Hi! Jerry,

In a message to Scott Little you wrote:

JS>>> BinkD has no problem actually finding my outbound and inbound
JS>>> directories, both of which are on the G: drive. So far as I can
JS>>> tell, everything works just fine in that regard.

SL>> Does the message appear at any particular interval?

JS> Actually, it seems to happen at one-minute intervals when there's
JS> nothing going on.

A couple of questions, if I may, Jerry:

Is there a directory called 'bink' on g: drive? Look closely, now. :)

Is g: drive the currently 'logged' drive? If not, then what you're seeing
-could- be a netbios "ghost in the machine" thing where network drives cannot
be tested for their existence by some MS utls.

Cheers,
Paul.