Am 09.05.2013 07:35, Andrew Bartlett wrote:
The issue is that testparm forces the log level to ensure the warnings
are output.
Thanks for the clarification.
Must be new, never had difficulties before with old samba versions.
--
der tom
--
To unsubscribe from this list go to the following URL
Am 08.05.2013 11:18, schrieb Karolin Seeger:
Major enhancements in Samba 3.6.15 include:
How is the 'log level' in 3.6.15 defined?
From
http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#LOGLEVEL
[...]
Default: log level = 0
And:
debuglevel
This parameter is a synonym for
On 11.09.2011 04:44, Linda Walsh wrote:
This sounds like https://bugzilla.samba.org/show_bug.cgi?id=8412.
I don't think, it's the same problem. I already tried without oplocks
and smb2 isn't activated here.
Anyway - I could test a patch for 3.5.11.
Don't know if there is one -- and there was
Am 10.09.2011 03:22, schrieb ich:
Internet Explorer 9 on Windows 7 cannot save files on shares from Samba
3.5.11, but Firefox can do this.
With IE9 there is only a 0-Byte-file on the share.
Maybe this is a problem with delete on close on the temporary file
xxx.partial, which will be created
Am 10.09.2011 17:13, schrieb ich:
Internet Explorer 9 on Windows 7 cannot save files on shares from Samba
3.5.11, but Firefox can do this.
With IE9 there is only a 0-Byte-file on the share.
Maybe this is a problem with delete on close on the temporary file
xxx.partial, which will be created
Hi @all,
Internet Explorer 9 on Windows 7 cannot save files on shares from Samba
3.5.11, but Firefox can do this.
With IE9 there is only a 0-Byte-file on the share.
--
der tom
--
To unsubscribe from this list go to the following URL and read the
instructions:
Anybody?
Schould I better ask this in samba-techni...@lists.samba.org?
On 31.10.2010 01:43 I wrote:
Hi @all,
this is an very old problem, posted the first time 2005 to
samba-test...@samba.org:
If I have a Domain client with WinXP, which is part of a domain and
using this client, if the PDC
Hi @all,
this is an very old problem, posted the first time 2005 to
samba-test...@samba.org:
If I have a Domain client with WinXP, which is part of a domain and
using this client, if the PDC is not available and want to remote shut
down this client with the net tool from other servers, then
Am 28.09.2010 23:17, schrieb Leonardo Carneiro:
Well, in theory this should work. I'll try and post here if this will
work well. Tks in advance.
It works, you could use many combinations:
for user:
logon script = %u.bat %g %m
for group:
logon script = %g.bat %u %m
for machine:
logon script
David C. Rankin wrote:
Ok, I think the following patch should fix the issues
you're seeing. It should apply on top of, or in place
of my previous patch - shouldn't matter.
It causes all opens requiring SEC_RIGHT_SYSTEM_SECURITY
to fail as Windows does with NT_STATUS_PRIVILEGE_NOT_HELD,
which
Gerald (Jerry) Carter wrote:
This is the second release candidate of the Samba 3.0.25 code
base and is provided for testing only.
These messages are new while compiling:
deveis # make
[...]
Compiling auth/auth_script.c
Building plugin bin/script.so
make: *** No rule to make target
Freitas wrote:
You can try here.
http://us3.samba.org/samba/docs/man/Samba-HOWTO-Collection/AdvancedNetworkManagement.html#id386516
Sorry for being so stupid but how should this working?
From the above link:
preexec script = /sbin/PermitSingleLogon.sh
Okay, this script is called
Volker Lendecke wrote:
I mean this was functional in older samba versions...
Can you send sniffs of both behaviours?
Mmmh, in 3.0.23c and 3.0.21c the behavior is the same:
deveis # smbclient -Utb%password //192.168.0.15/jet
Domain=[TB3] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
Volker Lendecke wrote:
But why is it impossible to listing the printer share directory on
windows clients?
Asked the other way round: What would you expect there?
The same output as on linux machines:
From the first posting:
Here a try with a local smb printer queue on the linux host:
I'm using 3.0.24 with patches from http://us4.samba.org/samba/patches/.
On my XP client the print services for Unix are installed, I shared the
local printer named 'jet' on the XP client to all users and the
connecting user is an existing user on linux (system and samba user) and XP.
I
The online documentation is not complete, see
http://us4.samba.org/samba/docs/man/manpages-3/smb.conf.5.html
...
EXPLANATION OF EACH PARAMETER
xi:include/xi:include
WARNINGS
...
Maybe this has something to do with the fact, that us1.samba.org is down?
der tom
--
To unsubscribe from this
larry wrote:
Thanks. Sorry I took so long to get back but other things were a higher
priority. I got the patch (nb. cut paste from the browser window, don't try to
download the browser file 'cause those gt; etc will get you) and tried it.
There was no change in operation. I still got that same
larry wrote:
The practical solution is to replace this box with a more modern one.
But I would still like to find out why it doesn't work.
See the complete thread
http://marc.theaimsgroup.com/?l=sambam=116533540200375w=2
and the patch in
Volker Lendecke wrote:
Please try the attached patch. I simply forgot to merge this
to 3.0.23d in time, sorry.
Sorry Volker, what is the suggested fix for the problem? You attached
the patch to the poster but not to the list. Can you tell me the svn
revision number for that?
--
der tom
--
Volker Lendecke wrote:
[2006/05/25 15:25:42, 0] smbd/oplock_linux.c:linux_init_kernel_oplocks(247)
Failed to setup RT_SIGNAL_LEASE handler
[2006/05/25 15:25:42, 0] smbd/notify_kernel.c:kernel_notify_init(224)
Failed to setup RT_SIGNAL_NOTIFY handler
Is this a change from pre1? I'm not
Volker Lendecke wrote:
Switched back to 3.0.21c. Ouch, access to shares is not granted anymore :(
Are you using tdbsam? I think we upgrade passdb.tdb's
version.
No, using smbpasswd.
I don't understand the error message on the client. Samba isn't a domain
controller at this time.
der tom
Hi @all,
I have many messages in the log file with this version:
[2006/05/25 15:25:42, 0] smbd/oplock_linux.c:linux_init_kernel_oplocks(247)
Failed to setup RT_SIGNAL_LEASE handler
[2006/05/25 15:25:42, 0] smbd/notify_kernel.c:kernel_notify_init(224)
Failed to setup RT_SIGNAL_NOTIFY handler
Gerald (Jerry) Carter wrote:
Volker, I don't know of any outstanding issues with
kernel oplocks. Any ideas?
Volker, before you are asking:
No kernel changes, no changes to the operating system, no changes to the
configure options, no changes to the developer tools since a long time...
Thomas Bork wrote:
[2006/05/25 15:25:42, 0] smbd/oplock_linux.c:linux_init_kernel_oplocks(247)
Failed to setup RT_SIGNAL_LEASE handler
Switched back to 3.0.21c. Ouch, access to shares is not granted anymore :(
The client is confused and thinks the samba server is an domain controller
Bruno Guerreiro wrote:
Has anyone here tried samba4WINS?
If positive, anyone tried replication between samba and windows(NT4/2000)?
Did it work?
And will samba4wins be a part of the normal samba (3.x) in the future?
der tom
--
To unsubscribe from this list go to the following URL and read
Jeremy Allison wrote:
Well you know what strict allocate does, right ? It causes the space
for the file to be allocated on disk once the set fil allocation is
set from the Windows client. If the client then writes this data it'll
write everything twice. Why are you setting this ? You should not
Tom Peters wrote:
While copying the wmv test file a have a cpu utilization of 95!
percent (top) of smbd at the time, samba creates the sparse (?) file
in the size needed for the test file.
I don't believe this happens in my case. I am not certain. I know that
when it fails, Windows clients
Tom Peters wrote:
Tell me, do you get this problem when you drag/n/drop a file into a
folder on the samba share? And can you prevent this problem from
occurring by the following procedure?
I cannot see the problem here but heared from 2 users of 3.0.21c with
this problem.
Downloaded a
Hi @all,
are there any problems known with 3.0.21c and bigger video files (mpg
and wmv greater than 700 MB)?
Received the information that these files cannot copied from XP to Samba
(W2K is okay). Error message is the well known:
[2006/03/28 18:03:36, 0]
Gerald (Jerry) Carter wrote:
Can you send me your smb.conf? Thanks.
Did you received my smb.conf?
der tom
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Gerald (Jerry) Carter wrote:
Can you send me your smb.conf? Thanks.
Did you received my smb.conf?
der tom
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Gerald (Jerry) Carter wrote:
Can you send me your smb.conf? Thanks.
Did you received my smb.conf?
der tom
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Gerald (Jerry) Carter wrote:
This is the latest stable release of Samba. This is the version
that production Samba servers should be running for all current
bug-fixes. Please read the following important changes in this
release.
deveis # smbd -V
Version 3.0.21c-for-eisfair-1
deveis # net
Gerald (Jerry) Carter schrieb:
Did you start smbd afetr 'net setlocalsid' ? It's been a
while since I looked at that code but I have this vague
memory of smbd setting the DOMAIN sid from the machine
SID if the box is setup as a DC.
deveis # /etc/init.d/samba stop
Stopping Samba...
smbd was
Hi Jerry,
tried to playing around with eventlogs but:
smb.conf global part:
eventlog list = SyslogLinux
In your Samba-EventLog-HOWTO.txt:
When Samba initially starts, it looks to see if the
eventlog directory, and a particular log exists; if not,
the directory and file are created under
Mike Partyka wrote:
Your referring to POSIX ACL support in the kernel? I am not entirely sure
how to check for this in the standard precompliled kernel, and i believe
that support not to be common in most linux distro's so i would guess that,
POSIX ACL support is not enabled.
for pseudofile
Ben Donnelly wrote:
I noticed that the Release Notes for Samba 3.0.21 say that the oplock
implementation has been rewritten. And we seem to be having problems
with some .exe files we are sharing out as read-only shares. The shares
now only allow the first person to open the executable and run
Gerald (Jerry) Carter wrote:
| does anybody know, where privileges are stored?
account_pol.tdb
Thanks.
@jht:
Could not find this in
http://us3.samba.org/samba/docs/man/Samba3-HOWTO/NetCommand.html#id2568526
http://us3.samba.org/samba/docs/man/Samba3-HOWTO/rights.html
der tom
--
To
Hi @all,
does anybody know, where privileges are stored?
deveis # net rpc rights list 'Domain Power Users' -U root%password
SeMachineAccountPrivilege
SeBackupPrivilege
SeRestorePrivilege
SePrintOperatorPrivilege
SeDiskOperatorPrivilege
But:
deveis # ls -l /var/lock/samba/*.tdb
-rw--- 1
Tomasz Chmielewski wrote:
Any chance of sending in a network trace when this message is
received ? We need to see how the client is getting this message
in order to be able to do the same.
yeah why not, just tell me what do I have to capture (and how?) and I'll
try to do it.
Mmmh:
Julian Pilfold-Bagwell wrote:
I have several rooms each with a printer, and nearly a thousand users divided
into two main groups - pupils and teachers who change rooms on a routine
basis. Is it possible to set up multiple login scripts that would be executed
in sequence i.e. run by user is
Christoph Peus wrote:
You have to find the point in the migration process, where the new
sambaSID is calculated. Your migrated sambaSID is not correct.
Hmmm... if I understood the net rpc vampire migration magic right, the
SID is not calculated using the algorithm you explained above but
Christoph Peus wrote:
after net rpc vampire migration:
uidNumber: 22693
sambaSID: S-1-5-21-1139895982-289624505-398547282-4370
after the maschine rejoined the domain:
uidNumber: 22694
sambaSID: S-1-5-21-1139895982-289624505-398547282-46388
Hi Christoph, nice to read you :)
What shows
Dragan Krnic wrote:
From what I gathered in the documentations on both sides of the
fence, Unix traditionally stamps file times (create/status change,
modify and last read access) with a long integer (32 bits) counting
full seconds since midnight A.M. January 1, 1970 in Greenwhich, EU,
Gerald (Jerry) Carter schrieb:
2) 'map read only = yes' should give you 3.0.14a behavior.
- according to the docs wouldn't map read only = Permissions
or No give the 3.0.20 behaviour?
oh yeah. I forgot that jeremy decided to make it an enumerated
type rather than a boolean.
Documentation
Andreas Oster wrote:
[2005/10/24 12:29:33, 0] smbd/service.c:make_connection(798)
novaws20 (10.2.1.71) couldn't find service aoste
The last five messages are the relavant ones. The share mentioned
(aoster) is the home share of user aoster. This not only happens with
the home share but with
Gerald (Jerry) Carter wrote:
It's not our bug Andrew. I've generated traces from
a Win2K - WinXP that show the exact same thing. It's
a Windows 2000 client bug.
tb3 is a XP SP2 client. Thats why it must be a Windows 2000 *and*
Windows XP client bug.
der tom
--
To unsubscribe from this
Gary Dale wrote:
Alright so I have samba running as a PDC and have roaming profiles,
however when I Logon it does everything successfully but then it shows
a desktop file in notepad with some info on it. Has anyone seen this
before?
The desktop.ini file is normally in the startup group for
José M. Fandiño wrote:
If you want to disable roaming profiles *but* want to use 'net use ?:
/HOME', then remove 'logon home =' from smb.conf to using defaults for
home dir or set it to anything usefull for your needs.
confirmed, by removing 'logon home =' completely disables profiles
with
José M. Fandiño wrote:
I'm following the recipe 26.2.1.4 to disable roaming profiles for
win9x and XPpro machines, but perhaps I'm missing something because
it doesn't seem be possible get the home shares mapped with profiles
disabled.
windows machines fails with this error:
Jeremy Allison wrote:
[2005/09/10 10:15:56, 0] rpc_server/srv_pipe.c:api_pipe_bind_req(981)
Attempt to bind using schannel without successful serverauth2
[...]
This is on a 3.0.20 (with patches) PDC.
[...]
Right now it's informative - I'd like to see the traffic
that is causing it though.
Danny Paul wrote:
I've had a series of files get created in user profiles with a mtime of Dec
13, 1901 14:45. 'stat -c %Y' reports -2147483648.
[...]
This is not a filesystem problem, fscheck is clean as a whistle, this must
be a SAMBA issue. I suspect that whatever problem causes the
Danny Paul wrote:
Thanks for your reply - can you send me any information about the other
people who have had similar problems?
http://lists.spline.inf.fu-berlin.de/mailman/htdig/eisfair/2005-September/084330.html
You can find the mail address from Michael Ebersbach there.
der tom
--
To
Umberto Zanatta wrote:
| Sep 1 20:44:41 provtvlp smbd[7699]: Failed to setup RT_SIGNAL_LEASE
| handler
I have this message, if 3.0.20 was compiled with aio support - even if
aio support in smb.conf is deactivated with
aio read size =
aio write size =
This leads here to problems with
Jeremy Allison wrote:
| Sep 1 20:44:41 provtvlp smbd[7699]: Failed to setup RT_SIGNAL_LEASE
| handler
I have this message, if 3.0.20 was compiled with aio support - even if
[...]
aio support is exteremly experimental. I did it to learn about
what effects this would have on our performance
Gerald (Jerry) Carter wrote:
ok. Can you folks try out the patch at
http://samba.org/~jerry/patches/regcreatekey_v1.patch
and let me know if that fixes the usrmgr.exe failures
you are seeing? It should at least fix the REG_CREATE_KEY_EX
failures in the logs.
+
Gerald (Jerry) Carter wrote:
failure error though. I've also gone ahead and added
the registry key to the Samba's registry.tdb file in
the patch posted at http://www.samba.org/samba/patches/
The only error message in the samba logs while joining the 3.0.20 samba
domain with XP SP2 is now:
Carsten Sander schrieb:
On 3.0.20
net rpc group list:
returns the unix groupnames instead of the mapped groupnames
Cannot reproduce this with 3.0.20 (unpatched):
vmeis # net groupmap list
System Operators (S-1-5-32-549) - -1
Replicators (S-1-5-32-552) - -1
Guests (S-1-5-32-546) - -1
Domain
Gerald (Jerry) Carter wrote:
Cannot reproduce this with 3.0.20 (unpatched):
It was pretty easy to reproduce for me. Are you using ldapsam?
No - smbpasswd. I double checked this, cannot reproduce the error
(output from 'net rpc group list') with the unpatched sources.
There were actually
Steven French wrote:
Surprisingly NT4 still has a huge installed base, and cifs vfs did not
support it reasonably well until version 1.30 of the cifs vfs (which is
less than a year ago). Win9x/WinME has a large installed base as well,
but is somewhat less important as a server, and would be
Chris wrote:
Looks like something has changed as samba-vscan 0.3.6 (latest as of this
writing) doesn't compile with 3.0.20.
Replace in global/vscan-fileaccesslog.c in samba_vscan directory all
occurences of new with new_entry .
http://marc.theaimsgroup.com/?l=sambam=112127118323642w=2
der
Gerald (Jerry) Carter wrote:
vmeis # net rpc rights grant tb SePrintOperatorPrivilege
Password:
Failed to grant privileges for tb (NT_STATUS_NO_SUCH_PRIVILEGE)
Do you have 'enable privileges = yes' in smb.conf ? I should probably
prevent smbd from returning any list when the feature has been
Thomas Bork schrieb:
After setting 'enable privileges = yes' in smb.conf:
vmeis # net rpc rights grant tb SePrintOperatorPrivilege
Password:
Successfully granted rights.
vmeis # net rpc rights list accounts
Password:
VMEIS\tb
- no output
Thomas Bork schrieb:
vmeis # net rpc rights list accounts
Password:
BUILTIN\Print Operators
No privileges assigned
BUILTIN\Account Operators
No privileges assigned
BUILTIN\Backup Operators
No privileges assigned
VMEIS\tb
[2005/08/07 21:20:58, 0] rpc_client/cli_pipe.c:rpc_api_pipe(438
Gerald (Jerry) Carter wrote:
This is a release candidate of the 3.0.20 code base and
vmeis # net rpc rights list
Password:
SeMachineAccountPrivilege Add machines to domain
SeTakeOwnershipPrivilege Take ownership of files or other objects
SeBackupPrivilege Back up
Gerald (Jerry) Carter wrote:
Connecting to 192.168.100.111 at port 445
cli_nt_setup_creds: auth2 challenge failed NT_STATUS_ACCESS_DENIED
just_change_the_password: unable to setup creds
(NT_STATUS_ACCESS_DENIED)!
No. Would have to be something different. Can you give me
some more
Thomas Bork wrote:
Connecting to 192.168.100.111 at port 445
cli_nt_setup_creds: auth2 challenge failed NT_STATUS_ACCESS_DENIED
just_change_the_password: unable to setup creds
(NT_STATUS_ACCESS_DENIED)!
No. Would have to be something different. Can you give me
some more information
Gerald Carter wrote:
You've got Windows 2000 SP4 SR1 installed don't you?
The only current fix is to either set 'client schannel = no'
in smb.conf or to just disable schannel connections
oln the SAMR pipe in nsswitch/winbindd_cm.c.
Is it possible, that with 3.0.20rc1 it is necessarily to set
Gerald (Jerry) Carter schrieb:
smbd version 3.0.20pre2 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
upgrade_to_version_5: normalizing printer keys
[...]
smbd version 3.0.20rc1 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
upgrade_to_version_4:
Gerald (Jerry) Carter wrote:
This is a release candidate of the 3.0.20 code base and
[...]
The release notes are available online at:
http://www.samba.org/samba/ftp/pre/WHATSNEW-3-0-20rc1.txt
http://www.samba.org/samba/ftp/rc/WHATSNEW-3-0-20rc1.txt
Gerald (Jerry) Carter wrote:
This is a release candidate of the 3.0.20 code base and
Is this ok?:
[2005/07/17 21:32:10, 0] smbd/server.c:main(802)
smbd version 3.0.20pre2 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2005/07/17 21:32:10, 0]
Gerald (Jerry) Carter wrote:
Could you swend me your smb.conf? This would be my fault.
We started normalizing the share names in the tdb. But
I didn't do a tdb version upgrade whuich I should have.
If you are normalizing the share names in the tdb due an upgrade from
3.0.15pre2 to
Rainer Link wrote:
Compiling global/vscan-fileaccesslog.c with -fPIC
global/vscan-fileaccesslog.c: In function `lrufiles_add':
global/vscan-fileaccesslog.c:131: error: syntax error at '#' token
global/vscan-fileaccesslog.c:131: error: syntax error before
DONT_USE_CPLUSPLUS_RESERVED_NAMES
Rainer Link wrote:
global/vscan-fileaccesslog.c:131: error: syntax error before
DONT_USE_CPLUSPLUS_RESERVED_NAMES
Interesting, I cannot see this message here.
Hum, which gcc are you using? :-)
An really old one:
vmeis # gcc -v
Reading specs from
John H Terpstra schrieb:
Samba version 3.0.14 is quite good. It has a known problem with setting up
interdomain trusts that will be fixed in the next update. Other than that
3.0.14 passes muster very nicely in all testing I have done.
The same here, with one problem (till today):
smbwebclient
Paul Gienger wrote:
The same here, with one problem (till today):
smbwebclient isn't working correct anymore. Think this is the result
of the changes to smbclient between samba 3.0.11 and 3.0.14.
http://smbwebclient.sourceforge.net/2005/03/version-28.html#comments
Note the release notes for
Masopust Christian wrote:
i'm sending some messages via smbclient -M user from my
solaris-system to my windows-pc and this fails now since i installed
3.0.12 (it also does with 3.0.13).
comparing the debug-output of 3.0.11 and 3.0.12 shows that it now tries
to open a connection to port 445 instead
Gerald (Jerry) Carter wrote:
| If specifying explicit port 139, the message will be
| sent with 3.0.13. Client is a W2K SP4 with active NetBIOS over
| TCP/IP and without firewall.
ok. That's good information to know. I'll get this fixed.
I think it has something to do with the following change
Thomas Bork wrote:
I think it has something to do with the following change in client.c
from Revision 5542 - 5545. But my understanding of C is not good enough:
Tried to patch it. Sending message is possible now, don't know, if it
will break anything else:
--- /usr/src/samba-3.0.13/source
Gerald (Jerry) Carter schrieb:
This is the latest stable release of Samba. This is the version
that production Samba servers should be running for all current
bug-fixes. Please read the following important changes in this
release.
Common bugs fixed in 3.0.13 include:
After 3.0.11 sending messages
Gerald (Jerry) Carter schrieb:
This is a release candidate of the Samba 3.0.12 code base and is
provided for testing only. While close to the final stable release,
this snapshot is *not* intended for production servers. If all
goes well, this this version (or something very similar) will become
Gerald (Jerry) Carter wrote:
| Light testing here appears to indicate that it has fixed the
| bug of ever-increasing number of documents appearing
| in Printer job windows.
kewl. Thanks for the feedback.
I'm waiting for one last feedback about this. Hopefully it will come
this week.
If it is
Hallo @all,
since 3.0.10 parameter min password lenght is deprecated. If removing
the entry from smb.conf, the default of min password lenght = 5 is
used. smbpasswd uses this entry if creating or changing passwords.
How can I set a min password lenght of 2 characters without the
deprecated
Gerald (Jerry) Carter wrote:
| How can I set a min password lenght of 2 characters
| without the deprecated parameter when the passdb
| backend is smbpasswd? Think min password lenght will
| be removed in the next releases.
It's an account policy. Use pdbedit to set the value.
That's why the
Gerald (Jerry) Carter wrote:
Due to the varied responses that we received with the 'phantom jobs
in the windows print queue listing' bug, I'm encouraging people
to test 3.0.11pre2 and let me know if you still see the bug after
ensuring that the $(lockdir)/printing/*tdb files have been removed.
The
Gerald (Jerry) Carter wrote:
Yes. I know. I'm still working on that log file. But I
have to finish up one more file on the privilege support for
3.0.11. All I said is that some people are reporting success
with the current 3.0 code in svn. Not everyone obviously.
Maybe the error has
Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Taylor, Marc wrote:
| Has there been any further progress on the finished
| print jobs piling up issue? In the last few emails
| there was mention of a fix by Monday.
|
| Any updates would be greatly appreciated.
I've got
Gerald (Jerry) Carter wrote:
| printing/printing.c: In function `print_cache_expired':
| printing/printing.c:1038: warning: passing arg 3 of `tdb_fetch_uint32'
| from incompatible pointer type
|
| Could this be a problem?
I don't think so. The warning is from a cast of time_t* to uint32*.
I'll
Thomas Bork wrote:
I think, I have a log from the error. Please see the pid 21540 doesn't
exist - deleting messages record messages.
[...]
[2005/01/10 11:00:01, 4] printing/printing.c:print_cache_expired(1028)
print_cache_expired: cache expired for queue hpclj450 (last_qscan_time
= 1105351088
Thomas Bork wrote:
I had two installations with old printjobs not deleting after printing
with 3.0.10 with printing patch.
After updating to 3.0.11pre1 one of these installations still have this
problems but not in the same manner. It is necessarily to update the
windows status monitor with F5
Gerald Carter wrote:
This is a preview release of the Samba 3.0.11 code base and
is provided for testing only. This release is *not* intended
for production servers. However, there have been several bug
fixes since 3.0.10 that we feel are important to make available
to the Samba community for
Hi Jerry, hi @all,
some users with 3.0.10 with printing patch have problems with old printjobs in
her status monitor in windows. Loglevel 10 shows two problems:
1. The devmode for this printer was not set properly (I know, thiswill cause
problems).
log.smbd:
[2005/01/05 14:02:09, 8]
Hi Jerry,
| some users with 3.0.10 with printing patch have problems
| with old printjobs in her status monitor in windows. Loglevel 10
| shows two problems:
I'm still working on this. The two errors you mention are
unrelated though. The last one might be related now that
I think of it.
Gerald (Jerry) Carter schrieb:
| A question to the thread 3.0.9 and macro %f
|
| http://marc.theaimsgroup.com/?l=sambam=110260704009010w=2
|
| Do you have a patch for that?
Not fixed yet. Is tehre a bugzilla number for it ?
Just so I don't forget.
no. You wrote on 2004-12-09:
ok.
Gerald Carter schrieb:
This is the latest stable release of Samba. This is the version
that production Samba servers should be running for all current
bug-fixes. This is primarily a security release to address
CAN-2004-1154.
Compiles ok with changed configure and printing-3-0-10.patch :)
A
[EMAIL PROTECTED] schrieb:
found a thread with almost my current problem. There wasn't any solution
out there.
Maybe anything has changed?
I want install samba v3.0.9 on an old rh linux v7.1. Currently there's no
chance to
update the core system. But while compiling it breaks with many
Gerald (Jerry) Carter schrieb:
| Subject: message from __2___
ok. reproduced it. The problem is that the string handling
in smbd/message.c assumes unicode strings rather than checking
the negotiated capability bits. The message command you list
works fine for messages from Windows
Gerald (Jerry) Carter schrieb:
| samba 3.0.9 cannot expand %f anymore:
|
| Sending a netbios message to the samba server himself
|
| test2 # echo test | /usr/bin/smbclient -U 'eisfair Samba Server on
| TEST2' -M TEST2 -I 192.168.0.6
| Connected. Type your message, ending it with a Control-D
| sent
Hi,
samba 3.0.9 cannot expand %f anymore:
Sending a netbios message to the samba server himself
test2 # echo test | /usr/bin/smbclient -U 'eisfair Samba Server on
TEST2' -M TEST2 -I 192.168.0.6
Connected. Type your message, ending it with a Control-D
sent 6 bytes
From smb.conf:
message command =
Gerald (Jerry) Carter schrieb:
Thanks to Martin and Walter for pointing out that this
is an old XP bug.
Here's the link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;329234
this bug is fixed in XP SP2 and not the same as in slow printing from
xp sp2 clients.
Unless someone can provide
1 - 100 of 193 matches
Mail list logo
