Displaying 20 results from an estimated 10000 matches similar to: "Semaphore timeout"
2004 Jan 28
1
new error when upgrading :P "The semaphore timeout period has exp
We have newly installed ADSL/speedTouch 510 modem. After the installation,
we are getting problems with out Win2K machines. On out NT workstation
everything is OK, but on the Win2K we are getting following error,
"The semaphore timeout period has expired" whne trying to connect to the
domain (GARAGET),
My Network Places
Entire network
MS Windows Network
Garaget (our
1999 Oct 13
3
Root did not create the semaphore
Hello all,
I have a very annoying situation (at least at my end). I set up Samba
2.0.5 on a Digital UNIX 4.0F system sitting on a Compaq DS20 server with
great success.... until recently. I set up three directory file shares
with no problems, when I tried to set up a forth, quite a while after
setting up the inital three, I tried to access it from a NT box, I got
the message server not found,
2004 Feb 09
3
pdbedit and password expiry
Hi guys/girls,
How are you ?
I've been struggling to get my users' passwords to expire.
My configuration is samba-3.0 running with the standard smbpasswd
back-end.
Everything that I can find on the web says I should set the following to
expire my users passwords after 28 days.:
pdbedit -v -P 'minimum password age' -C 300
pdbedit -v -P 'maximum password age' -C 2419200
2006 Mar 17
3
SETFEATURES SET TRANSFER MODE semaphore timeout on FreeBSD 6.0 RELEASE
Hi
I have a newly installed FreeBSD 6.0 release machine on which I am
getting the following error on the console:
"ad4: req=0xc23bc258 SETFEATURES SET TRANSFER MODE semaphore timeout !!
DANGER Will Robinson !!"
This is generally associated with heightened disk activity, but it
happens inevitably after a while (minutes or hours) if the machine is
running.
The atacontrol list shows:
2005 Aug 16
0
FW: Error:The semaphore timeout period has expired
UPDATE:
We found out that there was still an entry in /etc/rc.local to start up
the old SAMBA after upgrading and setting up to run from inetd.conf.
Once the /etc/rc.local entry was removed, we no longer receive the
"semaphore timeout period has expired" messages and we are able to
connect to the shares.
Ben Burruel
Sr. Systems Manager
Metrics & Mainframe Capacity Planning
San
2013 Aug 03
1
[PATCH][git-pull] Fix mbox/semaphore checks, UNDI ID debug
The following changes since commit 6438fbcb6cb7e0cd40e4bb3681ada047fe77ffdd:
Gene Cumm (1):
Allow for UNDIIF_ID_DEBUG in 1 mk line
are available in the git repository at:
git://github.com/geneC/syslinux.git elflink-undi-thread-for-mfleming
Gene Cumm (3):
core/lwip/undi: Improve UNDIIF_ID_DEBUG messages
core: mbox/semaphore NULL checks
core: make
2001 Feb 26
1
Semaphores
I am running Samba 2.0 and occasionally get a "semaphore timeout period has
expired" message when accessing Samba shares on a Digital UNIX 4.0e server.
Does anyone know what kernel semaphore settings should be. Or could a
upgrade to 2.0.7 help. I new to Samba and am very green with this product.
Thanks
David
2002 Nov 16
1
upgraded to kernel 2.4.19 from 2.4.7, samba not found from windows, network ok
Hi,
I have updated my old 2.4.7 kernel to 2.4.19 using the full download
from kernel.org and installed samba-2.2.6
Using my old kernel i can access every share and everything works fine.
Using my new kernel also everything works but samba,.
i can telnet the system, ftp also works ok, but windows 2k tells me
server not found if i try to acces the shares.
i think, i forgot something to compile to
2003 Nov 11
1
winbind cannot run correctly
I modified /etc/nsswitch.conf, added winbind after passwd & group.
Also modified /etc/samba/smb.conf same as samba HOWTO collection's example.
The command "net rpc join -S DOMAIN -U Administrator" runned successfully,
and I could see my Linuxbox listed in ADS user&computer management console.
But when I started winbindd, some error messages appeared in
/var/log/message:
2004 Jun 25
1
The semaphore timeout period has expired
Hello Hamish.
I found your message just googling for Suse and sk98lin.
Did you solve your problem?
I had the same case and only way to restore was to change NIS driver speed
settings from AUTO to 10Mb. And it was not related to OS as the same problem
is in WXP ( I have dual boot, ASUS P4P800, integrated GB NIS ).
Oleg.
2004 May 19
0
The semaphore timeout period has expired
Hello everyone
I have samba 3.0.3pre2-SuSE running on SuSE 9.0 i386, this is from SuSE
rpms not source. The box is joined to a 2k3 domain, wbinfo works fine,
acls work and users are authenticated properly.
I had a problem yesterday and cannot seem to find a solution:
I have been copying data across from the old SBS server, this seems to
work fine for about 5 minutes, then completely crashes
2005 Feb 09
0
Error:The semaphore timeout period has expired
hi,
I hv recently installed and configured samba-3.0.10-1 with Ldap and smb
tools.
Everything looks good, i mean Samba, LDAP and smbldaptools everything.
But now when i am trying to access the shares as well as trying to join w2k
prof desktop to the domain its giving the error "The semaphore timeout
period has expired"
Can any one let me know what could be the problem?
Thanks &
2006 Mar 18
0
error:semaphore timeout period has expired
Hi all
I have a samba pdc (3.0.21c) with openldap (2.3.19) on a Redhat Enterprise
Linux 4 (2.6.9-5EL-SMP) kernel
i have Domain Member servers (samba server), i redirect my users to share
declared to in my domain member servers.
using logon script which gets executed when users logon . my clients use
windows 2k professional and windows xp.
my logon script is
@ echo off
net time \\mypdc /set /yes
2003 Dec 11
0
Semaphore Timeout Period has Expired
Hi. We are running Solaris 2.6, Samba 2.0.0.
NT workstations can connect to all samba shares, but W2K workstations can't. Some users get "Semaphore Timeout Period has expired", some get "Network name not found". The NT and W2K users login to the same NT domain. There is a WINS entry matching the Unix server hostname. Any ideas? Thank you. -Anoosh
Here is smb.conf
2005 Feb 24
0
The semaphore timeout period has expired
[.. most data for the archives ..]
I've got several windows 2000 machines and a samba 2.2.12 on solaris 7.
for years only one of the windows machines has ever needed to connect to
the samba server. just a couple of days ago, it was necessary for a
second machine to connect to the samba server. Whenever the second
machine tried to load the network share, windows came back with its "The
2019 May 25
1
[nbdkit PATCH] nbd: Rewrite thread passing to use semaphore rather than pipe
I ran some local testing on my Fedora 29 system via:
$ ./nbdkit memory 1m
$ for i in `seq 10`; do
./nbdkit -U - --filter=stats nbd \
statsappend=true statsfile=$file hostname=localhost port=10809 \
--run '~/libnbd/examples/threaded-reads-and-writes $unixsocket'
done
Pre-patch, the runs averaged 1.266s, 1.30E+08 bits/s
Post-patch, the runs averaged 1.154s, 1.42E+08
2004 Jun 30
1
Semaphore Time Expired
I am running Debian 'woody' with Samba 3.0.2 and am having a sparatic
problem on my network.
Some users will suddenly lose their connections to the samba shares and
when trying to log in
to the system again will get an error that windows cannot locate their
roaming profile - "Semaphore time period has expired".
It seems that if they wait for about 15 minutes they can then
1999 Mar 25
1
semaphore-error
When I try to connect to smbd on a SUN Solaris 2.6 with a
running oracle database, I get the folloing error:
[1999/03/25 10:25:30, 1] smbd/files.c:file_init(219)
file_init: Information only: requested 10000 open files, 1014 are available.
[1999/03/25 10:26:07, 0] locking/shmem_sysv.c:sysv_shm_open(563)
Can't create or use semaphore [1]. Error was No space left on device
[1999/03/25
2002 Feb 26
1
semaphore timeoit period expired (root is full)
I have had samba running on my freebsd box for about 2 years now, and my / partition is 50MB (it is just a fileserver with ssh and
nothing more). However, recently (about a month or two ago) it disconnects itself from my LAN with warnings like: semaphore timeout
has expired. I go to the console on the box and it says that the disk is full (its not, but the root directory is at 101%) I cannot
2004 Oct 11
1
Fw: smb_proc_readdir_long error
Hi guys,
Does anyone have any ideas on my questions below ?
Kindest regards
David Wilson
D c D a t a
Tel +27 33 342 7003
Fax +27 33 345 4155
Cell +27 82 4147413
MSN: dave@dcdata.co.za
http://www.dcdata.co.za
support@dcdata.co.za
sales@dcdata.co.za
KZN's first and only pure Linux solution provider
____________________________________________________
LinuxBox S.A.: Africa's shell