search for: 0.000053

Hi folks, On Fri, Apr 24, 2015 at 08:01:54AM +0800, Jones Syue wrote: > Hello Ervin, > > > I'll notify to you about the result. (First, I need to upgrade > > that server.) > > Sure! That will be great help me to understand if this patch > works on thast compiling case too, > thank you. I"ve downloaded the Ubuntu's Samba 4.1.6 deb source, and patch it

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT

Hi Jones, many thanks again four your help and your time. Thanks for the patch too - I'll check it up. On my Ubuntu, there is a Samba 4.1.6. I'll install the samba source package, and will try to apply the patch, then - I hope - the package will be compiled as well. I'll notify to you about the result. (First, I need to upgrade that server.) Thanks again, Ervin On Thu, Apr

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

Hi, Great work Jim! I?m glad you could reproduce the problem and found a potential culprit. Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update)

Hi, Great work Jim! I?m glad you could reproduce the problem and found a potential culprit. Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update)

Hi, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

Hi, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

Dear Samba users, here is an Ubuntu 14.04, with Samba 4 (4.1.6), and LDAP (slapd 2.4.31). The config came from a previous system (Debian Squeezy), which had been crashed (HW error - on this new machine, I've put Ubuntu). So, as I wrote, the smb.conf and LDAP database was copied from the backup from the old system - but it works as well. Only one thing what's very annoying. The Samba is

So... determining that FD is to be reaped proved hard. Internet lore suggests fcntl() and poll() on the FD, but it just seems valid to them. The errno is also usually not raised (once I saw a "111: Connection refused" though). So the best dumb idea so far is to bail out if we spent the whole loop (128 attempts) and only got zero-sized read replies and no errors.

So... determining that FD is to be reaped proved hard. Internet lore suggests fcntl() and poll() on the FD, but it just seems valid to them. The errno is also usually not raised (once I saw a "111: Connection refused" though). So the best dumb idea so far is to bail out if we spent the whole loop (128 attempts) and only got zero-sized read replies and no errors.

Hi! I'm currently hunting a strange problem and looking for help! I have a samba3 fileserver (currently samba-3.0.20b, but problem can be reproduced with samba-3.0.7, but _not_ with samba2 like 2.2.8a), and I see performance problems when writing files with MS word 2002 SP3 from a NT4.0 (SP6a) workstation. Saving even the smallest file takes more than 10 seconds! Copying files with Windows

Package: xen-hypervisor-3.4-amd64 and linux-image-2.6.32-5-xen-amd64 Version: 3.4.3-1 and 2.6.32-15 Hello all, GRUB-PC does not automatically populate Xen related parameters in /boot/grub/grub.cfg so I added them manually (see below). All the packages involved on my Dell PowerEdge R710 running Debian GNU/Linux Squeeze AMD64 are from the Squeeze repository. There are four (4) 1TB SATA HDD

https://bugs.freedesktop.org/show_bug.cgi?id=109681 Bug ID: 109681 Summary: Nvidia GT710 => nouveau + wayland + swayWM => crash when use acceleration (open Firefox) Product: Mesa Version: 18.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical

Hi All, I am trying to get the pv_ops Xen dom0 kernel working with Xen 3.4 but with no success. I have been at this for 2 weeks now with different problems. Initially I could not get dom0 to boot when using LVM, so I reinstalled and didn''t use LVM. Now I am getting stack overran or currupted errors. Here is the boot log; From <IRQ 0> to the last line keeps on repeating until