Displaying 5 results from an estimated 5 matches for "302rc1".
2004 Jan 29
1
302rc1 and AIX 5.2
I'm getting some wierd things going on. Mostly segfaults with testparm,
but others as well...
AIX 5.2, IBM C compiler version 6.0, libiconv 1.9.1 compiled in shared
mode.
I've resolved the LIBPATH thing so I can compile correctly now.
When I start nmbd, or smbd with the -D option they just chew up a ton of
cpu and log level 10 only shows the code pages being mapped and that's it.
I
2004 Jan 19
4
network browserlist error(S)..
G'day.. just haveing the straingest problem..
I'd upgraded to the 302rc1 version. i configed it to be an pdc controller,
with wins to manage our local domain..
only when browsing the domain list.
it gives error(s) once in a while..
"An extended error has occured" &
"the system cannot find massage text for message number 0x in the message
file for \...
2004 Jan 29
2
smbd pids
just noticed the following problem..
after running samba 302rc1(as pdc) for a few day's.
old SMBD pid's are left in the procces tree..
eating memory and cpu time, causing linux to overload and not function
annymore.
after stopping samba, the smbd pid's will stay.
stopping samba the 2nd time will do the trick, they finaly disapear...
so you have t...
2004 Jan 30
1
Able to Mount home, but getting failure errors in logs
Hi,
I have a few users that are creating errors like below. These users have mapped
a directory via Samba and also have it connected. They can access their home
directory or other directory via Samba fine, but it is strange that every hour
on the hour there is a failure put into the log (even though they are working).
My server is joined to the Domain and it is using
2004 Jan 27
2
MS Word and Samba File Permissions Problem
Hello everybody!
Obviously Samba as a PDC and Fileserver for w2k clients is not as easy as I
first thought.
Soon after setup and integration in a network a problem with the shares and MS
Word appeared.
Any time a file is opened with M$ Word directly from a share and edited it
can't be saved. The M$ user gets the msg that the file is write-protected and
on the samba side the file