Displaying 20 results from an estimated 1000 matches similar to: "fork problem and web site problems"
2000 May 18
1
root preexec & 2.0.7
I a have a problem resulting from a neat tool I developed through the use of the
"root preexec" option:
This is done in the [homes] section of smb.conf.
I launch a shell script with the user name (%u) and machine name (%m). The shell
calls a C program to check the users quota and returns a code as the percentage
of quota used.
Meanwhile, all output of the C program has been captured
2000 Apr 28
3
Win2k & 2.0.7
When I try to join the Win2k machine to a domain, I get the following message:
The following error occurred attempting to join the domain "WIN2K":
The procedure number is out of range.
This is a Win2k PC attempting to join to AIX 4.3.2 running samba 2.0.7. Any
ideas would be greatly appreciated.
Thanks,
Bill
--
/------------------------------------------------------\
2000 May 02
2
ole locking compatibility
Would there be any conditions under which this setting (default to yes) could
cause an AIX 4.3.2 machine (samba 2.0.6) to suddenly have all processes (smbd or
otherwise) become blocked?
I've sent 5 dumps to IBM and they're stumped and this is the only thing I can
possibly find from the samba stuff that could possibly cause it.
Here is the exerpt from smb.conf:
ole locking
2000 Mar 30
4
Compile error - 3rd time...
Well, since alpha 0.0 this has been there....
Any ideas Luke?
Using LIBS = -ldl
Compiling rpc_client/cli_login.c with libtool
"include/sam.h", line 31.41: 1506-243 (S) Value of enumeration constant must be
in range of signed integer.
make: The error code from the last command is 1.
Stop.
IBM AIX 4.3.2. IBM C compiler 3.6.6.
Any idea when this will be fixed?
Bill
--
1999 Nov 11
0
Printing Problems w/Samba on AIX (2nd Try)
Hello all,
I have been running Samba on various versions of UNIX for quite a
while now without ever encountering any major problems. However, I have
now run into a problem that has me stumped.
I am running Samba 2.0.5a on an RS/6000 running AIX. Up until a
month or so ago we were running on AIX version 4.2.1. At that time we
upgraded to 4.3.2 and Samba continued to function properly.
2006 Jan 26
0
Fw: SAMBA on AIX 5.1
forwarding this for AIX people...forgot to CC list.... D'oh!
----- Original Message -----
From: Antonio Sosa
To: William Jojo
Sent: Thursday, January 26, 2006 12:05 PM
Subject: RE: SAMBA on AIX 5.1
Thanks William - I'll try it out.
Antonio Sosa
C.E.O.
Ansotech Inc.
"We Design Technology Around You"
Tel: 877-389-8728
Cell: 773-406-3663
1998 Jul 14
0
Slackware Shadow Insecurity (fwd)
Here's someone that felt the need to put something better together.
---------- Forwarded message ----------
Date: Mon, 13 Jul 1998 04:22:15 -0400
From: Richard Thomas <rthomas@sy.net>
To: BUGTRAQ@NETSPACE.ORG
Subject: Slackware Shadow Insecurity
Discovered by Ted Hickman:
Recently I noticed something rather "insecure" about the slackware 3.4
/bin/login (and probably other
2005 Oct 24
1
writing files via samba issues...
I've samba running an embedded linux system (2.6.x kernel with uClibc). I'=
m trying to transfer some medium to large files (65-225 MB). I'm using simp=
le windows explorer drag/drop to write the files to the embedded system. T=
he file transfer dialog will show some progress then lock up for a few minu=
tes. After this it reports with "The specified network name is no longer
2004 Jan 11
0
Win2k clients problem after updating system
Hello all samba users and programmers,
Since I changed my system and reinstalled samba funny things happen in my net. I used to work with a Gentoo system and now I've got installed a Knoppix 3.2 Debian, but by now I don't think it's interesting for the problem I've got.
What I did was:
- install samba 3.0.0-final
- copy the old smb.conf file to the path in the new system
1999 Sep 23
2
Race Condition cont'd
Thank you Paul for your response. Perhaps I can give a bit more info:
RS/6000 H50 w/AIX 4.3.2 running Samba 2.0.5a
PIII-450 NT4sp4 w/128MB
I indicated yesterday that a race condition appeared to be happening. I later
remembered that I turned on level2 oplocks on two read only shares as the last
tunings we did before this began to happen. I got the info from the Speed.txt
document in hopes of
1999 Dec 28
1
Level 2 Oplocks.
I know in 2.0.5a, level2 oplocks were broken. Can I safely use them in 2.0.6? I
recall getting a performance increase when using them.
Bill
--
/------------------------------------------------------\
| |
| William E. Jojo, Jr. |
| |
| Senior
1999 Jun 14
0
Possible Password Sync Solution!
I've been reading many of password sync problems from both this list and the
NTDOM list and have come up with a solution that seems secure enough although I
had to modify some samba code to make it work.
This potential solution is for sync from Unix to smbpasswd and has nothing to do
with "unix passswd sync".
What I've done is literally rewrite the unix "passwd"
1999 Aug 30
0
URGENT: UID Sync problem and smbpasswd problem
We have 4200 users on 2.0.5a as a PDC. Everything works great, except. We
somehow overlooked 300 users from our summer sessions and these people's UID are
in conflict between /etc/passwd and /usr/samba/private/smbpasswd.
Also why is there no option to REMOVE a user with smbpasswd? I could solve this
live if this option existed. I cannot simply edit the file because I could cause
machine
1999 Sep 16
0
Performance Question...
We have 600 PCs - PIII 450 - with NT4SP4, 10BaseT Full Duplex SMC9432 NICs,
64MB.
Server is RS/6000-H50 1GB Memory and 4-way SMP. It serves 64GB of student
storage and 8GB shared programs (Read Only).
Samba 2.0.5a is configured with 4MB shared mem, TCP_NODELAY IPTOS_LOWDELAY
SO_SNDBUF=131072 SO_RCVBUF=131072.
We've moved 200 of the 600 PCs from Novell/Samba combo to all Samba shares.
Does
1999 Sep 23
1
Shared Memory Problems
I just thought I'd throw this out there because it doesn't seem normal to me.
We have 2.0.5a on AIX 4.3.2.
We initially tried to increase the shared mem size to 4MB. This would not happen
until we rebooted AIX. Then smbstatus reported a 4MB shared mem size. Now we are
trying to decrease it because we will only need about 2MB and it won't reduce. I
suspect it will when we reboot
2000 Feb 10
0
Compile problem(s)...
Just thought I'd pass this along....compiling TNG code from CVS on AIX 4.3.2
using IBM C/C++ compiler 3.6.6:
Compiling rpc_client/cli_login.c with libtool
"include/sam.h", line 31.41: 1506-243 (S) Value of enumeration constant must be
in range of signed integer.
make: The error code from the last command is 1.
The alpha 0.0 code does this:
Compiling tdb/tdb.c with libtool
2000 Feb 15
0
WIN2K authenticates against 2.0.6!!!
Since I didn't receive any replies to my questions or observations, we were
forced to try new things...
We upgraded NT4SP5 (which does everything we want it to do) to Windows 2000 Pro
and magically it now authenticates against Samba 2.0.6 on AIX 4.3.2.
We have some problems however...the logon script does not run and the
"LogonServer" environment variable is no longer set to the
2000 Feb 22
1
Second Notice...
This is the second posting of a TNG compile problem on AIX 4.3.2 - this time
with alpha0.5 this has been there for some time...can anybody explain why - it's
just an enumeration constant problem.
Compiling rpc_client/cli_login.c with libtool
"include/sam.h", line 31.41: 1506-243 (S) Value of enumeration constant must be
in range of signed
1999 Jun 29
0
Help. Unable to print from NT
Hi,
I'm running samba-2.0.4b rpm package on Redhat 6.0. I
was able to setup samba just fine along with the
printer. I can print from the linux box just fine both
text and postscript. My NT 4.0 server(SP3) running PDC
saw the printer fine. I was able to install the
printer as a network printer with no problem. But I
just cannot print to it. When I turned on the debug
level to 10. I got the
2000 Jun 28
0
Urgent Help pls - NT4.0 Term Server and SAMBA - RDR timeouts
Hello,
I'm new to this list.
The NT folk here, are concerned about some timeout errors and stuff that appear
in their event viewer. They are building a case to convince management that
unless these "samba" errors are fixed, we should move to NT file shares. I think
this is a bad idea. Can anyone help me out here.
We are running samba 2.0.6 (1st msg) and 2.0.5a (2nd err msg)