Re: Problems with ACLs in 2.2.8
Jan Houstek wrote: server: linux 2.4.19 with xfs 1.2 and its ACL libacl 2.0.19 samba 2.2.8 compiled from source with --with-acl-support acting as PDC interesting parts of smb.conf create mask = 0600 directory mask = 0700 [testshare] path = /data/testshare readonly = No client: 1) Windows XP, servicepack 1.2a 2) smbmount from another linux box server:~# getfacl /data/testshare/testdir # file: testdir # owner: testuser # group: users user::rwx group::--- group:somegroup:r-x group:anothergroup:rwx mask::rwx other::--- default:user::rwx default:group::--- default:group:somegroup:r-x default:group:anothergroup:rwx default:mask::rwx default:other::--- server:~# umask 007 server:~# mkdir /data/testshare/testdir/test1 server:~# getfacl /data/testshare/testdir/test1 # file: test1 # owner: root # group: root user::rwx group::--- group:somegroup:r-x group:anothergroup:rwx mask::rwx other::--- default:user::rwx default:group::--- default:group:somegroup:r-x default:group:anothergroup:rwx default:mask::rwx default:other::--- On windows: logon to domain as testuser create test2 in testdir (right mouse button - New - Folder) server:~# getfacl /data/testshare/testdir/test2 # file: test2 # owner: testuser # group: users user::rwx group::rwx # !!! problem !!! group:somegroup:r-x group:anothergroup:rwx mask::rwx other::--- default:user::rwx default:group::--- default:group:somegroup:r-x default:group:anothergroup:rwx default:mask::rwx default:other::--- I could (almost) reproduce it on HP-UX, and (almost) fix it using inherit acls = Yes. :) Both almost refer to mask (or class, respectively) behaving a bit strange. But this might be platform specific. Maybe using inherit acls could already do the job in your setup? Cheers! Michael
Re: more then one backend in one module
On Tue, Mar 25, 2003 at 08:11:35AM +0100, Stefan (metze) Metzmacher wrote about 'more then one backend in one module': HI Jelmer, how do we handle *sam_nua modules and friends... 'ldapsam' and 'ldapsam_nua' are in pdb_ldap.c 'sam','samstrict' and 'samstrict_dc' are all in auth_sam.c if this modules are static all is fine, but as module??? smb_probe_module() will not find them... Right, there should be symlinks -- Jelmer Vernooij [EMAIL PROTECTED] - http://nl.linux.org/~jelmer/ 11:14:02 up 7 days, 17:28, 22 users, load average: 0.00, 0.02, 0.00
Re: Machine account password interoperablity for Samba 3.0secrets.tdb and keytabs
I really don't think that putting keytab code in to Samba is the right answer. Do you really want to be in charge of modifying keytabs? This could get quite complicate -- especially when you multiply the effort by the number of possible encryption types... I don't think it's that complicated. It is not difficult to enumerate the supported encryption types. Moreover, there's no requirement that SAMBA use the same keytab as other applications, or that keytab support completely replace the secret store. -- Luke -- Luke Howard | PADL Software Pty Ltd | www.padl.com
Re: Machine account password interoperablity for Samba 3.0secrets.tdb and keytabs
On Tue, 2003-03-25 at 22:36, Luke Howard wrote: I really don't think that putting keytab code in to Samba is the right answer. Do you really want to be in charge of modifying keytabs? This could get quite complicate -- especially when you multiply the effort by the number of possible encryption types... I don't think it's that complicated. It is not difficult to enumerate the supported encryption types. Moreover, there's no requirement that SAMBA use the same keytab as other applications, or that keytab support completely replace the secret store. I agree that if Samba is changing the password for a particular kerberos principal, then it should store the hashes in the keytab. The idea of *finally* getting kerberos useful on real sites is just too appealing :-) Naturally, the original plaintext password should stay basically where it is. Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net signature.asc Description: This is a digitally signed message part
samba cluster active-active configuration.
Hi all, Sorry for posting this one here, I guess it is a bit out of topic, But I tried about 4 or 5 other mailing lists - no luck yet. I'm trying to configure my samba on a RedHat AS 2.1, to run in an active-active configuration. The Red Hat Cluster Manager Installation and Administration Guide says on chapter 6.2 : Allows the setup of an active-active configuration to maximize equipment utilization. More details on active-active configurations appear below. But - no luck for me :-) , because no such details appear below... My questions are: 1. How do I make samba run in active-active configuration ? 2. What happens to nmbd - which node runs this one ? (I guess both of them can't) 3. Should the netbios name be the same for both nodes ? Is there an netbios name alias option so both nodes will be accessed by same netbios name ? 4. In case I use security = domain, and my node names are RHCLU0 and RHCLU1 , should I add both of them as a computer account in my domain ? Do I also need an alias for them ? Your help is appreciated Nir
Re: Machine account password interoperablity for Samba 3.0secrets.tdb and keytabs
I agree that if Samba is changing the password for a particular kerberos principal, then it should store the hashes in the keytab. The idea of *finally* getting kerberos useful on real sites is just too appealing :-) Naturally, the original plaintext password should stay basically where it is. In that case, perhaps it *is* better just to provide a get/set command line tool for the secret store rather than trying to hook the keytab into SAMBA per se. -- Luke -- Luke Howard | PADL Software Pty Ltd | www.padl.com
Re: Machine account password interoperablity for Samba 3.0secrets.tdb and keytabs
On Tue, 2003-03-25 at 22:55, Luke Howard wrote: I agree that if Samba is changing the password for a particular kerberos principal, then it should store the hashes in the keytab. The idea of *finally* getting kerberos useful on real sites is just too appealing :-) Naturally, the original plaintext password should stay basically where it is. In that case, perhaps it *is* better just to provide a get/set command line tool for the secret store rather than trying to hook the keytab into SAMBA per se. Well, I think we should provide both, but if Samba just changed the password for a principal, I see no harm in setting the password into the keytab, when selected by the admin. Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net signature.asc Description: This is a digitally signed message part
compiling with gcc 3.3
Hi!
Compiling samba CVS with gcc 3.3 gives quite some
annoying warnings in proto.h because exp and log are
builtins. Attached is a patch that replaces exp with expr
and log with clog (didn't know a better name for it)
in the affected c files.
Please apply.
Greetings, Stephan
Index: rpc_parse/parse_misc.c
===
RCS file: /cvsroot/samba/source/rpc_parse/parse_misc.c,v
retrieving revision 1.111
diff -u -3 -p -u -r1.111 parse_misc.c
--- rpc_parse/parse_misc.c 15 Mar 2003 07:45:51 - 1.111
+++ rpc_parse/parse_misc.c 25 Mar 2003 09:05:39 -
@@ -1289,22 +1289,22 @@ void init_dom_rid4(DOM_RID4 *rid4, uint1
Inits a DOM_CLNT_SRV structure.
/
-static void init_clnt_srv(DOM_CLNT_SRV *log, const char *logon_srv, const char *comp_name)
+static void init_clnt_srv(DOM_CLNT_SRV *clog, const char *logon_srv, const char *comp_name)
{
DEBUG(5,(init_clnt_srv: %d\n, __LINE__));
if (logon_srv != NULL) {
- log-undoc_buffer = 1;
- init_unistr2(log-uni_logon_srv, logon_srv, strlen(logon_srv)+1);
+ clog-undoc_buffer = 1;
+ init_unistr2(clog-uni_logon_srv, logon_srv, strlen(logon_srv)+1);
} else {
- log-undoc_buffer = 0;
+ clog-undoc_buffer = 0;
}
if (comp_name != NULL) {
- log-undoc_buffer2 = 1;
- init_unistr2(log-uni_comp_name, comp_name, strlen(comp_name)+1);
+ clog-undoc_buffer2 = 1;
+ init_unistr2(clog-uni_comp_name, comp_name, strlen(comp_name)+1);
} else {
- log-undoc_buffer2 = 0;
+ clog-undoc_buffer2 = 0;
}
}
@@ -1312,9 +1312,9 @@ static void init_clnt_srv(DOM_CLNT_SRV *
Inits or writes a DOM_CLNT_SRV structure.
/
-static BOOL smb_io_clnt_srv(const char *desc, DOM_CLNT_SRV *log, prs_struct *ps, int depth)
+static BOOL smb_io_clnt_srv(const char *desc, DOM_CLNT_SRV *clog, prs_struct *ps, int depth)
{
- if (log == NULL)
+ if (clog == NULL)
return False;
prs_debug(ps, depth, desc, smb_io_clnt_srv);
@@ -1323,22 +1323,22 @@ static BOOL smb_io_clnt_srv(const char *
if(!prs_align(ps))
return False;
- if(!prs_uint32(undoc_buffer , ps, depth, log-undoc_buffer))
+ if(!prs_uint32(undoc_buffer , ps, depth, clog-undoc_buffer))
return False;
- if (log-undoc_buffer != 0) {
- if(!smb_io_unistr2(unistr2, log-uni_logon_srv, log-undoc_buffer, ps, depth))
+ if (clog-undoc_buffer != 0) {
+ if(!smb_io_unistr2(unistr2, clog-uni_logon_srv, clog-undoc_buffer, ps, depth))
return False;
}
if(!prs_align(ps))
return False;
- if(!prs_uint32(undoc_buffer2, ps, depth, log-undoc_buffer2))
+ if(!prs_uint32(undoc_buffer2, ps, depth, clog-undoc_buffer2))
return False;
- if (log-undoc_buffer2 != 0) {
- if(!smb_io_unistr2(unistr2, log-uni_comp_name, log-undoc_buffer2, ps, depth))
+ if (clog-undoc_buffer2 != 0) {
+ if(!smb_io_unistr2(unistr2, clog-uni_comp_name, clog-undoc_buffer2, ps, depth))
return False;
}
@@ -1349,28 +1349,28 @@ static BOOL smb_io_clnt_srv(const char *
Inits a DOM_LOG_INFO structure.
/
-void init_log_info(DOM_LOG_INFO *log, const char *logon_srv, const char *acct_name,
+void init_log_info(DOM_LOG_INFO *clog, const char *logon_srv, const char *acct_name,
uint16 sec_chan, const char *comp_name)
{
DEBUG(5,(make_log_info %d\n, __LINE__));
- log-undoc_buffer = 1;
+ clog-undoc_buffer = 1;
- init_unistr2(log-uni_logon_srv, logon_srv, strlen(logon_srv)+1);
- init_unistr2(log-uni_acct_name, acct_name, strlen(acct_name)+1);
+ init_unistr2(clog-uni_logon_srv, logon_srv, strlen(logon_srv)+1);
+ init_unistr2(clog-uni_acct_name, acct_name, strlen(acct_name)+1);
- log-sec_chan = sec_chan;
+ clog-sec_chan = sec_chan;
- init_unistr2(log-uni_comp_name, comp_name, strlen(comp_name)+1);
+ init_unistr2(clog-uni_comp_name, comp_name, strlen(comp_name)+1);
}
/***
Reads or writes a DOM_LOG_INFO structure.
/
-BOOL smb_io_log_info(const char *desc, DOM_LOG_INFO *log, prs_struct *ps, int depth)
+BOOL smb_io_log_info(const char *desc, DOM_LOG_INFO *clog, prs_struct *ps, int depth)
{
- if (log == NULL)
+ if (clog == NULL)
return False;
prs_debug(ps, depth, desc, smb_io_log_info);
@@ -1379,18 +1379,18 @@ BOOL smb_io_log_info(const char *desc, D
if(!prs_align(ps))
return False;
- if(!prs_uint32(undoc_buffer, ps, depth, log-undoc_buffer))
+ if(!prs_uint32(undoc_buffer, ps, depth, clog-undoc_buffer))
return False;
- if(!smb_io_unistr2(unistr2, log-uni_logon_srv, True, ps, depth))
+ if(!smb_io_unistr2(unistr2, clog-uni_logon_srv, True, ps, depth))
return False;
- if(!smb_io_unistr2(unistr2, log-uni_acct_name, True, ps, depth))
+ if(!smb_io_unistr2(unistr2, clog-uni_acct_name, True, ps, depth))
return False;
-
[PATCH] Better fix for devicetype?
Would this be a better fix for the devicetype problem?
It looks like we are putting the strings into the buffer twice, and we
are not returning the 'fixed' devicetype for both protocol levels ( NT1
and NT1).
What happened here is that jermey 'fixed' a const warning. This meant
that this 'in/out' buffer became an 'in' buffer, and we didn't push the
correct devicetype back to the wire.
Volker then tried to fix the specific case he hit.
Andrew Bartlett
--
Andrew Bartlett [EMAIL PROTECTED]
Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED]
Student Network Administrator, Hawker College [EMAIL PROTECTED]
http://samba.org http://build.samba.org http://hawkerc.net
Index: smbd/reply.c
===
RCS file: /data/cvs/samba/source/smbd/reply.c,v
retrieving revision 1.422
diff -u -r1.422 reply.c
--- smbd/reply.c 25 Mar 2003 04:19:04 - 1.422
+++ smbd/reply.c 25 Mar 2003 10:51:14 -
-204,16 +204,21
{
fstring service;
DATA_BLOB password;
- fstring devicename;
+
+ /* what the cleint thinks the device is */
+ fstring client_devicetype;
+ /* what the server tells the client the share represents */
+ const char *server_devicetype;
NTSTATUS nt_status;
uint16 vuid = SVAL(inbuf,smb_uid);
int passlen = SVAL(inbuf,smb_vwv3);
pstring path;
char *p, *q;
extern BOOL global_encrypted_passwords_negotiated;
+
START_PROFILE(SMBtconX);
- *service = *devicename = 0;
+ *service = *client_devicetype = 0;
/* we might have to close an old one */
if ((SVAL(inbuf,smb_vwv2) 0x1) conn) {
-250,11 +255,11
else
fstrcpy(service,path);
- p += srvstr_pull(inbuf, devicename, p, sizeof(devicename), 6, STR_ASCII);
+ p += srvstr_pull(inbuf, client_devicetype, p, sizeof(client_devicetype), 6, STR_ASCII);
- DEBUG(4,(Got device type %s\n,devicename));
+ DEBUG(4,(Client requested device type [%s] for share [%s]\n, client_devicetype, service));
- conn = make_connection(service,password,devicename,vuid,nt_status);
+ conn = make_connection(service,password,client_devicetype,vuid,nt_status);
data_blob_clear_free(password);
-263,37 +268,30
return ERROR_NT(nt_status);
}
+ if ( IS_IPC(conn) )
+ server_devicetype = IPC;
+ else if ( IS_PRINT(conn) )
+ server_devicetype = LPT:;
+ else
+ server_devicetype = A:;
+
if (Protocol PROTOCOL_NT1) {
set_message(outbuf,2,0,True);
p = smb_buf(outbuf);
- p += srvstr_push(outbuf, p, devicename, -1,
+ p += srvstr_push(outbuf, p, server_devicetype, -1,
STR_TERMINATE|STR_ASCII);
set_message_end(outbuf,p);
} else {
/* NT sets the fstype of IPC$ to the null string */
const char *fsname = IS_IPC(conn) ? : lp_fstype(SNUM(conn));
- const char *devicetype;
-
set_message(outbuf,3,0,True);
- if ( IS_IPC(conn) )
- devicetype = IPC;
- else if ( IS_PRINT(conn) )
- devicetype = LPT:;
- else
- devicetype = A:;
-
p = smb_buf(outbuf);
- p += srvstr_push(outbuf, p, IS_IPC(conn) ? IPC : devicetype, -1,
+ p += srvstr_push(outbuf, p, server_devicetype, -1,
STR_TERMINATE|STR_ASCII);
p += srvstr_push(outbuf, p, fsname, -1,
STR_TERMINATE);
p = smb_buf(outbuf);
- p += srvstr_push(outbuf, p, IS_IPC(conn) ? IPC : devicename, -1,
- STR_TERMINATE|STR_ASCII);
- p += srvstr_push(outbuf, p, fsname, -1,
- STR_TERMINATE);
-
set_message_end(outbuf,p);
/* what does setting this bit do? It is set by NT4 and
signature.asc
Description: This is a digitally signed message part
Mounting to a Windows Share
From my RH 8 box I use smbmount to mount a share to \\windows2k\fileshare1 \\windows2k\fileshare1 . The mount point is created.. Now I want to use either chmod, or chown and change the file called 'testing.txt', no matter what I do I still get the error operation not permitted. My whole point in doing all this is so my linux boxes can write to a file share in windows, and so I may change the ownership of those files and folders. Additionally since I'm using winbind when I use chown on a file or folder I want the ACL's on windows to be changed to reflect this info. Can anyone tell me if this is possible and if so what actions I must take? Thank you,
Re: Mounting to a Windows Share
On March 25, [EMAIL PROTECTED] said: Can anyone tell me if this is possible and if so what actions I must take? Not presently possible. The files remain owned by the user/group that you used for the smbmount command. Cheers, Waider. -- [EMAIL PROTECTED] / Yes, it /is/ very personal of me. dhalgren says to waider, dude, your computers aren't even countable, they're like some kind of giant unitary cruftdevice
RE: Mounting to a Windows Share
Does anyone know if this will be possible in future releases of samba? Anyone have a work around? Thanks again! -Original Message- From: Ronan Waide [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 8:59 AM To: Eisenstein, Doug Cc: '[EMAIL PROTECTED]' Subject: Re: Mounting to a Windows Share On March 25, [EMAIL PROTECTED] said: Can anyone tell me if this is possible and if so what actions I must take? Not presently possible. The files remain owned by the user/group that you used for the smbmount command. Cheers, Waider. -- [EMAIL PROTECTED] / Yes, it /is/ very personal of me. dhalgren says to waider, dude, your computers aren't even countable, they're like some kind of giant unitary cruftdevice
RE: Mounting to a Windows Share
At 09:00 25.03.2003 -0500, Eisenstein, Doug wrote: Does anyone know if this will be possible in future releases of samba? Anyone have a work around? you can use smbcacls to change the permisions on files/directories metze - Stefan metze Metzmacher [EMAIL PROTECTED]
RE: Mounting to a Windows Share
Does anyone know if this will be possible in future releases of samba? It's not really a samba issue, it's an SMBFS issue. You may want to check out the Linux CIFS VFS at http://us1.samba.org/samba/Linux_CIFS_client.html I'm not sure if this can do what you want yet, but you can contact the author (Steve French) and ask. He's still developing it and input is appreciated. Jim McDonough IBM Linux Technology Center Samba Team 6 Minuteman Drive Scarborough, ME 04074 USA [EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (207) 885-5565 IBM tie-line: 776-9984
[PATCH] fix segfault in smbcontrol
Hi all, here's a small fix that prevents us from segfaulting... please apply this to all all branches witch are infected :-) metze - Stefan metze Metzmacher [EMAIL PROTECTED] smbcontrol.diff Description: Binary data
[patch] uppercase workgroup in browse request
Hi! I noticed a difference between testsmbc smb://MYGRP and testsmbc smb://mygrp (it doesn't make a difference for SAMBA servers, but it does for XP and for winME) So please apply the included patch. Greetings, Stephan Index: libsmb/clirap.c === RCS file: /cvsroot/samba/source/libsmb/clirap.c,v retrieving revision 1.30 diff -u -3 -p -u -r1.30 clirap.c --- libsmb/clirap.c 15 Mar 2003 06:45:19 - 1.30 +++ libsmb/clirap.c 25 Mar 2003 15:25:20 - @@ -233,8 +233,10 @@ BOOL cli_NetServerEnum(struct cli_state SIVAL(p,0,stype); p += 4; - p += push_pstring_base(p, workgroup, param); - + pstrcpy_base(p, workgroup, param); + strupper(p); + p += strlen(p); + if (cli_api(cli, param, PTR_DIFF(p,param), 8,/* params, length, max */ NULL, 0, CLI_BUFFER_SIZE, /* data, length, max */
Re: Problems with ACLs in 2.2.8 (solved)
Michael Steffens wrote: I could (almost) reproduce it on HP-UX, and (almost) fix it using inherit acls = Yes. :) Both almost refer to mask (or class, respectively) behaving a bit strange. But this might be platform specific. Yes. inherit acls = yes solves my problem. Thanks to all who helped! -- Honza Houstek
Re: [PATCH] Better fix for devicetype?
On Tue, Mar 25, 2003 at 10:02:13PM +1100, Andrew Bartlett wrote: Would this be a better fix for the devicetype problem? It looks like we are putting the strings into the buffer twice, and we are not returning the 'fixed' devicetype for both protocol levels ( NT1 and NT1). What happened here is that jermey 'fixed' a const warning. This meant that this 'in/out' buffer became an 'in' buffer, and we didn't push the correct devicetype back to the wire. Well it wasn't so much a warning as a bug. We were passing quoted strings into that function in some cases, so writing into them was not recommended :-). Jeremy.
Re: Problems with ACLs in 2.2.8
Date: Mon, 24 Mar 2003 19:43:18 + From: [EMAIL PROTECTED] To: Jan Houstek [EMAIL PROTECTED] Cc: Samba technical list [EMAIL PROTECTED] Subject: Re: Problems with ACLs in 2.2.8 Message-ID: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED]; +0100 References: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Precedence: list Message: 12 On Mon, Mar 24, 2003 at 08:39:22PM +0100, Jan Houstek wrote: Hi all! I posted this in [EMAIL PROTECTED] but there were no reactions. Particulary I'm interested if anyone observe the same behavior. I'll take a look at this. Jeremy. As long as you're having a look, will you give a look at the mode problem at file create time? In some cases samba over-rides the umask and inherited acls and creates the file as r--r--r--. Only samba's force create will kind of fix that. It's like the --with-acl-support is not always working. Jeff
winbind build/link question
I'm trying to use some of the functions in winbind_nss.c in my winbind_aix.c module. It compiles, but when I try to link it fill_pwent is unresolved. What do I need to link against in order to get fill_pwent and such from winbind_nss.c? I tried making nsswitch/winbind_nss.o and linking against that, but it still didn't resolve fill_pwent. I realize this is basic stuff that maybe I should be able to figure out from the Makefile, but it's an order of magnitude more complex than anything I've tried to work with before. Bear with me, I'm trying, Steve Roylance
SMB URL
Hi! I looked into the URL handling libsmbclient is doing and it's lacking quite some of the stuff that the DRAFT specifies (and some of the stuff that generally are required for URIs). Is someone working on that? I'm currently preparing some patches, but hate C programming enough to dump it for some other solution :) Greetings, Stephan
working winbind for AIX
Still a work-in-progress, but this compiles and works as expected on AIX 5.1. I haven't implemented getgrset yet, the NSS API is pretty different from AIX in that case. It also needs a mechanism to allocate more memory when the winbind response is larger than 4096 bytes. I had to copy fill_pwent, fill_grent, next_token and get_static from winbind_nss.c because they currently IFDEF out on AIX because of the lack of NSS API (I think). Compile with: gcc -o WINBIND winbind_aix.c -lsys -lcsys -lc -I../include -I.. -Xlinker -bM:SRE -Xlinker -ewb_aix_init wb_common.o Feedback would be nice, does anybody other than me need this? -Steve winbind_aix.c Description: Binary data
Re: msdfs broken in 2.2.8
On Mon, Mar 24, 2003 at 02:30:32PM -0800, Eric Horst wrote:
Hello! With great enthusiasm I upgraded from 2.2.7a to 2.2.8 last week
to get the critical security fix. However, it appears that msdfs is
broken in 2.2.8. Several on the 'samba' list have reported this as
well. Some say it works OK for W2K but not for XP. In my case I know
it doesn't work for XP clients. Testing, switching back and forth from
2.2.7a to 2.2.8 and using various clients it consistently confirms that
2.2.8 doesn't work. I dug through logs, source and the 2.2.7a to 2.2.8
diff and can't see any obvious change that would have broken it. I've
tried hard over the last few days to understand the flow through the
code and find the problem but haven't been successful.
Would a saavy Samba technical person be willing to work with me on
resolving this? I have logs and data but lacking an obvious focal point
for the problem I can't summarize the logs enough to include them in
this message.
Here is the fix for Samba 2.2.8 to make MS-DFS work again with WinXP.
(For once this wasn't my fault :-).
Sorry for the problem,
Jeremy.
Index: smbd/trans2.c
===
RCS file: /data/cvs/samba/source/smbd/trans2.c,v
retrieving revision 1.149.4.98
diff -u -r1.149.4.98 trans2.c
--- smbd/trans2.c 7 Mar 2003 23:35:00 - 1.149.4.98
+++ smbd/trans2.c 25 Mar 2003 23:36:05 -
@@ -3043,7 +3043,7 @@
{
char *params = *pparams;
enum remote_arch_types ra_type = get_remote_arch();
- BOOL NT_arch = ((ra_type == RA_WINNT) || (ra_type == RA_WIN2K));
+ BOOL NT_arch = ((ra_type == RA_WINNT) || (ra_type == RA_WIN2K) || (ra_type ==
RA_WINXP) || (ra_type == RA_WIN2K3));
pstring pathname;
int reply_size = 0;
int max_referral_level;
domain trusts with security=domain does not work for 3.0a21?
Hello, I verified that when I use security=ads, the domain trusts work. But when I use security=domain and join the w2k domain using net rpc join, I don't see any trusted domain. I checked with wbinfo -m, wbinfo --sequence and finally add ACL entries for a file served by samba. I see that if I use HEAD, security=domain, doing wbinfo -m gives a list of domains I expected. So my question is, what have been done to fix this? I would like to merge the code back if possible. I can not upgrade to HEAD, because there are too many changes. 3.0a21 works for us, well, mostly. Thanks in advance! Chere
RE: msdfs broken in 2.2.8
Thanks Jeremy. Works much better now.
--Eric
Here is the fix for Samba 2.2.8 to make MS-DFS work again with WinXP.
(For once this wasn't my fault :-).
Sorry for the problem,
Jeremy.
Index: smbd/trans2.c
===
RCS file: /data/cvs/samba/source/smbd/trans2.c,v
retrieving revision 1.149.4.98
diff -u -r1.149.4.98 trans2.c
--- smbd/trans2.c 7 Mar 2003 23:35:00 - 1.149.4.98
+++ smbd/trans2.c 25 Mar 2003 23:36:05 -
@@ -3043,7 +3043,7 @@
{
char *params = *pparams;
enum remote_arch_types ra_type = get_remote_arch();
- BOOL NT_arch = ((ra_type == RA_WINNT) || (ra_type ==
RA_WIN2K));
+ BOOL NT_arch = ((ra_type == RA_WINNT) || (ra_type ==
RA_WIN2K)
+ || (ra_type == RA_WINXP) || (ra_type == RA_WIN2K3));
pstring pathname;
int reply_size = 0;
int max_referral_level;
A please report me error
In today's CVS, I caught this message zip by while configuring: ... checking net/if.h presence... yes configure: WARNING: net/if.h: present but cannot be compiled configure: WARNING: net/if.h: check for missing prerequisite headers? configure: WARNING: net/if.h: proceeding with the preprocessor's result configure: WARNING: ## ## configure: WARNING: ## Report this to [EMAIL PROTECTED] ## configure: WARNING: ## ## checking for net/if.h... yes Anyone want to pass it on the gnuvians, as asked? --dave -- David Collier-Brown, | Always do right. This will gratify Americas Customer Eng | some people and astonish the rest. at Sun Canada | -- Mark Twain (905) 415-2849| [EMAIL PROTECTED]
Re: A please report me error
Am Tuesday 25 March 2003 21:46 schrieb Dave Collier-Brown: In today's CVS, I caught this message zip by while configuring: ... checking net/if.h presence... yes configure: WARNING: net/if.h: present but cannot be compiled configure: WARNING: net/if.h: check for missing prerequisite headers? configure: WARNING: net/if.h: proceeding with the preprocessor's result configure: WARNING: ## ## configure: WARNING: ## Report this to [EMAIL PROTECTED] ## configure: WARNING: ## ## checking for net/if.h... yes Anyone want to pass it on the gnuvians, as asked? Better check your config.log and find out what header it requires. Greetings, Stephan
RE: Compile error in server.c
Well, that's what I was saying I did. I first did just a 'make clean' and rebuilt, but then I went further and did a 'make distclean', followed by 'autoconf', './configure', and 'make'. Both ways result in the compile error. Thanks, James -Original Message- From: Jelmer Vernooij [mailto:[EMAIL PROTECTED] On Behalf Of Jelmer Vernooij Sent: Tuesday, March 25, 2003 4:15 PM To: James Willard Cc: [EMAIL PROTECTED] Subject: Re: Compile error in server.c Importance: High On Tue, Mar 25, 2003 at 04:12:04PM -0500, James Willard wrote about 'Compile error in server.c': I'm getting an error when trying to compile the HEAD branch of Samba. I've been following it in CVS since, well, since it was created. The problem suddenly appeared about a week or two ago and I've been updating daily ever since to see if it would go away. Despite a 'make distclean', removing config.h, and rebuilding, the error still exists: Compiling smbd/server.c smbd/server.c: In function `main': smbd/server.c:862: `static_init_rpc' undeclared (first use in this function) smbd/server.c:862: (Each undeclared identifier is reported only once smbd/server.c:862: for each function it appears in.) make: *** [smbd/server.o] Error 1 make clean ./configure make should fix this. Jelmer -- Jelmer Vernooij [EMAIL PROTECTED] - http://nl.linux.org/~jelmer/ 22:13:59 up 8 days, 4:28, 24 users, load average: 0.14, 0.29, 0.25
Re: Compile error in server.c
On Tue, Mar 25, 2003 at 04:19:12PM -0500, James Willard wrote about 'RE: Compile error in server.c': Well, that's what I was saying I did. I first did just a 'make clean' and rebuilt, but then I went further and did a 'make distclean', followed by 'autoconf', './configure', and 'make'. Both ways result in the compile error. Have you tried that again lately after doing a 'cvs update -dP .' ? It really should work now... Jelmer -Original Message- From: Jelmer Vernooij [mailto:[EMAIL PROTECTED] On Behalf Of Jelmer Vernooij Sent: Tuesday, March 25, 2003 4:15 PM To: James Willard Cc: [EMAIL PROTECTED] Subject: Re: Compile error in server.c Importance: High On Tue, Mar 25, 2003 at 04:12:04PM -0500, James Willard wrote about 'Compile error in server.c': I'm getting an error when trying to compile the HEAD branch of Samba. I've been following it in CVS since, well, since it was created. The problem suddenly appeared about a week or two ago and I've been updating daily ever since to see if it would go away. Despite a 'make distclean', removing config.h, and rebuilding, the error still exists: Compiling smbd/server.c smbd/server.c: In function `main': smbd/server.c:862: `static_init_rpc' undeclared (first use in this function) smbd/server.c:862: (Each undeclared identifier is reported only once smbd/server.c:862: for each function it appears in.) make: *** [smbd/server.o] Error 1 make clean ./configure make should fix this. Jelmer -- Jelmer Vernooij [EMAIL PROTECTED] - http://nl.linux.org/~jelmer/ 22:13:59 up 8 days, 4:28, 24 users, load average: 0.14, 0.29, 0.25 -- Jelmer Vernooij [EMAIL PROTECTED] ~/.plan: poptify smbmount and others smb_register_vfs() pgp0.pgp Description: PGP signature
RE: Compile error in server.c
Yes I did that about an hour ago, but just to be absolutely sure I went ahead and did the following again just about 2 minutes ago: cvs update -d -P cd source make clean ./configure make Then I received the error once again: Compiling smbd/server.c smbd/server.c: In function `main': smbd/server.c:862: `static_init_rpc' undeclared (first use in this function) smbd/server.c:862: (Each undeclared identifier is reported only once smbd/server.c:862: for each function it appears in.) make: *** [smbd/server.o] Error 1 Thanks, James Willard [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jelmer Vernooij Sent: Tuesday, March 25, 2003 4:23 PM To: James Willard Cc: [EMAIL PROTECTED] Subject: Re: Compile error in server.c Importance: High On Tue, Mar 25, 2003 at 04:19:12PM -0500, James Willard wrote about 'RE: Compile error in server.c': Well, that's what I was saying I did. I first did just a 'make clean' and rebuilt, but then I went further and did a 'make distclean', followed by 'autoconf', './configure', and 'make'. Both ways result in the compile error. Have you tried that again lately after doing a 'cvs update -dP .' ? It really should work now... Jelmer -Original Message- From: Jelmer Vernooij [mailto:[EMAIL PROTECTED] On Behalf Of Jelmer Vernooij Sent: Tuesday, March 25, 2003 4:15 PM To: James Willard Cc: [EMAIL PROTECTED] Subject: Re: Compile error in server.c Importance: High On Tue, Mar 25, 2003 at 04:12:04PM -0500, James Willard wrote about 'Compile error in server.c': I'm getting an error when trying to compile the HEAD branch of Samba. I've been following it in CVS since, well, since it was created. The problem suddenly appeared about a week or two ago and I've been updating daily ever since to see if it would go away. Despite a 'make distclean', removing config.h, and rebuilding, the error still exists: Compiling smbd/server.c smbd/server.c: In function `main': smbd/server.c:862: `static_init_rpc' undeclared (first use in this function) smbd/server.c:862: (Each undeclared identifier is reported only once smbd/server.c:862: for each function it appears in.) make: *** [smbd/server.o] Error 1 make clean ./configure make should fix this. Jelmer -- Jelmer Vernooij [EMAIL PROTECTED] - http://nl.linux.org/~jelmer/ 22:13:59 up 8 days, 4:28, 24 users, load average: 0.14, 0.29, 0.25 -- Jelmer Vernooij [EMAIL PROTECTED] ~/.plan: poptify smbmount and others smb_register_vfs()
RE: Compile error in server.c
At 16:29 25.03.2003 -0500, James Willard wrote: Yes I did that about an hour ago, but just to be absolutely sure I went ahead and did the following again just about 2 minutes ago: cvs update -d -P cd source make clean ./configure make can you try: cvs update -d -P cd source make distclean rm configure ./autogen.sh ./configure make metze - Stefan metze Metzmacher [EMAIL PROTECTED]
Large RPC bug found, I think
Ok, I think I've figured this out, but since I'm relatively new to Samba internals I'm not entirely clear on how to fix it, or what I might break with my fix. In a large RPC call, such as an EnumPrinters 2 call with a big buffer, the DCE/RPC stuff gets split into several SMB messages and tossed into a WriteAndX loop. Running a comparison between Samba/NT4 and NT4/NT4, I noticed the following: * For all RPC traffic, if the RPC is unfragmented Samba sets both RPC_HDR_FIRST and RPC_HDR_LAST flags. NT4 sets neither if there's only as single RPC block. This is in rpc_api_pipe_req (possibly elsewhere). It's easily fixed, but I don't know if setting both flags is required behaviour for some other Windows version. * The RPC bind I'm seeing has a max tx/rx buffer size of 5680 bytes. This is independant of whether I use Samba or NT4 as the client. * NT4 sends RPCs via WriteAndX in chunks of 4292 bytes and 1392 bytes (to make 5680 bytes per pair of WriteAndX requests) using the Raw Pipe Write, so two bytes represent the length of the data and the payload is 4290 bytes. As a side note, this length field throws ethereal off being able to decode these packets, as best I can tell. * Samba sends RPCs chunked as 4096 bytes and 1584 bytes. It's not using the Raw Pipe Write. And now, what I think are bugs as opposed to implementation details: * NT4 only sets PIPE_START_MESSAGE on the very first packet; Samba sets this flag on all packets. * NT4 sets the WriteAndX remaining field to 5680 (max tx size) for the first packet and 1390 (max tx less size of first packet) for the second packet. Samba sets the remaining field to the packet size if PIPE_START_MESSAGE is set, and to zero otherwise. (code in cli_issue_write) * Lastly, from the packet traces it appears as if Samba issues each pair of writes before waiting for a response, while NT only issues a new write once it's got the previous response. I've got as far as getting the PIPE_START_MESSAGE flag working correctly. PIPE_RAW_MODE doesn't appear to be implemented in the low-level SMB write stuff. I'm not clear on a clean way of fixing the remaining field, though. Perhaps someone with a bit more understanding of this code could use the above to determine if I have, in fact, found a bug that needs fixing. Cheers, Waider. -- [EMAIL PROTECTED] / Yes, it /is/ very personal of me. For those that dont remember, PI is the big number that begins with three. - http://www.facade.com/legacy/amiinpi/
Re: Large RPC bug found, I think
On Wed, Mar 26, 2003 at 01:58:49AM +, Ronan Waide wrote: Ok, I think I've figured this out, but since I'm relatively new to Samba internals I'm not entirely clear on how to fix it, or what I might break with my fix. In a large RPC call, such as an EnumPrinters 2 call with a big buffer, the DCE/RPC stuff gets split into several SMB messages and tossed into a WriteAndX loop. Running a comparison between Samba/NT4 and NT4/NT4, I noticed the following: * For all RPC traffic, if the RPC is unfragmented Samba sets both RPC_HDR_FIRST and RPC_HDR_LAST flags. NT4 sets neither if there's only as single RPC block. This is in rpc_api_pipe_req (possibly elsewhere). It's easily fixed, but I don't know if setting both flags is required behaviour for some other Windows version. * The RPC bind I'm seeing has a max tx/rx buffer size of 5680 bytes. This is independant of whether I use Samba or NT4 as the client. * NT4 sends RPCs via WriteAndX in chunks of 4292 bytes and 1392 bytes (to make 5680 bytes per pair of WriteAndX requests) using the Raw Pipe Write, so two bytes represent the length of the data and the payload is 4290 bytes. As a side note, this length field throws ethereal off being able to decode these packets, as best I can tell. * Samba sends RPCs chunked as 4096 bytes and 1584 bytes. It's not using the Raw Pipe Write. And now, what I think are bugs as opposed to implementation details: * NT4 only sets PIPE_START_MESSAGE on the very first packet; Samba sets this flag on all packets. * NT4 sets the WriteAndX remaining field to 5680 (max tx size) for the first packet and 1390 (max tx less size of first packet) for the second packet. Samba sets the remaining field to the packet size if PIPE_START_MESSAGE is set, and to zero otherwise. (code in cli_issue_write) * Lastly, from the packet traces it appears as if Samba issues each pair of writes before waiting for a response, while NT only issues a new write once it's got the previous response. I've got as far as getting the PIPE_START_MESSAGE flag working correctly. PIPE_RAW_MODE doesn't appear to be implemented in the low-level SMB write stuff. I'm not clear on a clean way of fixing the remaining field, though. Perhaps someone with a bit more understanding of this code could use the above to determine if I have, in fact, found a bug that needs fixing. What is the bug you're trying to fix ? ie. What is the behaviour that Windows shows that is not correct with the Samba code ? Also, I'd feel happier if you tested and compared with Win2000/WinXP rather than WinNT as NT is rather old these days Jeremy.
RE: Compile error in server.c
Ahh.. Okay... That was the magic solution, running autogen.sh. I did not realize that was also a necessary component to run. On a side note, does anybody know when we can expect net ads password to function without a segfault? It will be really cool to have that feature. Thanks, James Willard [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Liguori Sent: Tuesday, March 25, 2003 4:50 PM To: James Willard Cc: 'Jelmer Vernooij'; [EMAIL PROTECTED] Subject: RE: Compile error in server.c Importance: High autoconf isn't enough. Run autogen.sh (to ensure autoheader is run too). Anthony Liguori Linux/Active Directory Interoperability Linux Technology Center (LTC) - IBM Austin E-mail: [EMAIL PROTECTED] Phone: (512) 838-1208 Tie Line: 678-1208
Re: [PATCH] Better fix for devicetype?
On Wed, 2003-03-26 at 03:28, Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25 Mar 2003, Andrew Bartlett wrote: Would this be a better fix for the devicetype problem? I may be blind here, but the only difference in your patch that I see is some rewritten debug messages. What am I overlooking? The second half of the patch? It looks like we are putting the strings into the buffer twice, and we are not returning the 'fixed' devicetype for both protocol levels ( NT1 and NT1). What happened here is that jermey 'fixed' a const warning. This meant that this 'in/out' buffer became an 'in' buffer, and we didn't push the correct devicetype back to the wire. Volker then tried to fix the specific case he hit. I could gripe about serious regressions here but I won't Not so much aimed at any one in particular cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc You can never go home again, Oatman, but I guess you can shop there. --John Cusack - Grosse Point Blank (1997) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+gIPLIR7qMdg1EfYRAtthAKCKEVVXzUUcNlSfO1MbYo2cJhtZBACg7J+C EyxqWrdm57jcnZRDtmUivTg= =1ig+ -END PGP SIGNATURE- -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net signature.asc Description: This is a digitally signed message part
VFS and the new modules system
Hi! Here's a patch that adds support to the VFS for the new modules system. The only problem is that it breaks all current modules, but I don't think I can do anything about that. Any objections? Jelmer -- Jelmer Vernooij [EMAIL PROTECTED] - http://nl.linux.org/~jelmer/ 23:26:54 up 8 days, 5:41, 24 users, load average: 0.07, 0.64, 1.97 Index: Makefile.in === RCS file: /home/cvs/samba/source/Makefile.in,v retrieving revision 1.648 diff -u -3 -p -d -r1.648 Makefile.in --- Makefile.in 25 Mar 2003 14:46:10 - 1.648 +++ Makefile.in 25 Mar 2003 16:25:11 - @@ -136,8 +136,7 @@ SCRIPTS = $(srcdir)/script/smbtar $(srcd [EMAIL PROTECTED]@ -VFS_MODULES = bin/[EMAIL PROTECTED]@ bin/[EMAIL PROTECTED]@ bin/[EMAIL PROTECTED]@ \ - bin/[EMAIL PROTECTED]@ bin/[EMAIL PROTECTED]@ +VFS_MODULES = @VFS_MODULES@ PDB_MODULES = @PDB_MODULES@ RPC_MODULES = @RPC_MODULES@ CHARSET_MODULES = @CHARSET_MODULES@ @@ -324,7 +325,7 @@ SMBD_OBJ_SRV = smbd/files.o smbd/chgpass smbd/process.o smbd/service.o smbd/error.o \ printing/printfsp.o lib/util_seaccess.o \ smbd/build_options.o \ - smbd/change_trust_pw.o \ + smbd/change_trust_pw.o @VFS_STATIC@ \ $(MANGLE_OBJ) SMBD_OBJ_BASE = $(SMBD_OBJ_SRV) $(MSDFS_OBJ) $(PARAM_OBJ) $(LIBSMB_OBJ) $(UBIQX_OBJ) \ @@ -604,7 +606,7 @@ NTLM_AUTH_OBJ = utils/ntlm_auth.o $(LIBN # now the rules... ## all : SHOWFLAGS proto_exists $(SBIN_PROGS) $(BIN_PROGS) $(SHLIBS) \ - $(TORTURE_PROGS) @EXTRA_ALL_TARGETS@ + $(TORTURE_PROGS) $(MODULES) @EXTRA_ALL_TARGETS@ pam_smbpass : SHOWFLAGS bin/[EMAIL PROTECTED]@ @@ -1020,27 +1022,27 @@ bin/[EMAIL PROTECTED]@: $(XML_OBJ) @$(SHLD) $(LDSHFLAGS) -o $@ $(XML_OBJ) @XML_LIBS@ \ @[EMAIL PROTECTED] [EMAIL PROTECTED] -bin/[EMAIL PROTECTED]@: $(VFS_AUDIT_OBJ) +bin/[EMAIL PROTECTED]@: $(VFS_AUDIT_OBJ) @echo Building plugin $@ @$(SHLD) $(LDSHFLAGS) -o $@ $(VFS_AUDIT_OBJ) \ @[EMAIL PROTECTED] [EMAIL PROTECTED] -bin/[EMAIL PROTECTED]@: $(VFS_EXTD_AUDIT_OBJ) +bin/[EMAIL PROTECTED]@: $(VFS_EXTD_AUDIT_OBJ) @echo Building plugin $@ @$(SHLD) $(LDSHFLAGS) -o $@ $(VFS_AUDIT_OBJ) \ @[EMAIL PROTECTED] [EMAIL PROTECTED] -bin/[EMAIL PROTECTED]@: $(VFS_RECYCLE_OBJ) +bin/[EMAIL PROTECTED]@: $(VFS_RECYCLE_OBJ) @echo Building plugin $@ @$(SHLD) $(LDSHFLAGS) -o $@ $(VFS_RECYCLE_OBJ) \ @[EMAIL PROTECTED] [EMAIL PROTECTED] -bin/[EMAIL PROTECTED]@: $(VFS_NETATALK_OBJ) +bin/[EMAIL PROTECTED]@: $(VFS_NETATALK_OBJ) @echo Building plugin $@ @$(SHLD) $(LDSHFLAGS) -o $@ $(VFS_NETATALK_OBJ) \ @[EMAIL PROTECTED] [EMAIL PROTECTED] -bin/[EMAIL PROTECTED]@: $(VFS_FAKE_PERMS_OBJ) +bin/[EMAIL PROTECTED]@: $(VFS_FAKE_PERMS_OBJ) @echo Building plugin $@ @$(SHLD) $(LDSHFLAGS) -o $@ $(VFS_FAKE_PERMS_OBJ) \ @[EMAIL PROTECTED] [EMAIL PROTECTED] @@ -1074,7 +1076,7 @@ bin/[EMAIL PROTECTED]@: bin/libbigballofmu bin/[EMAIL PROTECTED]@: bin/[EMAIL PROTECTED]@ torture/t_stringoverflow.o $(CC) $(FLAGS) -o $@ torture/t_stringoverflow.o -L./bin -lbigballofmud -install: installbin installman installscripts installdat installswat +install: installbin installman installscripts installdat installswat installmodules # DESTDIR is used here to prevent packagers wasting their time # duplicating the Makefile. Remove it and you will have the privelege Index: configure.in === RCS file: /home/cvs/samba/source/configure.in,v retrieving revision 1.432 diff -u -3 -p -d -r1.432 configure.in --- configure.in25 Mar 2003 14:46:10 - 1.432 +++ configure.in25 Mar 2003 16:25:13 - @@ -239,7 +239,7 @@ AC_VALIDATE_CACHE_SYSTEM_TYPE DYNEXP= dnl Add modules that have to be built by default here -default_modules=pdb_smbpasswd pdb_tdbsam pdb_unix rpc_lsa rpc_samr rpc_reg rpc_wks rpc_net rpc_dfs rpc_srv rpc_spoolss auth_rhosts auth_sam auth_unix auth_winbind auth_server auth_domain auth_builtin +default_modules=pdb_smbpasswd pdb_tdbsam pdb_unix rpc_lsa rpc_samr rpc_reg rpc_wks rpc_net rpc_dfs rpc_srv rpc_spoolss auth_rhosts auth_sam auth_unix auth_winbind auth_server auth_domain auth_builtin vfs_recycle vfs_audit vfs_extd_audit vfs_fake_perms vfs_netatalk # # Config CPPFLAG settings for strange OS's that must be set @@ -3397,6 +3397,13 @@ SMB_MODULE(auth_server, \$(AUTH_SERVER_O SMB_MODULE(auth_domain, \$(AUTH_DOMAIN_OBJ), bin/domain.so, AUTH) SMB_MODULE(auth_builtin, \$(AUTH_BUILTIN_OBJ), bin/builtin.so, AUTH) SMB_SUBSYSTEM(AUTH) + +SMB_MODULE(vfs_recycle, \$(VFS_RECYCLE_OBJ), bin/recycle.so, VFS) +SMB_MODULE(vfs_audit, \$(VFS_AUDIT_OBJ), bin/audit.so, VFS)
Re: [PATCH] Better fix for devicetype?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26 Mar 2003, Andrew Bartlett wrote: I may be blind here, but the only difference in your patch that I see is some rewritten debug messages. What am I overlooking? The second half of the patch? Ah...you mean adding the server_devicetype string into the PROTOCOL_NT1 branch. Yeah. That's fine. cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc You can never go home again, Oatman, but I guess you can shop there. --John Cusack - Grosse Point Blank (1997) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+gNgFIR7qMdg1EfYRAvk5AKDWvfjChW1cTuX+eBv2Dr8v8rOSRgCgqy9a SStWUJAJ0UDFsXzy5BvVGtU= =ZcsX -END PGP SIGNATURE-
Re: [PATCH] Better fix for devicetype?
On Wed, 2003-03-26 at 09:28, Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26 Mar 2003, Andrew Bartlett wrote: I may be blind here, but the only difference in your patch that I see is some rewritten debug messages. What am I overlooking? The second half of the patch? Ah...you mean adding the server_devicetype string into the PROTOCOL_NT1 branch. Yeah. That's fine. And removing the second set of push_string()s. It looked like you had some kind of merge error - your patch added new push_string() calls, rather than modified the original push_string() lines. Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net signature.asc Description: This is a digitally signed message part
RE: Compile error in server.c
Maybe use the -A option to cvs update, to clear any sticky tags that might
be applied to your files. Such tags would prevent the latest code from being
downloaded.
-Original Message-
From: James Willard [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 3:52 PM
To: 'Jelmer Vernooij'
Cc: [EMAIL PROTECTED]
Subject: RE: Compile error in server.c
I promise you, I did everything that I said I did, including running
make clean, make distclean, cvs update -d -P, autoconf, and ./configure.
Is there something you would like for me to look at? My include/config.h
does not have that #define, despite having rm'd include/config.h and
running ./configure again.
James
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Jelmer Vernooij
Sent: Tuesday, March 25, 2003 4:41 PM
To: James Willard
Cc: [EMAIL PROTECTED]
Subject: Re: Compile error in server.c
Importance: High
On Tue, Mar 25, 2003 at 04:29:01PM -0500, James Willard wrote about 'RE:
Compile error in server.c':
Yes I did that about an hour ago, but just to be absolutely sure I
went ahead and did the following again just about 2 minutes ago:
cvs update -d -P
cd source
make clean ./configure make
Then I received the error once again:
Compiling smbd/server.c
smbd/server.c: In function `main':
smbd/server.c:862: `static_init_rpc' undeclared (first use in this
function)
smbd/server.c:862: (Each undeclared identifier is reported only once
smbd/server.c:862: for each function it appears in.)
make: *** [smbd/server.o] Error 1
Are you really sure you've reran configure ? My include/config.h
contains:
/* Static init functions */
#define static_init_rpc { rpc_srv_init(); rpc_spoolss_init();}
Jelmer
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Jelmer Vernooij
Sent: Tuesday, March 25, 2003 4:23 PM
To: James Willard
Cc: [EMAIL PROTECTED]
Subject: Re: Compile error in server.c
Importance: High
On Tue, Mar 25, 2003 at 04:19:12PM -0500, James Willard wrote about
'RE: Compile error in server.c':
Well, that's what I was saying I did. I first did just a 'make
clean'
and rebuilt, but then I went further and did a 'make distclean',
followed by 'autoconf', './configure', and 'make'. Both ways result
in
the compile error.
Have you tried that again lately after doing a 'cvs update -dP .' ?
It really should work now...
Jelmer
-Original Message-
From: Jelmer Vernooij [mailto:[EMAIL PROTECTED] On Behalf
Of
Jelmer Vernooij
Sent: Tuesday, March 25, 2003 4:15 PM
To: James Willard
Cc: [EMAIL PROTECTED]
Subject: Re: Compile error in server.c
Importance: High
On Tue, Mar 25, 2003 at 04:12:04PM -0500, James Willard wrote about
'Compile error in server.c':
I'm getting an error when trying to compile the HEAD branch of
Samba.
I've been following it in CVS since, well, since it was created.
The
problem suddenly appeared about a week or two ago and I've been
updating daily ever since to see if it would go away. Despite a
'make
distclean', removing config.h, and rebuilding, the error still
exists:
Compiling smbd/server.c
smbd/server.c: In function `main':
smbd/server.c:862: `static_init_rpc' undeclared (first use in this
function)
smbd/server.c:862: (Each undeclared identifier is reported only
once
smbd/server.c:862: for each function it appears in.)
make: *** [smbd/server.o] Error 1
make clean ./configure make should fix this.
Jelmer
--
Jelmer Vernooij [EMAIL PROTECTED] - http://nl.linux.org/~jelmer/
22:13:59 up 8 days, 4:28, 24 users, load average: 0.14, 0.29, 0.25
--
Jelmer Vernooij
[EMAIL PROTECTED]
~/.plan:
poptify smbmount and others
smb_register_vfs()
--
Jelmer Vernooij [EMAIL PROTECTED]
~/.plan:
poptify smbmount and others
smb_register_vfs()
Re: winbind build/link question
On Tue, Mar 25, 2003 at 12:37:33PM -0500, Roylance, Stephen D. wrote: I'm trying to use some of the functions in winbind_nss.c in my winbind_aix.c module. It compiles, but when I try to link it fill_pwent is unresolved. What do I need to link against in order to get fill_pwent and such from winbind_nss.c? I tried making nsswitch/winbind_nss.o and linking against that, but it still didn't resolve fill_pwent. The fill_pwent function is static in winbind_nss.c You are probably trying to call it directly from your winbind_aix.c which won't work. Can winbind_aix.c be modelled like winbind_solaris.c? That is, wrapper functions abstract out the vendor specific nss stuff which then call the _nss_winbind_* functions. Tim.
Re: [PATCH] Better fix for devicetype?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26 Mar 2003, Andrew Bartlett wrote: And removing the second set of push_string()s. It looked like you had some kind of merge error - your patch added new push_string() calls, rather than modified the original push_string() lines. Ahh...yes. It was a merge error in HEAD. Thanks. You want to fix this up or should I? cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+gOAmIR7qMdg1EfYRArnpAJ9g0Ev3aZbrhyFjgYzGThlwP9WR7QCePGD9 +TZ71ovK1VywRxW0cxLntiU= =ZEsZ -END PGP SIGNATURE-
RE: winbind build/link question
The fill_pwent function is static in winbind_nss.c You are probably trying to call it directly from your winbind_aix.c which won't work. Can winbind_aix.c be modelled like winbind_solaris.c? That is, wrapper functions abstract out the vendor specific nss stuff which then call the _nss_winbind_* functions. Tim. I am by no means an expert. I don't understand the nss api at all, and I only understand the AIX API from studying it over the past two weeks. Nss and AIX loadable auth modules seem very different. In AIX the module is responsible for allocating the memory for the result structures. The return value is a pointer to the result struct and failure is communicated by returning NULL. I'm not sure if it's possible to differentiate between failure because an object wasn't found and some other kind of failure. It appears to be less work to go from AIX-winbind rather than AIX-nss-winbind. I can probably make it cleaner/more efficient if I rewrite what fill_pwent/fill_grent do for AIX, because winbind_aix has to allocate the memory itself anyway. -Steve
Re: VFS and the new modules system
At 23:29 25.03.2003 +0100, Jelmer Vernooij wrote:
I took Jelmer's patch and modifed it,
to support an easy way to have per connection default_vfs_ops
and per connection private data in the vfs modules
so every module registers and got a unique vfs module number for te current
smbd or vfstest process.
now the module only regiter the vfsops_tuple_struct array
and the vfs_init() and vfs_done() fn's are gone.
vfs_init_custom() hang the default ops for each module on the vfs_handle
and mark this handle with the unique vfs module number
#define VFS_HANDLE_GET_OPS(conn, ret) \
if
((default_vfs_ops=vfs_handle_get_ops(conn,vfs_module_number))==NULL) { \
DEBUG(0,(%s() failed to get
default_vfs_ops!\n,FUNCTION_MACRO)); \
ret; \
}
this macro helps the module to get its default_vfs_ops
struct vfs_ops *vfs_handle_get_ops(connection_struct *conn, int vfs_num)
{
struct smb_vfs_handle_struct *handle = NULL;
if (!conn) {
DEBUG(0,(vfs_handle_get_ops() called with NULL pointer.\n));
return NULL;
}
handle = conn-vfs_handles;
while (handle) {
if (handle-vfs_num == vfs_num) {
return handle-vfs_def_ops;
}
handle = handle-next;
}
return NULL;
}
I have converted vfs_recycle.c for this setup:
all options are now resolved in run time (if smb.conf changed and smbd got
-HUP)
the modified options are used
What's left todo for this fix up pramateric options a bit
basicly prevent us from memory leeks when we alloc the lp_params values on
each call
maybe we should cache the values and make the return values const
But that will be another patch...
I hope you see how the vfs stuff work.
Comments are welcome
Goodnight all...
metze
-
Stefan metze Metzmacher [EMAIL PROTECTED]
vfs-02.diff
Description: Binary data
Re: VFS and the new modules system
At 00:52 26.03.2003 +0100, Stefan (metze) Metzmacher wrote:
At 23:29 25.03.2003 +0100, Jelmer Vernooij wrote:
I took Jelmer's patch and modifed it,
to support an easy way to have per connection default_vfs_ops
and per connection private data in the vfs modules
so every module registers and got a unique vfs module number for te current
smbd or vfstest process.
now the module only regiter the vfsops_tuple_struct array
and the vfs_init() and vfs_done() fn's are gone.
vfs_init_custom() hang the default ops for each module on the vfs_handle
and mark this handle with the unique vfs module number
#define VFS_HANDLE_GET_OPS(conn, ret) \
if
((default_vfs_ops=vfs_handle_get_ops(conn,vfs_module_number))==NULL) { \
DEBUG(0,(%s() failed to get
default_vfs_ops!\n,FUNCTION_MACRO)); \
ret; \
}
this macro helps the module to get its default_vfs_ops
struct vfs_ops *vfs_handle_get_ops(connection_struct *conn, int vfs_num)
{
struct smb_vfs_handle_struct *handle = NULL;
if (!conn) {
DEBUG(0,(vfs_handle_get_ops() called with NULL
pointer.\n));
return NULL;
}
handle = conn-vfs_handles;
while (handle) {
if (handle-vfs_num == vfs_num) {
return handle-vfs_def_ops;
}
handle = handle-next;
}
return NULL;
}
I have converted vfs_recycle.c for this setup:
all options are now resolved in run time (if smb.conf changed and smbd got
-HUP)
the modified options are used
What's left todo for this fix up pramateric options a bit
basicly prevent us from memory leeks when we alloc the lp_params values on
each call
maybe we should cache the values and make the return values const
But that will be another patch...
I hope you see how the vfs stuff work.
Note: this patch is only a preview to get feedback
it's not tested and there maybe some typos and merging bugs
but here smbd/vfs.o and modules/vfs_recycle.o
are build fine (expect some cast warnings in vfs_recycle.o)
metze
-
Stefan metze Metzmacher [EMAIL PROTECTED]
Mounting to a Windows Share
Does anyone know if this will be possible in future releases of samba? It's not really a samba issue, it's an SMBFS issue. You may want to check out the Linux CIFS VFS at http://us1.samba.org/samba/Linux_CIFS_client.html If unix extensions = yes in the smb.conf file on the Samba server, then the cifs vfs can do chmod, chown, chgrp (the latter two are even easier if the local and remote name user/group name maps to the same uid or gid) to the server.A version of the corresponding mount helper, mount.cifs is also now available (and is optional, allowing you to mount using tcp names rather than ip addresses). Steve French Senior Software Engineer Linux Technology Center - IBM Austin phone: 512-838-2294 email: [EMAIL PROTECTED]
Re: A please report me error
Righto, the background information is as follows:. --dave uname -a SunOS hobbes 5.8 Generic_108528-18 sun4u sparc SUNW,Ultra-1 Compiler: gcc version 2.95.3 20010315 (release) And the log entries were: configure:4693: checking net/if.h usability configure:4706: gcc -c -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 conftest.c 5 In file included from configure:4763: /usr/include/net/if.h:225: field `ifa_addr' has incomplete type /usr/include/net/if.h:227: field `ifu_broadaddr' has incomplete type /usr/include/net/if.h:228: field `ifu_dstaddr' has incomplete type /usr/include/net/if.h:260: field `lnr_addr' has incomplete type /usr/include/net/if.h:329: field `lifru_addr' has incomplete type /usr/include/net/if.h:330: field `lifru_dstaddr' has incomplete type /usr/include/net/if.h:331: field `lifru_broadaddr' has incomplete type /usr/include/net/if.h:332: field `lifru_token' has incomplete type /usr/include/net/if.h:333: field `lifru_subnet' has incomplete type /usr/include/net/if.h:372: field `sa_addr' has incomplete type /usr/include/net/if.h:382: field `slr_src' has incomplete type /usr/include/net/if.h:383: field `slr_grp' has incomplete type /usr/include/net/if.h:402: field `ifru_addr' has incomplete type /usr/include/net/if.h:403: field `ifru_dstaddr' has incomplete type /usr/include/net/if.h:405: field `ifru_broadaddr' has incomplete type /usr/include/net/if.h:473: parse error before `sa_family_t' /usr/include/net/if.h:473: warning: no semicolon at end of struct or union /usr/include/net/if.h:476: parse error before `}' /usr/include/net/if.h:486: parse error before `sa_family_t' /usr/include/net/if.h:486: warning: no semicolon at end of struct or union /usr/include/net/if.h:495: parse error before `}' Stephan Kulow wrote/usr/include/net/if.h:626: field `ifta_saddr' has incomplete type /usr/include/net/if.h:627: field `ifta_daddr' has incomplete type configure:4709: $? = 1 configure: failed program was: | #line 4695 configure | /* confdefs.h. */ | | #define PACKAGE_NAME :#define PACKAGE_TARNAME | #define PACKAGE_VERSION | #define PACKAGE_STRING | #define PACKAGE_BUGREPORT | #define HAVE_VOLATILE 1 | #define _LARGEFILE64_SOURCE 1 | #define _FILE_OFFSET_BITS 64 | #define STDC_HEADERS 1 | #define HAVE_DIRENT_H 1 | #define TIME_WITH_SYS_TIME 1 | #define HAVE_SYS_WAIT_H 1 | #define HAVE_SYS_TYPES_H 1 | #define HAVE_SYS_STAT_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_MEMORY_H 1 | #define HAVE_STRINGS_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_UNISTD_H 1 | #define HAVE_ARPA_INET_H 1 | #define HAVE_SYS_FCNTL_H 1 | #define HAVE_SYS_SELECT_H 1 | #define HAVE_FCNTL_H 1 #define HAVE_SYS_UNISTD_H 1 | #define HAVE_UNISTD_H 1 | #define HAVE_UTIME_H 1 | #define HAVE_GRP_H 1 | #define HAVE_LIMITS_H 1 | #define HAVE_MEMORY_H 1 | /* end confdefs.h. */ | #include stdio.h | #if HAVE_SYS_TYPES_H | # include sys/types.h | #endif | #if HAVE_SYS_STAT_H | # include sys/stat.h | #endif | #if STDC_HEADERS | # include stdlib.h | # include stddef.h | #else | # if HAVE_STDLIB_H | # include stdlib.h | # endif | #endif | #endif | #if HAVE_STRING_H | # if !STDC_HEADERS HAVE_MEMORY_H | # include memory.h | # endif | # include string.h | #endif | #if HAVE_STRINGS_H | # include strings.h | #endif | #if HAVE_INTTYPES_H | # include inttypes.h | #else | # if HAVE_STDINT_H | # include stdint.h | # endif | #endif | #if HAVE_UNISTD_H | # include unistd.h | #endif | #include net/if.h configure:4725: result: no configure:4729: checking net/if.h presence configure:4740: gcc -E -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 conftest.c configure:4746: $? = 0 configure:4765: result: yes Tuesday 25 March 2003 21:46 schrieb Dave Collier-Brown: In today's CVS, I caught this message zip by while configuring: ... checking net/if.h presence... yes configure: WARNING: net/if.h: present but cannot be compiled configure: WARNING: net/if.h: check for missing prerequisite headers? configure: WARNING: net/if.h: proceeding with the preprocessor's result configure: WARNING: ## ## configure: WARNING: ## Report this to [EMAIL PROTECTED] ## configure: WARNING: ## ## checking for net/if.h... yes Anyone want to pass it on the gnuvians, as asked? Better check your config.log and find out what header it requires. Greetings, Stephan -- David Collier-Brown, | Always do right. This will gratify Americas Customer Eng | some people and astonish the rest. at Sun Canada | -- Mark Twain (905) 415-2849| [EMAIL PROTECTED]
BUG (samba 2.2.8): smbd -l logfile does not work under solaris
Folks ** I am not on this alias. Could all relevent replies please be CC'ed to me as well ** I have configured and compiled samba 2.2.8 with gcc 2.95.3 on Solaris 9 using the options --with-automount. When I try to use the command: smbd -D -l /var/log/log.smbd The log file is not created. Neither is the default log file which is in /usr/local/samba/var/. # /usr/local/samba/bin/smbd -D -l /var/log/log.smbd # ls -ald /var/log/log.smbd /var/log/log.smbd: No such file or directory The log file option in smb.conf works fine, but does not give you the granularity to have different log files for nmbd and smbd. tony
[pseudo-patch] source/web/swat.c
Samba 3.0, Line 1269 of web/swat.c references TRUE rather than the POSIX-ly correct True. There may be others; this is the one that killed the build on Stratus VOS. Would whoever checked in this change please correct it? Many thanks. PG -- Paul Green, Senior Technical Consultant, Stratus Technologies, Maynard, MA USA Voice: +1 978-461-7557; FAX: +1 978-461-3610 Speaking from Stratus not for Stratus
Re: Problems with ACLs in 2.2.8
Hello Jeff, Jeff Mandel wrote: As long as you're having a look, will you give a look at the mode problem at file create time? In some cases samba over-rides the umask and inherited acls and creates the file as r--r--r--. Only samba's force create will kind of fix that. It's like the --with-acl-support is not always working. Does that happen with 2.2.8? Some of the changes to Samba's ACL code were meant to avoid exactly this problem. In case it happens with 2.2.8, some details about the conditions under which it happens could be helpful. Cheers! Michael
Re: [pseudo-patch] source/web/swat.c
On Tue, 25 Mar 2003, Green, Paul wrote: Samba 3.0, Line 1269 of web/swat.c references TRUE rather than the POSIX-ly correct True. There may be others; this is the one that killed the build on Stratus VOS. Would whoever checked in this change please correct it? Many thanks. Done. - John T. PG -- Paul Green, Senior Technical Consultant, Stratus Technologies, Maynard, MA USA Voice: +1 978-461-7557; FAX: +1 978-461-3610 Speaking from Stratus not for Stratus -- John H Terpstra Email: [EMAIL PROTECTED]
Re: BUG (samba 2.2.8): smbd -l logfile does not work under solaris
Oh, that is just so annoying This must have changed from 2.0.x to 2.2.x. It was logfile in 2.0.10 (what I am upgrading from)... Well, I feel like a goose now.That works so much better. Thanks for the help tony --On Tuesday, March 25, 2003 09:46:16 PM -0500 Brian Poole [EMAIL PROTECTED] wrote: Reread the man page, -l is log directory, not log file. Caught me on first try as well. -b Quoting tony shepherd ([EMAIL PROTECTED]) from 26 March 2003: Folks ** I am not on this alias. Could all relevent replies please be CC'ed to me as well ** I have configured and compiled samba 2.2.8 with gcc 2.95.3 on Solaris 9 using the options --with-automount. When I try to use the command: smbd -D -l /var/log/log.smbd The log file is not created. Neither is the default log file which is in /usr/local/samba/var/. # /usr/local/samba/bin/smbd -D -l /var/log/log.smbd # ls -ald /var/log/log.smbd /var/log/log.smbd: No such file or directory The log file option in smb.conf works fine, but does not give you the granularity to have different log files for nmbd and smbd. tony
Re: [PATCH] Better fix for devicetype?
On Tue, Mar 25, 2003 at 05:02:58PM -0600, Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26 Mar 2003, Andrew Bartlett wrote: And removing the second set of push_string()s. It looked like you had some kind of merge error - your patch added new push_string() calls, rather than modified the original push_string() lines. You can fix (and test :-) it. (Given it was Win9X and WinNT that were particualry fussy on this one, my test env isn't quit up to it). Andrew Bartlett
Re: A please report me error
On Tue, Mar 25, 2003 at 03:46:27PM -0500, Dave Collier-Brown wrote: In today's CVS, I caught this message zip by while configuring: ... checking net/if.h presence... yes configure: WARNING: net/if.h: present but cannot be compiled configure: WARNING: net/if.h: check for missing prerequisite headers? configure: WARNING: net/if.h: proceeding with the preprocessor's result configure: WARNING: ## ## configure: WARNING: ## Report this to [EMAIL PROTECTED] ## configure: WARNING: ## ## checking for net/if.h... yes Anyone want to pass it on the gnuvians, as asked? Given that the configure script is no longer stored in CVS, this may be a problem specific to the version of autoconf that you have installed on your system. Have you checked if there's a more recent version available than what you're running? -- Steve Langasek postmodern programmer pgp0.pgp Description: PGP signature
Re: Compile error in server.c
On Tue, Mar 25, 2003 at 04:12:04PM -0500, James Willard wrote about 'Compile error in server.c': I'm getting an error when trying to compile the HEAD branch of Samba. I've been following it in CVS since, well, since it was created. The problem suddenly appeared about a week or two ago and I've been updating daily ever since to see if it would go away. Despite a 'make distclean', removing config.h, and rebuilding, the error still exists: Compiling smbd/server.c smbd/server.c: In function `main': smbd/server.c:862: `static_init_rpc' undeclared (first use in this function) smbd/server.c:862: (Each undeclared identifier is reported only once smbd/server.c:862: for each function it appears in.) make: *** [smbd/server.o] Error 1 make clean ./configure make should fix this. Jelmer -- Jelmer Vernooij [EMAIL PROTECTED] - http://nl.linux.org/~jelmer/ 22:13:59 up 8 days, 4:28, 24 users, load average: 0.14, 0.29, 0.25 pgp0.pgp Description: PGP signature
Re: SMB URL
On Tue, 25 Mar 2003 21:39:26 +0100 Stephan Kulow [EMAIL PROTECTED] wrote: Hi! I looked into the URL handling libsmbclient is doing and it's lacking quite some of the stuff that the DRAFT specifies (and some of the stuff that generally are required for URIs). Is someone working on that? I'm currently preparing some patches, but hate C programming enough to dump it for some other solution :) Greetings, Stephan Please look at the jCIFS mailing list for discussions in February about the SMB URL. There was an interesting discussion about Unicode hanlding. The problem of course is that URLs require characters outside of ASCII to be escaped with %HH hex escapes. This is of course not very reasonable with SMB URLs so hex escaping is not required. In practice this should not be a problem because these URLs are not submitted as parameters to text based RPCs like HTTP GET requests. We did reach an important conclusion that would be influential to anyone writing an SMB URL parser. That is, even though SMB URLs do not require Unicode characters be escaped (for practical reasons) they should be able to decode escaped Unicode characters. This begs the question; how do you escape Unicode characters? The prevailing answer appears to be specified in the W3C IRI documents which suggest each escape should be treated as a byte in a UTF-8 multibyte sequence. Otherwise, the SMB URL is reasonably well defined. Unicode handling was the only remaining issue I believe. The jCIFS client implements all of this functionality minus the decoding of escaped UTF-8 sequences. Please join the jCIFS mailing list if you have specific questions. We have had many interesting discussions there about the SMB URL, we have implemented it completely, and there are three people who understand it quite well. Chris and Eric have the brains. Me type. I'm not familiar with the state of the libsmbclient SMB URL handling. Mike -- A program should be written to model the concepts of the task it performs rather than the physical world or a process because this maximizes the potential for it to be applied to tasks that are conceptually similar and, more important, to tasks that have not yet been conceived.
RE: Compile error in server.c
autoconf isn't enough. Run autogen.sh (to ensure autoheader is run too). Anthony Liguori Linux/Active Directory Interoperability Linux Technology Center (LTC) - IBM Austin E-mail: [EMAIL PROTECTED] Phone: (512) 838-1208 Tie Line: 678-1208
RE: Compile error in server.c
I promise you, I did everything that I said I did, including running
make clean, make distclean, cvs update -d -P, autoconf, and ./configure.
Is there something you would like for me to look at? My include/config.h
does not have that #define, despite having rm'd include/config.h and
running ./configure again.
James
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Jelmer Vernooij
Sent: Tuesday, March 25, 2003 4:41 PM
To: James Willard
Cc: [EMAIL PROTECTED]
Subject: Re: Compile error in server.c
Importance: High
On Tue, Mar 25, 2003 at 04:29:01PM -0500, James Willard wrote about 'RE:
Compile error in server.c':
Yes I did that about an hour ago, but just to be absolutely sure I
went ahead and did the following again just about 2 minutes ago:
cvs update -d -P
cd source
make clean ./configure make
Then I received the error once again:
Compiling smbd/server.c
smbd/server.c: In function `main':
smbd/server.c:862: `static_init_rpc' undeclared (first use in this
function)
smbd/server.c:862: (Each undeclared identifier is reported only once
smbd/server.c:862: for each function it appears in.)
make: *** [smbd/server.o] Error 1
Are you really sure you've reran configure ? My include/config.h
contains:
/* Static init functions */
#define static_init_rpc { rpc_srv_init(); rpc_spoolss_init();}
Jelmer
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Jelmer Vernooij
Sent: Tuesday, March 25, 2003 4:23 PM
To: James Willard
Cc: [EMAIL PROTECTED]
Subject: Re: Compile error in server.c
Importance: High
On Tue, Mar 25, 2003 at 04:19:12PM -0500, James Willard wrote about
'RE: Compile error in server.c':
Well, that's what I was saying I did. I first did just a 'make
clean'
and rebuilt, but then I went further and did a 'make distclean',
followed by 'autoconf', './configure', and 'make'. Both ways result
in
the compile error.
Have you tried that again lately after doing a 'cvs update -dP .' ?
It really should work now...
Jelmer
-Original Message-
From: Jelmer Vernooij [mailto:[EMAIL PROTECTED] On Behalf
Of
Jelmer Vernooij
Sent: Tuesday, March 25, 2003 4:15 PM
To: James Willard
Cc: [EMAIL PROTECTED]
Subject: Re: Compile error in server.c
Importance: High
On Tue, Mar 25, 2003 at 04:12:04PM -0500, James Willard wrote about
'Compile error in server.c':
I'm getting an error when trying to compile the HEAD branch of
Samba.
I've been following it in CVS since, well, since it was created.
The
problem suddenly appeared about a week or two ago and I've been
updating daily ever since to see if it would go away. Despite a
'make
distclean', removing config.h, and rebuilding, the error still
exists:
Compiling smbd/server.c
smbd/server.c: In function `main':
smbd/server.c:862: `static_init_rpc' undeclared (first use in this
function)
smbd/server.c:862: (Each undeclared identifier is reported only
once
smbd/server.c:862: for each function it appears in.)
make: *** [smbd/server.o] Error 1
make clean ./configure make should fix this.
Jelmer
--
Jelmer Vernooij [EMAIL PROTECTED] - http://nl.linux.org/~jelmer/
22:13:59 up 8 days, 4:28, 24 users, load average: 0.14, 0.29, 0.25
--
Jelmer Vernooij
[EMAIL PROTECTED]
~/.plan:
poptify smbmount and others
smb_register_vfs()
--
Jelmer Vernooij [EMAIL PROTECTED]
~/.plan:
poptify smbmount and others
smb_register_vfs()
