Displaying 10 results from an estimated 10 matches for "disonnected".
Did you mean:
disconnected
2005 Feb 01
1
VFS calls after disonnect
Hello,
I am having the same problem as below. I am using 3.02a on FreeBSD.
Was this solved or does anyone know how to solve it?
Many Thanks,
Chetana
On Wed, May 26, 2004 at 09:54:18AM +0200, yves.lejeune at kodak.com wrote:
> Hello,
>
> > >
> > > Is is normal to have the initial double SMB_VFS_CONNECT and
> > > SMB_VFS_DISCONNECT ?
> > > Should I
2013 Aug 20
0
[Announce] Samba 4.0.9 Available for Download
...l/samba/var/locks/sysvol"
(bug #9820).
o Fix segmentation fault while reading incomplete session info (bug #10003).
o smbd: Fix a 100% loop at shutdown time (bug #10013).
Changes since 4.0.8:
--------------------
o Michael Adam <obnox at samba.org>
* BUG 9930: smbd: Cleanup disonnected durable handles.
o Jeremy Allison <jra at samba.org>
* BUG 9992: Fix Windows error 0x800700FE when copying files with xattr names
containing ":".
* BUG 10064: Linux kernel oplock breaks can miss signals.
o Andrew Bartlett <abartlet at samba.org>
* BUG...
2013 Aug 20
0
[Announce] Samba 4.0.9 Available for Download
...l/samba/var/locks/sysvol"
(bug #9820).
o Fix segmentation fault while reading incomplete session info (bug #10003).
o smbd: Fix a 100% loop at shutdown time (bug #10013).
Changes since 4.0.8:
--------------------
o Michael Adam <obnox at samba.org>
* BUG 9930: smbd: Cleanup disonnected durable handles.
o Jeremy Allison <jra at samba.org>
* BUG 9992: Fix Windows error 0x800700FE when copying files with xattr names
containing ":".
* BUG 10064: Linux kernel oplock breaks can miss signals.
o Andrew Bartlett <abartlet at samba.org>
* BUG...
2011 Aug 22
0
How to Connect a new CD via virt-manager
Hi,
I have virt-manager 0.9 connecting to a libvirtd 0.9.3 on Debian
unstable. Hypervisor being used is KVM.
In a VM, I can select the "IDE CDROM 1" and click on "disonnect" which
makes the virtual disk disappear from the virtual drive and the former
disconnect button now reads "connect". Hence, when I click there,
nothing happens.
Currently, the only way I am
2024 Jan 19
1
NUT and Eaton UPS produce a lot of error messages
On 19.01.24 09:00, Jim Klimov via Nut-upsuser wrote:
>Well, from your logs it seems that at 05:17:03 your nut-server (upsd)
>restarted, so an upsmon reconnection attempt at 05:17:09 had an issue with
>that (config not all applied? strange a bit) but since 05:17:14 it is okay.
>
>Maybe a few too many banners shown from upsmon, while its same uptime seems
>to continue. Maybe
2024 Jan 19
1
NUT and Eaton UPS produce a lot of error messages
With recent NUT releases, driver disconnections should be contained in its
own `nut-driver at eaton` instance (the `@upsname` part is derived from the
`ups.conf` section name). One of the drivers failing and restarting is not
a proper cause for the data server to recycle.
Also, nowadays some (maybe not all) USB-capable drivers should try to
reconnect without restarting. Note however, that in some
2024 Jan 19
2
NUT and Eaton UPS produce a lot of error messages
Hello and thanks for all the replies.
This morning at 9:50 the server stopped working unexpectedly - I was
still sleeping until 10:00, so no user intervention took place.
Jan 19 05:50:17 mars nut-server[1303]: mainloop: Interrupted system call
Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting
Jan 19 05:50:17 mars nut-server[1303]: Network UPS Tools upsd 2.8.0
Jan 19 05:50:17 mars
2024 Jan 19
1
NUT and Eaton UPS produce a lot of error messages
On 19.01.24 16:20, Stefan Schumacher via Nut-upsuser wrote:
>This morning at 9:50 the server stopped working unexpectedly - I was
>still sleeping until 10:00, so no user intervention took place.
>
>Jan 19 05:50:17 mars nut-server[1303]: mainloop: Interrupted system call
>Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting
>Jan 19 05:50:17 mars nut-server[1303]: Network UPS
2024 Jan 19
2
NUT and Eaton UPS produce a lot of error messages
Jan 19 05:50:13 mars nut-monitor[849]: Signal 15: exiting
Jan 19 05:50:13 mars nut-monitor[849]: Network UPS Tools upsmon 2.8.0
Jan 19 05:50:13 mars systemd[1]: Stopping nut-monitor.service -
Network UPS Tools - power device monitor and shutdown controller...
Jan 19 05:50:13 mars systemd[1]: nut-monitor.service: Deactivated successfully.
Jan 19 05:50:13 mars systemd[1]: Stopped nut-monitor.service
2024 Jan 19
1
NUT and Eaton UPS produce a lot of error messages
Well, from your logs it seems that at 05:17:03 your nut-server (upsd)
restarted, so an upsmon reconnection attempt at 05:17:09 had an issue with
that (config not all applied? strange a bit) but since 05:17:14 it is okay.
Maybe a few too many banners shown from upsmon, while its same uptime seems
to continue. Maybe someone should check on that, seems like a good and easy
newcomer issue to learn