On Feb 16 08:17, Ryan Johnson wrote:
> On 16/02/2012 6:09 AM, Corinna Vinschen wrote:
> >I just applied a patch which calls NetUseGetInfo on SMB drives in
> >the cygdrive::readdir call. As I mentioned above, if the function
> >returns OK, we fetch the inode number. If the function returns
> >"Dis
Hi Corinna,
On 16/02/2012 6:09 AM, Corinna Vinschen wrote:
On Feb 15 10:24, Corinna Vinschen wrote:
On Feb 14 14:50, Ryan Johnson wrote:
Heisenburg? Impossible to know both what SMB share a mount points to
and whether it's currently connected?
Almost. You have to access the share to find out
On Feb 15 10:24, Corinna Vinschen wrote:
> On Feb 14 14:50, Ryan Johnson wrote:
> > Heisenburg? Impossible to know both what SMB share a mount points to
> > and whether it's currently connected?
Almost. You have to access the share to find out if it is really
connected because the information ret
On Feb 15 04:35, Mark Geisert wrote:
> Corinna Vinschen writes:
> > > > Does anybody know a system call which allows to fetch the network drive
> > > > state (connected/not connected) without a billion microsecond timeout?
> > >
> > > I just looked into this and I really don't see a way. While th
On Feb 14 14:50, Ryan Johnson wrote:
> On 14/02/2012 12:57 PM, Corinna Vinschen wrote:
> >On Feb 14 12:46, Ryan Johnson wrote:
> >>On 14/02/2012 11:26 AM, Corinna Vinschen wrote:
> >>>On Feb 14 10:47, Ryan Johnson wrote:
> On 14/02/2012 10:17 AM, Corinna Vinschen wrote:
> >Does anybody know
Corinna Vinschen writes:
> > > Does anybody know a system call which allows to fetch the network drive
> > > state (connected/not connected) without a billion microsecond timeout?
> >
> > I just looked into this and I really don't see a way. While there's a
> > NetUseGetInfo call, which is pretty
On 14/02/2012 12:57 PM, Corinna Vinschen wrote:
On Feb 14 12:46, Ryan Johnson wrote:
On 14/02/2012 11:26 AM, Corinna Vinschen wrote:
On Feb 14 10:47, Ryan Johnson wrote:
On 14/02/2012 10:17 AM, Corinna Vinschen wrote:
Does anybody know a system call which allows to fetch the network drive
sta
On Feb 14 12:46, Ryan Johnson wrote:
> On 14/02/2012 11:26 AM, Corinna Vinschen wrote:
> >On Feb 14 10:47, Ryan Johnson wrote:
> >>On 14/02/2012 10:17 AM, Corinna Vinschen wrote:
> >>>Does anybody know a system call which allows to fetch the network drive
> >>>state (connected/not connected) withou
On 14/02/2012 11:26 AM, Corinna Vinschen wrote:
On Feb 14 10:47, Ryan Johnson wrote:
On 14/02/2012 10:17 AM, Corinna Vinschen wrote:
Does anybody know a system call which allows to fetch the network drive
state (connected/not connected) without a billion microsecond timeout?
[...]
What if we p
On Feb 14 18:18, Corinna Vinschen wrote:
> On Feb 14 16:17, Corinna Vinschen wrote:
> > So, even if we fix fstat, it doesn't solve the problem for readdir. The
> > GetFileAttributes call is obviously supposed to find out if the drive is
> > accessible. If not, it's omitted from the cygdrive dir.
On Feb 14 16:17, Corinna Vinschen wrote:
> So, even if we fix fstat, it doesn't solve the problem for readdir. The
> GetFileAttributes call is obviously supposed to find out if the drive is
> accessible. If not, it's omitted from the cygdrive dir. Unfortunately...
>
> Does anybody know a system
On Feb 14 10:47, Ryan Johnson wrote:
> On 14/02/2012 10:17 AM, Corinna Vinschen wrote:
> >Does anybody know a system call which allows to fetch the network drive
> >state (connected/not connected) without a billion microsecond timeout?
> [...]
> What if we parsed the mount table instead of calling
On 14/02/2012 10:17 AM, Corinna Vinschen wrote:
On Feb 14 09:44, Ryan Johnson wrote:
On 14/02/2012 8:52 AM, Corinna Vinschen wrote:
On Feb 14 08:37, Ryan Johnson wrote:
(\??\C:\cygwin\cygdrive,0x28BB68)
^^^
This looks suspicious. I assume you're suffering from SMB n
On Feb 14 09:44, Ryan Johnson wrote:
> On 14/02/2012 8:52 AM, Corinna Vinschen wrote:
> >On Feb 14 08:37, Ryan Johnson wrote:
> >(\??\C:\cygwin\cygdrive,0x28BB68)
> ^^^
> This looks suspicious. I assume you're suffering from SMB network
> scanning.
> >>
On 14/02/2012 8:52 AM, Corinna Vinschen wrote:
On Feb 14 08:37, Ryan Johnson wrote:
Bump?
Stagger!
On 13/02/2012 8:31 AM, Ryan Johnson wrote:
On 11/02/2012 5:11 AM, Corinna Vinschen wrote:
On Feb 10 20:18, Ryan Johnson wrote:
Hi all,
For some reason file operations have become very slow i
On Feb 14 08:37, Ryan Johnson wrote:
> Bump?
Stagger!
> On 13/02/2012 8:31 AM, Ryan Johnson wrote:
> >On 11/02/2012 5:11 AM, Corinna Vinschen wrote:
> >>On Feb 10 20:18, Ryan Johnson wrote:
> >>>Hi all,
> >>>
> >>>For some reason file operations have become very slow inside emacs
> >>>starting ye
Bump?
On 13/02/2012 8:31 AM, Ryan Johnson wrote:
On 11/02/2012 5:11 AM, Corinna Vinschen wrote:
On Feb 10 20:18, Ryan Johnson wrote:
Hi all,
For some reason file operations have become very slow inside emacs
starting yesterday. It's especially painful when saving a file
that's managed by merc
On Feb 13 08:31, Ryan Johnson wrote:
> On 11/02/2012 5:11 AM, Corinna Vinschen wrote:
> >>(\??\C:\cygwin\cygdrive,0x28BB68)
> > ^^^
> > This looks suspicious. I assume you're suffering from SMB network
> > scanning.
> Turns out you were right after all. I have Z: mapped t
On 11/02/2012 5:11 AM, Corinna Vinschen wrote:
On Feb 10 20:18, Ryan Johnson wrote:
Hi all,
For some reason file operations have become very slow inside emacs
starting yesterday. It's especially painful when saving a file
that's managed by mercurial (more than 20 seconds!), but I've seen
it on
On Sat, Feb 11, 2012 at 02:50:31PM -0500, Ryan Johnson wrote:
>On 11/02/2012 12:24 PM, Christopher Faylor wrote:
>> On Sat, Feb 11, 2012 at 09:21:11AM -0500, Ryan Johnson wrote:
>>> On 11/02/2012 5:11 AM, Corinna Vinschen wrote:
On Feb 10 20:18, Ryan Johnson wrote:
> Hi all,
>
> Fo
On 11/02/2012 12:24 PM, Christopher Faylor wrote:
On Sat, Feb 11, 2012 at 09:21:11AM -0500, Ryan Johnson wrote:
On 11/02/2012 5:11 AM, Corinna Vinschen wrote:
On Feb 10 20:18, Ryan Johnson wrote:
Hi all,
For some reason file operations have become very slow inside emacs
starting yesterday. It
On Sat, Feb 11, 2012 at 09:21:11AM -0500, Ryan Johnson wrote:
>On 11/02/2012 5:11 AM, Corinna Vinschen wrote:
>> On Feb 10 20:18, Ryan Johnson wrote:
>>> Hi all,
>>>
>>> For some reason file operations have become very slow inside emacs
>>> starting yesterday. It's especially painful when saving a
On 11/02/2012 5:11 AM, Corinna Vinschen wrote:
On Feb 10 20:18, Ryan Johnson wrote:
Hi all,
For some reason file operations have become very slow inside emacs
starting yesterday. It's especially painful when saving a file
that's managed by mercurial (more than 20 seconds!), but I've seen
it on
On Feb 10 20:18, Ryan Johnson wrote:
> Hi all,
>
> For some reason file operations have become very slow inside emacs
> starting yesterday. It's especially painful when saving a file
> that's managed by mercurial (more than 20 seconds!), but I've seen
> it on the command line as well (x-server tak
Hi all,
For some reason file operations have become very slow inside emacs
starting yesterday. It's especially painful when saving a file that's
managed by mercurial (more than 20 seconds!), but I've seen it on the
command line as well (x-server takes a similar amount of time to start,
for ex
25 matches
Mail list logo
