search for: deadtime

My expectations are probably wrong, but I had to manually kill a process to unlock a file when I think it should have killed itself. I have deadtime set to 15 and keepalive at default (300). I opened a file on my server in Excel, then shut down the machine. Hours later someone tells me the file is locked. Shouldn't keepalive have detected that the machine was off in 5 minutes? Shouldn't deadtime have disconnected the process and unlo...

...34PM -0700, Jeremy Allison via samba wrote: > On Tue, Nov 01, 2016 at 05:16:47PM -0500, Ed Siefker via samba wrote: > > My expectations are probably wrong, but I had to manually kill a process > > to unlock a file when I think it should have killed itself. > > > > I have deadtime set to 15 and keepalive at default (300). I opened a file on > > my server in Excel, then shut down the machine. Hours later someone > > tells me the file is locked. > > > > Shouldn't keepalive have detected that the machine was off in 5 minutes? > > Shouldn'...

Hello samba gurus ! I'm using samba 3.0.21c on AIX 5.3 box . I've specified deadtime=15 in my smb.conf file and I'm expecting that inactive sessions ( has no open files ) will be closed after 15 minutes . I'm connecting to samba from my PC ( win2000 ) , minimizing the window and waiting 15 minutes ... but nothing happens - smbd opened by my connection is still running ,...

...rote: > Thanks. I should also mention the freenas server is setup with an lacp lagg. > > I will also mention that even when not setting pollfreq (leave as default) the issue still occurs. > It looks like the default for pollfreq is actually 30 on snmp-ups, which means you would want DEADTIME to be at least 2x that in order for a single stale data event to not trigger the COMMBAD message, and the default is only 15. As you can imagine, choosing default values that work across all the UPS models is somewhat tricky. > FreeNAS has an additional parameters area to add to the upsmon.conf....

I missed that snmp-ups set pollfreq to 30 by default. I'd hope that it would set deadtime to an appropriate value as well than, no? Is there a way to query what the settings are or what the defaults are? I'm going to set POLLFREQ=30 and DEADTIME = 90 and see if that has any effect. I'll check for the logs. And if that doesn't get my anywhere I'll look at trying to simul...

When a user is not using a samba share, after a while they become "inactive". When a user wants to access the share again, it takes an irritating long time before they get access again. The (windows) application that does the accessing is not responding during that time. There are no drive letters assigned to the shares in a logon script. When I do assign a drive letter to the share (in

Hi Jeremy, No, I don't mean "deadtime". I mean auto disconnect. Specifically, the command "net config server /autodisconnect:-1" was run on each client machine. If deadtime is a server configuration item perhaps you could point me in the direction of some documentation where that is covered. The documentation for smb...

Hi, I currently have deadtime = 15 in my smb.conf. This featured worked good to disconnect clients that have been idle for > 15 minutes in the past. With the 3.0.13 version, it seems to do nothing. As in, it just keeps the user connected indefinitely. Here is what I see when no one is currently at the office and ever...

On Mar 31, 2015, at 9:07 AM, Jason Gould <jgould at cddiagnostics.com> wrote: > I missed that snmp-ups set pollfreq to 30 by default. I?d hope that it would set deadtime to an appropriate value as well than, no? Is there a way to query what the settings are or what the defaults are? There is a TODO comment in snmp-ups that mentions doing something similar to usbhid-ups: just poll the important status OIDs every two seconds (pollinterval), and fill in the rest ever...

We are currently trying to limit the number of processes/connections on our samba server. Our current version is Samba version 3.0.23c-SerNet-RedHat. We tried to use the deadtime parameter. If we set deadtime to 3 (3 minutes), the connection that is not used by the client for more than 3 minutes is still seen in the smbstatus and net status sessions. The corresponding smbd process is still available on the samba server. The client has to disconnect itself to : - stop the...

Hallo, I have one ups with snmp and any ups without snmp. Shutdown works while network online. But some batteries are empty, so that the communication break early. Howto force shutdown if nut-snmp Communications lost? My 1. suggestion was option DEADTIME, but seem to be information only. (s. below) Any suggestions? The last way would be a ugly cronjob (like: ping || shutdown). regards Heiko ------------------------------------------------------ - script simulate network failure defaultrouter=`netstat -rn | grep "^0.0" | awk '{pri...

Hello, I hope it is ok to come here for a little help. I use _Samba Version 4.5.12-Debian_ on a _Linux serveur 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux_. I use it to load games from my Playstation 2 over my home network. Here is the relevant part of my smb.conf file. ~ % cat /etc/samba/smb.conf [global]         netbios name = Partage         workgroup

...ther OS needs it, nor can test it to any truly useful extent. Thanks for point out the man page, which I've always taken as be referring to Samba 3, not Samba 4. I can only wonder why there's a site dedicated to Samba 4 documentation and this information isn't there. If the default deadtime = 0 and we haven't changed it then that's obviously not the culprit and I need to keep looking for a cause. regards, John On 15/12/15 16:35, Jeremy Allison wrote: > On Tue, Dec 15, 2015 at 04:07:55PM +1100, John Gardeniers wrote: >> Hi Jeremy, >> >> No, I don't...

...; is responsible for monitoring the "upsd" process on the master system that provides information about the state of the UPS. Each slave system can set parameters for the upsmon process (using the NUT configuration file "upsmon.conf"). One of these parameters is called "DEADTIME". The man page for upsmon (upsmon.8) states: DEAD UPSES In the event that upsmon can?t reach upsd(8), it declares that UPS dead after some interval controlled by DEADTIME in the upsmon.conf(5). If this happens while that UPS was last known to be on battery, it is assumed to have gone crit...

Thanks. As mentioned, deadtime can't be set for snmp-ups. You see this in the logs. Mar 31 09:08:30 freenas notifier: Fatal error: 'DEADTIME' is not a valid variable name for this driver. Mar 31 09:08:30 freenas notifier: Look in the man page or call this driver with -h for a list of valid variable names and flags....

On Sep 3, 2014, at 9:38 AM, Heiko L. <HL at fh-lausitz.de> wrote: > Howto force shutdown if nut-snmp Communications lost? > > My 1. suggestion was option DEADTIME, but seem to be information only. (s. below) DEADTIME expiration is a critical condition if the UPS is on battery when comms are lost, otherwise you are correct, it is only informative. What about a NOTIFYCMD script that checks for COMMBAD or NOCOMM? (passed in $NOTIFYTYPE) You will also need to...

...othing on a standalone server > > ; name resolve order = lmhosts host wins bcast > ; if winbind is running, use wins host bcast > ; name resolve order = wins host bcast > name resolve order = host bcast You may have problems if you don't use 'wins' > ; note: deadtime is in minutes 1440=24hrs 2880=48hrs (2 days) > 20160=14days ; deadtime = 60 > ; deadtime = 1440 > deadtime = 20160 I will be a bit blunter this time, waiting for 2 weeks before an idle connection is disconnected is just plain stupid. The shares don't seem to have changed, so se...

I edited my smb.conf acording to all your remarks, thanks. Just so I understand, the manual says that the default is "deadtime=0" and that > A deadtime of zero indicates that no auto-disconnection should be > performed. So how come I am getting auto-disconnected? And how come I need to set deadtime=15? I am currently leaving my PS2 idling, will keep you informed. Your help is very appreciated. Best, Antoin...

This is normal. Samba spawns 1 smbd plus 1 for each connected client. If it concerns you that these hang around you can set the deadtime parameter in smb.conf to limit the time they remain live. The default is deadtime=0 which means no automatic termination of unused connections. Set this to the number of minutes to wait before disconnecting an idle connection. I use deadtime=10 on a server with ~100 print queues [no file shares.....

I need to disconnect some samba connections to my linux redhat server. I searched online and found these two tips but neither work: 1. Set the deadtime parameter to specific time in the smb.conf file my smb.conf file does not have the parameter deadtime listed 2. Use kill command to kill the smbd PID. Kill -15 <PID> I tried that and after killing my own connection I could still open and save files to the samba share that I had connected to....