Re: [Samba] had 3 kernel panics since upgrade from 3.0.21a to 3.0.25 and 3.0.25a on CentOS 4.4
Urs Rau wrote: > Any clever ideas? I will explore the redhat kernel list and see if there > is a newer one maybe one from CentOS 4.5? > Should have spent some more time on this, in the first place. I have found an entry in the redhat bugzilla, that looks like it might fit. There are two entries in redhat bugzilla for rhel 4 error "kernel BUG at mm/prio_tree.c" https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185472 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=173981 Bug 173981 was closed with an ERRATA issued in mid 2006 which upgrades the kernel up to 2.6.9-34.EL (we are still at 2.6.9-22.0.1) http://rhn.redhat.com/errata/RHSA-2006-0132.html I have now temporarily upgraded our kernel to the latest centos 4.5 one 2.6.9-55.EL. We will monitor this and report back, hopefully the crashes are really a kernel bug and not a samba bug and will now have been fixed by this upgrade. Sorry, but it seemed to point in the direction of smbd, at least at first glance. Will be keeping you posted if this changes again. -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] had 3 kernel panics since upgrade from 3.0.21a to 3.0.25 and 3.0.25a on CentOS 4.4
+0x7e/0xaf Jun 15 17:26:36 uk kernel: [] syscall_call+0x7/0xb Jun 15 17:26:36 uk kernel: Code: c3 39 ca 74 08 0f 0b 0f 02 64 4e 2e c0 8b 43 08 2b 43 04 c1 e8 0c 8d 54 02 ff 8b 46 08 2b 46 04 c1 e8 0c 8d 44 01 ff 39 c2 74 08 <0f> 0b 10 02 64 4e 2e c0 c7 43 34 00 00 00 00 83 7e 34 00 c7 43 Jun 15 17:26:36 uk kernel: <0>Fatal exception: panic in 5 seconds Am I reading this right? The Process involved on each of these kernel panics is "Process smbd"? Jun 9 10:58:28 uk kernel: Process smbd (pid: 21513, threadinfo=db80e000 task=c269eef0) Jun 14 16:32:23 uk kernel: Process smbd (pid: 17852, threadinfo=cb136000 task=d22a85b0) Jun 15 17:26:36 uk kernel: Process smbd (pid: 12530, threadinfo=c4093000 task=f72bf1f0) I am sorry if I point the finger at the wrong thing here. But it seems strange that a server starts kernel panicking in this 'consistent' way always showing the same process 'smbd' involved and combined with the fact that the samba rpm upgrade is the only thing that recently changed on this server. Or is the fault really a kernel bug as the log file entry suggests with "kernel BUG at mm/prio_tree.c:528!" Jun 9 10:58:28 uk kernel: kernel BUG at mm/prio_tree.c:528! Jun 9 10:58:28 uk kernel: invalid operand: [#1] Jun 9 10:58:28 uk kernel: SMP Jun 14 16:32:23 uk kernel: kernel BUG at mm/prio_tree.c:528! Jun 14 16:32:23 uk kernel: invalid operand: [#1] Jun 14 16:32:23 uk kernel: SMP Jun 15 17:26:36 uk kernel: kernel BUG at mm/prio_tree.c:528! Jun 15 17:26:36 uk kernel: invalid operand: [#1] Jun 15 17:26:36 uk kernel: SMP Any clever ideas? I will explore the redhat kernel list and see if there is a newer one maybe one from CentOS 4.5? Google gives me a number of hits dating back many months where the kernel BUG "kernel BUG at mm/prio_tree.c:528!" has been triggered with a variety of processes (some smbds - but also a few others) Many thanks for any pointers. Would be really great if I could tell people Monday morning when they come back to work, that we have found the culprit, or better that we have managed to fix it even. There is to hopeing. Regards, -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] changing DOMAIN name on samba PDC
For historic reasons we have a DOMAIN name of 'WORKGROUP' on our one server only samba PDC. Now that we have upgradced to 3.0.25 We would like to change this to something more sensible, but are concerned what the consequences will be for the Win XP Pro workstations that are currently joined to this domain. which of the following scenarios will we likely face after the change? scenario #1 (wishful thinking) we only change the domain name on the one pdc of the domain and on next login of a win xp pro workstation it will automagically learn that the sid of it's domain now 'translates' to a new name and will show this new domain name in places where it used to say the old name 'WORKGROUP' in the past. scenario #2 the right sequence of getlocalsid and setlocalsid before and after the domain change on the samba pdc, can allow us to 'cheat' and the workstations can be 'tricked' into preserving the domain trust relationships and won't need to leave the domain and be re-joined after the renaming of the domain? scenario #3 all workstations have to leave the old DOMAIN (does this have to be done before the rename?). and after the renaming of the main PDC we'll have to rejoin all windows xp pro workstations to the newly named domain? scenario #4 any other suggestions or hints on how to best do this, with the least impact and downtime and admin work coming our way? Many thanks in advance for any help or pointers on this. -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] howto "upgrade/transfer" samba domain-user + domain-group data to a new windows 2003 active directory domain?
Thanks Michael, On 12/6/06, Michael Schurter <[EMAIL PROTECTED]> wrote: Urs Rau wrote: > We have two basic needs that demand we now introduce active directory > servers to our previously 'windows server free' office. One we want to > manage the windows xp sp2 desktops using group policies and secondly > we have a need to start using shared calendaring. > > Alternatively, I would also welcome any suggestions that would allow > us to use microsoft outlook shared calendaring and enable us to manage > the windows xp workstations using group policies, using any other > configuration, preferably open source of course. ;-) Group Policy Management in Samba: http://samba.org/samba/docs/man/Samba-HOWTO-Collection/PolicyMgmt.html Not sure if I am missing the trees for the forrest but to me that page seems to support my conclusion. That if I want to use Group Policy features with Samba I _do need_ active directory. I could try to use the older NT4 style System Policies but that is not what I am after, I am after using the _Group_ Policy features that only come with using active directory? Or did I miss something? -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] howto "upgrade/transfer" samba domain-user + domain-group data to a new windows 2003 active directory domain?
I much regret in many ways having to ask this question below. But our business needs now demand more than we think we can deliver using open source software exclusively. What is the best way to 'suck up' all of the domain group and user data from a current samba 3.0.21a PDC into a microsoft windows 2003 server? We have two basic needs that demand we now introduce active directory servers to our previously 'windows server free' office. One we want to manage the windows xp sp2 desktops using group policies and secondly we have a need to start using shared calendaring. Alternatively, I would also welcome any suggestions that would allow us to use microsoft outlook shared calendaring and enable us to manage the windows xp workstations using group policies, using any other configuration, preferably open source of course. ;-) Many thanks in advance for any hints or suggestions. PS: Please note there is _no_ active directory already deployed. All of the user and group info is currently on our samba 3.0.21a PDC running on a CentOs 4.x box. -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] can a combination of samba 4 tp4 server set as AD controiller with a samba 3.x BDC(slave) emulate a MS AD infrastructure ' well enough' right now?
Looking at the warnings about not running samba 4 (tp3) in a working environment, because of the missing file printing features make me wonder if one could get away with only using the AD controller features of samba 4 for now and have a samba 3.x DC, that has joined the samba 4 controlled Active Directory domain, handle the file and print sharing. How much of an issue would the missing samba4 (tp3) ACLs functionality and other registry type functions likely be for running such an 'emulated MS' Active Directory domain all under the top-level control of a samba 4 (tp4) AD server? Would this be a thinkable thought to have some of the benefits of an AD domain 'right now', and allowing us to wait for samba4 to be completed and then do it properly as opposed to being forced to introduce MS Servers running AD at the top-level right now, and then likely never getting a chance to switch back to using open source software exclusively as our NOS? Has anyone already tried this? Or is there a project out there that works on this sort of samba 4 AD now, as oppsed to waiting for the whole of samba 4 to be production ready? -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] net view \\machine\Admin$ fails with "_net_sam_logon: creds_server_step failed. Rejecting auth request from client ..." on the samba pdc side
I am running my self compiled samba 3.0.21a PDC on centos 4.1. My Admin shares seem inaccessible across the network. When I do a "net view \\it-015\C$", or exactly same error for \\it-015\Admin$ or \\it-015\IPC$ shares, I get an error as follows on the win xp pro sp2 machine IT-010: System error 123 has occurred. The filename, directory name, or volume label syntax is incorrect. And each time I do this the samba server logs "_net_sam_logon: creds_server_step failed. Rejecting auth request from client IT-015 machine account IT-015$" The IT-015 as well as my own, IT-010, machines were successfully joined to the domain, and netdom on the two win xp pro machines also confirms that the machines are properly part of the domain. C:\>netdom /verify it-10 /Domain:MYDOMAIN /UserO:sysadmin /PasswordO:* Type the password associated with the object user: The secure channel from IT-10 to the domain MYDOMAIN has been verified. The connection is with the machine \\MYPDC. The command completed successfully. C:\>netdom /reset it-10 /Domain:MYDOMAIN /UserO:sysadmin /PasswordO:* Type the password associated with the object user: The secure channel from IT-10 to the domain MYDOMAIN has been reset. The connection is with the machine \\MYPDC. The command completed successfully. Any ideas how I can fix my samba PDC so it also thinks my machines are part of the domain, not just the machines themselves? Thanks in advance. -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] what samba file do I need to change when manually changing gid in /etc/group file?
Sorry for appearing to answer my own post. I just thought I might not have given enough detail. Urs Rau wrote: > I have a need to renumber some of my /etc/group numbers from below 100 > to a value that is above 500. (e.g 88 -> 535, 91 -> 632, etc etc, about > 9 changes in total) > > If I had to do this in an earlier version of samba then I think the > correct files I would have to keep in sync would be /etc/group and > /etc/samba/smbpasswd, simply changing the gid from the value below 100 > to it's new value above 500. And then of course run a script that does > those changes for all directories and files owned by that old low > numbered group against the filesystem. > > But now that I am using samba samba-3.0.14a-2 it looks as if this > version no longer stores the gid in the /etc/samba/smbpasswd file, as this > file is > now empty. Does samba now build the group sid dynamically from the > values in /etc/group, or do I have to tell samba somehow, somewhere that > the gid value for the low numbered gid is now such and such higher > numbered value? Maybe the answer depends on how I am running samba on this machine? Well it is a PDC of a domain with name 'WORKGROUP'. Here are hopefully the relevant lines from the testparm output. # Global parameters [global] dos charset = CP850 unix charset = UTF-8 display charset = LOCALE workgroup = WORKGROUP realm = netbios name = LINUX netbios aliases = netbios scope = server string = "" interfaces = 10.37.1.200/24, 10.37.2.200/24, lo bind interfaces only = Yes security = USER auth methods = encrypt passwords = Yes update encrypted = No client schannel = Auto server schannel = Auto allow trusted domains = Yes hosts equiv = min password length = 5 map to guest = Never null passwords = No obey pam restrictions = No password server = * smb passwd file = /etc/samba/smbpasswd private dir = /etc/samba passdb backend = tdbsam algorithmic rid base = 1000 root directory = guest account = nobody enable privileges = Yes pam password change = No passwd program = /usr/local/sbin/sysadm-samba.pl --changepw=%u passwd chat = *new*password* %n\n *changed* passwd chat debug = No passwd chat timeout = 2 check password script = username map = password level = 0 username level = 0 unix password sync = Yes restrict anonymous = 0 lanman auth = Yes ntlm auth = Yes client NTLMv2 auth = No client lanman auth = Yes client plaintext auth = Yes preload modules = use kerberos keytab = No log level = 1 syslog = 1 syslog only = No log file = max log size = 5000 debug timestamp = Yes debug hires timestamp = No debug pid = No debug uid = No smb ports = 139 445 large readwrite = Yes max protocol = NT1 min protocol = CORE read bmpx = No read raw = No write raw = Yes disable netbios = No acl compatibility = defer sharing violations = Yes nt pipe support = Yes nt status support = Yes announce version = 4.9 announce as = NT max mux = 50 max xmit = 16644 name resolve order = lmhosts hosts wins bcast max ttl = 259200 max wins ttl = 518400 min wins ttl = 21600 time server = Yes unix extensions = Yes use spnego = Yes client signing = auto server signing = No client use spnego = Yes change notify timeout = 60 deadtime = 0 getwd cache = Yes keepalive = 300 kernel change notify = Yes lpq cache time = 60 max smbd processes = 0 paranoid server security = Yes max disk size = 0 max open files = 1 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 use mmap = Yes hostname lookups = No name cache timeout = 660 load printers = Yes printcap cache time = 0 printcap name = cups cups server = disable spoolss = No enumports command = /usr/local/bin/samba_enumports.sh addprinter command = deleteprinter command = show add printer wizard = Yes os2 driver map = mangling method = hash2 mangle prefix = 1 stat cache = Yes machine password timeout = 604800 add user script = delete user script = add group script = delete group script = add user to group script = delete user from gro
[Samba] what samba file do I need to change when manually changing gid in /etc/group file?
I have a need to renumber some of my /etc/group numbers from below 100 to a value that is above 500. (e.g 88 -> 535, 91 -> 632, etc etc, about 9 changes in total) If I had to do this in an earlier version of samba then I think the correct files I would have to keep in sync would be /etc/group and /etc/samba/smbpasswd, simply changing the gid from the value below 100 to it's new value above 500. And then of course run a script that does those changes for all directories and files owned by that old low numbered group against the filesystem. But now that I am using samba samba-3.0.14a-2 it looks as if this version no longer stores the gid in the smbpasswd file, as this file is now empty. Does samba now build the group sid dynamically from the values in /etc/group, or do I have to tell samba somehow, somewhere that the gid value for the low numbered gid is now such and such higher numbered value? And while I am asking these questions, does anybody have such a group number id migration script handy? Thanks for any pointers. Regards, -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] allowing windows xp local service with systems accounts rights to access samba share
I am trying to use 'wpkg' omn win xp sp2 machine, a windows package installer service, to access shares on my domain server. 'Wpkg' is running as a local service on a windows xp box that is joined to a domain, and I would like this local 'wpkg' service that is running with local systems rights to access files on a samba domain share. I have played with a number of options including allowing guest access but none of it seems successfull. It seems to either not accept the username and password pair, although they are valid, or else complained about not it not allowing multiple user connections to the same server. What would I have to add in the share definition on the samba primary domain server that would allow all windows xp sp2 workstations in the domain that are running this service access to the share (if possible - concurrently to a limited user account actually running the network login script) Thanks for any hints with this. -- Urs Rau Head of Operations Operation Mobilisation UK National Office Tel: +44-1691-773388 The Quinta, Weston Rhyn Fax: +44-1691-778378 Oswestry, Shropshire, SY10 7LT E-mail: [EMAIL PROTECTED] United Kingdom http://www.uk.om.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 3.0.14a migrating from tdbsam -> ldapsam
This is probably one of those really obvious ones. I have been searching the different samba and openldap docs and howtos in the hope to find some report of somebody that has "migrated" from samba 3.x running with the tdbsam passdb backend over to having everything in in ldap backend using ldapsam. But it seems as if the only documented scenario is migrating from nt4 to samba 2.x/3.x, surely that is not true and I am jsut missing the trees for the forrest? Would some kind soul point me to the right documentation for this, please. Regards, -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 3.0.13 - word cannot complete the save due to a file permission error. for smb/NFS mounted dirs
I am using 3.0.13 and have temporarily run out of disk space on the main samba server, so I have NFS mounted some space from another machine. into a directory that is accessible under samba. When I try to save directly from ms word 2003 sp1 (and same from word 2000) it tells me: on the win98se and win xp pro sp2 clients: "Microsoft Office Word" Word cannot complete the save due to a file permission error. (I:\transfer\ursr\chidren\2005.doc) and on the server it logs [2005/04/11 11:03:06, 0] locking/posix.c:posix_fcntl_lock(659) on 32 bit NFS mounted file systems. [2005/04/11 11:03:07, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING: lock request at offset 2147483538, length 1 returned [2005/04/11 11:03:07, 0] locking/posix.c:posix_fcntl_lock(658) an No locks available error. This can happen when using 64 bit lock offsets [2005/04/11 11:03:07, 0] locking/posix.c:posix_fcntl_lock(659) on 32 bit NFS mounted file systems. Now, this does sound a bit as if this was/is expected to go wrong. But if I save my document locally and then copy it with the same name and to the same dir on the server there is no issue. Is there anything I can do from the samba server to avoid this error? As from a unix perspective there is no permissions problem. Many thanks for any help or pointers with this. If a log with a higher debug would help let me know. Regards, PS: The nfs part is kernel: Linux 2.6.8-1.521.1omsmp #1 SMP Mon Sep 13 18:41:51 EDT 2004 i686 athlon i386 GNU/Linux and nfs-utils-1.0.6-22 -- Urs Rau Head of Operations Operation Mobilisation UK National Office -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: apologies for duplicate posts - btw what's the real diff between gmane.network.samba.general and mailing.unix.samba?
Urs Rau wrote: So I went to check the samba.org archives and found that my messages had not made it to the official mailing list nor to the email archives. That's when I started resending the relevant messages from the past few days but this time to "gmane.network.samba.general". So if some have seen my posts more than once, I am sorry, but at least I corrected my spelling in the second postings and did not resend the level 10 log of 2.4MB. ;-) OK, the messages were silently dropped because I had a "Reply-To:" header in my newsposts. ;-) -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Problem with pdf printing (SOLVED)
Luca, Luca Olivetti wrote: Vincent Mikalinis wrote: Hi all, Has anyone figured out why some people are not having a problem with similar configurations, however some people require that we add the "lpq command = /bin/true" line? It is a very good and simple solution. Should all pdf printers be set with this option for future reference? I don't know, but I bypassed the problem by using a pdf backend in cups (which is really a simple shell script that I tailored to my needs), so even the pdf printer is a "normal" cups printer. Somebody called "misty" said the same thing in IRC #samba yesterday, but they had to run before they could show me the contents of the file. Would you mind sending this to the list? I think it is still at least slighlty "on-topic". The person on IRC said they then have another cron job that goes and emails the so created pdf every 5 minutes to the users that created them. For one situation here that would be THE ideal solution. So if misty or anybody else that happens to have the same solution wouldn't mind emailing me the details for that, that would be really appreciated. Regards, Urs Rau Bye -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] "logon path" and "logon home" settings return different values in 3.0.13?
When exactly did the samba meaning/returns for "logon path" and "logon home" change? (at which version?) We used to have a system that appeared to be working well and it was as follows logon script = logon.bat logon path = \\%L\profiles\%U logon drive = h: logon home = \\%L\%U\.profile domain logons = Yes and the [profiles] share had the following [profiles] comment = User Profiles path = /usr/local/samba/profiles profile acls = Yes root preexec = PROFILE=/usr/local/samba/profiles/%u; if [ ! -e $PROFILE ]; then mkdir -pm700 $PROFILE; chown %u.%g $PROFILE;fi this gave all users a h: (for homes) regardless whether they were on win9x or xp and their win98 profile was under h:\.profile and h: was mapped to \\server\homes and their xp machines still mapped h: to \\server\homes but the profiles were safely tucked away under \\server\profiles\%U, away from users harm. But now on 3.0.13 I noticed that the xp workstations h: drive now get's mapped to \\server\homes\.profile, XP is now reading the "logon home" dir, why? why is xp "suddenly" picking up what used to be used by the win9x machines? I am sure there is a good writeup somewhere that explains how I set my profiles up now. The smb.conf man page has warnings about not using %U in the "logon path" but how else do I get my old functionality back? I would like to have the following effect (on both win98 and xp clients) 1. the user having a h:drive that get's mapped against his unix home dir 2. and xp can handle the profile being "somewhere" else and we don't want a drive mapping for it (but how do we now set this up so we don't run foul of the xp habit of keeping connections open even after a user has logged out? 3. and for the win98 we want the profile to be in a "safer" dir and would be quite happy for that to continue to be the ".profile" subdir under the users win98 and unix home dir What would I have to do with my "logon home", "logon path" and "logon drive" ? Any help with this would be greatly appreciated. Regards, Urs Rau PS: I guess our current setup would explain why samba sometimes said a user was still logged in and using files when they were not? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Windows XP & greyed-out Guest user password prompt
Jules Agee wrote: (replying to self) Jules Agee wrote: Hi, we've been using Samba for a while, and are just now starting to switch our desktop computers to Windows XP. We are having a problem where connections to our Samba server fail, and the user is presented with a password prompt asking for a password for user Guest. They can't select a different user. From what I have seen is that samba often doesn't allow you to change the username if it already has even just one single smb connection to the samba server. And there are a number of reports of win xp (in particular) caching some info about connections to a server. In order to find your problem you could try doing: net use * /del followed by a net use to double check that all network connections are gone. Your description sounds as if samba already has that workstation as being "connected" as the user "guest" (maybe?) and now only needs the credentials for the guest account to allow access. The other way would be to query the server as to what user it thinks is connected to the "updates" share at the time of the error. HTH Urs Rau Sorry, forgot to mention that we're running Samba 3.0.7 on Debian GNU/Linux -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Very HUGE binaries!?
Hansjörg Maurer wrote: Hi I have tried this patch, but the generated Makefile still contains the -g CFFLAG. (running Solaris8 with gcc) Removing the -g manually from the Makefile works. Did you run the source/autogen.sh script after you applied the patch? quote from patch: http://samba.org/~jerry/patches/post-3.0.13/configure_debug.patch ## ## Prevent debug binaries from being built by default ## Make sure to run source/autogen.sh after applying this patch. ## Index: source/configure.in === --- source/configure.in (revision 6060) +++ source/configure.in (revision 6062) Regards, -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Samba or Cups-Problem ?
Stefan-Michael, Stefan-Michael. Guenther (in-put GbR) wrote: Hi, I'm using some kind of pseudo printer on our samba server to automatically produce PDF files. The smb.conf looks like this (the samba server is successfully conteced to an ADS): [global] workgroup = ADS netbios name = pc103.ads.local realm = ADS.LOCAL security = ADS password server = win2ksrv.ads.local log level = 2 winbind separator = + template homedir = /home/%U idmap uid = 1-2 idmap gid = 1-2 winbind enum users = yes winbind enum groups = yes winbind enable local accounts = yes template shell = /bin/bash log file = /var/log/samba/log.smb.%U max log size = 500 printing = cups printcap name = cups cups options = raw The samba HowTo in chapter 20 says ( emphasis mine): "ldd `which smbd` libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000) libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000) libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) [] The line libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) shows there is CUPS support compiled into this version of Samba. If this is the case, and printing = cups is set, then any otherwise manually set print command in smb.conf is ignored. This is an important point to remember! ^^ Tip Should it be necessary, for any reason, to set your own print commands, you can do this by setting printing = sysv. However, you will lose all the benefits of tight CUPS/Samba integration. When you do this you must manually configure the printing system commands (most important: print command; other commands are lppause command, lpresume command, lpq command, lprm command, queuepause command and queue resume command)." So what you need is [pdfprinter] comment = Minolta Color PageWorks/Pro Ps printing = bsd path = /samba/pdfprinter print command = /samba/pdfprinter/pdfscript "%s" printable = yes public = yes writeable = yes and you'll also need a lpq command=/bin/true otherwise your printer is going to show offline and jobs won't clear from the queue on the clients. HTH, Regards, Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 3.0.13 why is "lpq command=%p" showing with testparm -v ?
the docs say that all lp commands are ignored if one has printing =cups printcap name=cups in the global section and cups support is compiled in. ldd `which smbd` says I do have cups compiled in and my global section does have the two cups lines. But on 3.0.13 I get testparm -s | grep lp returns no output BUT testparm -s -v | grep lp returns lpq cache time = 30 lpq command = %p lprm command = lppause command = lpresume command = I understand that if I do testparm -v this also shows me the built-in defaults. Why does it only show %p for the lpq command and nothing else for the other lp commands? Regards, Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Problem with pdf printing
Vincent, Vincent Mikalinis wrote: Hello, I'm hoping someone can help me. I have several pdf printers set up and when I print to them samba becomes unstable and several errors are dumped to the log. These pdf printers were working when I was using version 3.0.6. When I went to a newer version of samba the queue would not clear on the windows side and no errors were logged. Yesterday I upgraded to version 3.0.13-1 and the errors started and the queue still will not clear. I have a very similar problem with my pdf printers. I have the following in my [global] section. printcap name = cups printing = cups cups options = "raw" and my pdf printer share now has [pdf] comment=PostScript to PDF Converter printing=bsd public=no guest ok=no create mode=0600 path=/var/tmp printable=yes print command=. /etc/sysconfig/rc.sysadm; \ ulimit -c 0; \ ulimit -S -d $PDF_MEM_LIMIT; \ ps2pdf %s "%H/%J.pdf"; \ chmod 640 "%H/%J.pdf"; \ rm -f %s lppause command= lpresume command= lpq command=lpq -P'%p' lprm command=lprm -P'%p' %j queuepause command= queueresume command= and it now shows the printer as online and the printjobs show up and get removed just as they should. All it took to change the printer status displayed on the windows xp pro workstation from offline to online, was to add a "real" lpq command line, (lpq -P'%p'). Now all looks fine from the workstations viewpoint. BUT on the server I now have repeated entries of cups telling samba that it does not know the printer 'pdf'. Win one, loose one. ;-) level 3 error msg lpq: Unknown destination "pdf"! [2005/03/27 22:20:00, 3] printing/print_generic.c:print_run_command(62) Running the command `lpq -P'pdf'' gave 1 I start to wonder what "dammage" it would do to set lpq to lpq command =/bin/true for my pdf printer? ;-) HTH -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] apologies for duplicate posts - btw what's the real diff between gmane.network.samba.general and mailing.unix.samba?
Sorry to those of you that have received duplicates of my messages over the easter weekend. I had subscribed to the nntp server of my isp (pipex uk) and searched for "samba" it showed a few hits but "gmane.network.samba.general" showed as containing no posts but "mailing.unix.samba" showed a bit more than 20'000 so I subscribed to that and sent a slurr of messages with questions and followups to that newslist over the weekend, and my questions did show up in "mailing.unix.samba". But not having received a single answer by the end of the weekend I thought something was a little strange. So I went to check the samba.org archives and found that my messages had not made it to the official mailing list nor to the email archives. That's when I started resending the relevant messages from the past few days but this time to "gmane.network.samba.general". So if some have seen my posts more than once, I am sorry, but at least I corrected my spelling in the second postings and did not resend the level 10 log of 2.4MB. ;-) What is the purpose or function of newsgroup "mailing.unix.samba"? And is it my ISPs fault that they only offer "mailing.unix.samba" for subscription and not "gmane.network.samba.general" and how do the two lists relate to each other? It would appear that at least some of the posts to "gmane.network.samba.general" do make it to "mailing.unix.samba" but no messages appear to travel the "other way". -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] printers offline in 3.0.13 - is it because they are "local printer"s printing to "local port"s ?
Maybe my printers being offline with samba 3.0.13 on some xp pro workstations is not a bug after all, maybe it was a (mis)feature in samba-2.2? My problem is that I can't easily test on < 3.0.13, because until a few days ago I had been running 2.2.12 and all was fine, then. No printers showed as offlne. But then I upgraded to 3.0.7 for a day or two immediately followed by an upgrade to 3.0.11 and I only held my breadth to check things when I was on 3.0.11 and found that my printers were showing as offline under 3.0.11, but of course maybe that would have been like that even on 3.0.7? We have had 3 good reasons to install samba printers on win xp workstations as "local printer"s printing to "local port"s (e.g. \\linux\printerqueuename) reason 1 our main email application (pegasus mail) was playing very annoying timeout delays with reading emails and going up or down the email inbox if the default printer was a smb network printer that was unreachable at the time. (for some strange reason pegasus was trying to interact with the printer for every msg) reason 2 just when we thought we should point the finger at pegasus mail for this we found that ms word had a similar problem when it came to a workstation having the default printer as a smb network printer and it wasn't accessible. reason 3 if we installed the samba network printers as "local printer"s printing to a "local port" (e.g \\linux\printerqueuename then we could install the printer for all users on that workstation and also set the default config for all of those queues once for all, from a script. (so no need to set the network printer settings and defaults once every login.) BUT maybe we have to throw out those gains and stop using printers defined as "local printer"s printing to "local port"s which are pointed at the samba print queue? Is there a reason why samba changed it's behaviour showing it's printers as being offline if they are accessed in this way? I guess the question to ask is, what status does a win2k3 shared printer show as on a win xp pro workstation if one sets the workstation printer up as a "local printer" with a "local port" of the name "\\sambaservername\printerqueuename". I hope somebody can tell me that such a setup would result in a printer showing the proper status? Because then I am sure samba could be told the same trick, surely? I am hoping one or two of you can shed some light on this. Regards, Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Problems with Excel & MS Word files (still)
Jeremy Allison wrote: On Tue, Mar 29, 2005 at 07:45:53AM -0500, Nathan Vidican wrote: No confirmation over here, havn't had a chance to compile a new copy - rolled back to 3.0.8 for the time being it's been less buggy but still have occasional file(s) locking up. A little unclear here, do I need to add a patch to 3.0.13 before compiling, or simply add 'dos filetime = yes' to the configuration? Lastly, does it matter if I'm not using ACL's? Just using plain old UNIX permissions (750/660 dir/file) and the force-group parameter for most shares - which works quite well thus far. No, you don't need to add a patch. Simply setting dos filetimes should do it. Ohh, I have added the patch you emailed to the newsgroup on 24/3/05, in this thread, I guess I should back that out again in my custom rpm? Or is it a fix that will make it into 3.0.14 anyway? (maybe I am confusing people with my question about my self-rolled samba rpm, where I included your newspost as a patch on top of 3.0.13, sorry) -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Problems with Excel & MS Word files (still)
Jeremy or Nathan, Jeremy Allison wrote: Ok, I have a working theory for this. It concerns ACLs and what happens when excel wants to update the filetime on a file the user doesn't own. Normally you just set the "dos filetime" parameter to allow this (this causes a timestamp to be updated on a file if you can write to it - normally POSIX only allows this if you're the owner). I've realised the codepath here doesn't check ACL semantics. This is a bug we've had since we introduced ACLs a long time ago but only now seems to have been triggered. Here is a patch to the just released 3.0.13 that causes ACL entries to be properly checked when "dos filetime= True" has been set. Please try this on top of 3.0.13 and let me know if it fixes the issues. Has this been confirmed, as fixing it? I am rolling a 3.0.13 maintenance release and it would be nice to clear this excel ACL bug. What is the bugzilla entry for this bug, so I can follow it? Thanks a lot. Regards, -- Urs Rau Head of Operations Operation Mobilisation UK National Office -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Very HUGE binaries!?
Urs Rau wrote: > It would appear that $RPM_OPT_FLAGS is the one that introduces "CFLAGS=-O2 -g -march=i386 -mcpu=i686" > > Any advice on the cleanest way to reduce the size of the binaries and not have them compiled with "-g"? For now I have added an "ugly" 2-liner to the beginning of the %prep and %build sections. (in case rpm builders jump straight to the %build section) # avoid building huge rpms RPM_OPT_FLAGS=`echo $RPM_OPT_FLAGS | sed s/-g//` I know I could have either reset my system wide rpmrc or set my own ~/.rpmrc, but I wanted to make sure that anybody that uses my spec file to rebuild the rpm would also get small binaries and not have to remember to set their own system or personal rpmrc Is this all one can do, it feels like an ugly "hack"? Regards, Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Very HUGE binaries!?
Gerald (Jerry) Carter wrote: > Gerald (Jerry) Carter wrote: > | Toni Verdu Carbo wrote: > | | Hi! > | | > | | I've been compiling Samba 3.0.x on a Solaris 2.6 > | | server using GCC 3.4.1 without any problem until recently... > | | The problem started with 3.0.12 version, and reproduced in 3.0.13. > | | Doing "configure" and then "make" produces with these two > | | versions VERY HUGE binaries! > | > | I've tracked down the change to configure.in that caused this. > | YOu can work around it by either (a) stripping the resulting > | binaries, (b) manually removing '-g' from the Makefile, or > | (c) manually setting CFLAGS to any value before running > | configure. > | > | I'll go ahead and fix this in the SAMBA_3_0 svn tree. > > Fixed in svn now. The patch is at > http://samba.org/~jerry/patches/post-3.0.13/configure_debug.patch > > Thanks for this fix. However on my FC2 I still get huge binaries and as a consequence huge rpms even after running your patch and then running autogen.sh in the rpm building. I have tried inserting "sh autogen.sh" into the samba.spec file instead of "script/mkversion.h" in the %prep stage. Also adding --enable-developer=no to the configure lines in %build was to no avail. It would appear that $RPM_OPT_FLAGS is the one that introduces "CFLAGS=-O2 -g -march=i386 -mcpu=i686", so your patch helps set sane defaults for normal compiles but does not fix the problem for a rpm build. Any advice on the cleanest way to reduce the size of the binaries and not have them compiled with "-g"? Thanks in advance. Regards, Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 3.0.13 winxp pro printers offline and don't come online, but you can print to them (shorter version - no log level 10)
%p' lprm command = lprm -P'%p' %j [printers] comment = All Printers path = /var/spool/samba read only = Yes guest ok = Yes printable = Yes browseable = No [profiles] comment = User Profiles path = /usr/local/samba/profiles profile acls = Yes root preexec = PROFILE=/usr/local/samba/profiles/%u; if [ ! -e PROFILE ]; then mkdir -pm700 $PROFILE; chown %u.%g $PROFILE;fi + and now my level 10 log the xp workstation is Fin-70 the user is kerstinr the domain is called WORKGROUP the first printer that is offline is "copier (pcl)" queue name copier_pcl the second printer that us also offline is "laser (ps)" queue name laser_ps I guess some of the relevant sections are around [2005/03/27 23:07:54, 3] rpc_server/srv_spoolss_nt.c:_spoolss_open_printer_ex(1770) access DENIED for printer open and maybe [2005/03/27 23:07:42, 3] rpc_server/srv_spoolss_nt.c:_spoolss_open_printer_ex(1770) access DENIED for printer open I hope this is an obvious one for you. Regards, Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] can I (re-)share a share of another samba server
What I would like to achieve is having a symlink under a mapped share on my main server (called linux) which would transparently read or write the data stored under that dir across the network to another samba server (called backup). What I have done sofar. I have one main samba server called "linux" that is the PDC and one backup samba server called "backup" that has "security = server" and "password server = linux". What I would like to have is a directory on the users home dirs that is a symlink to their homedir on the backup server What I have tried doing is I mounted the share of the backup server from the smb backup server into the "/mnt/samba/backup/users/" dir and then creating a symlink on linux in the users homedir to the correct place under the "/mnt/samba/backup/users" dir. ( I have made sure that the mount points have adequate permissions.) This almost works as intended. I can now read the data that is coming from the backup servers share, but I cannot write to it. (Is this because "root" has mounted the smb share from backup onto linux?) Is there a way to (re-)mount a smb share in this fashion and share it out again or does each client PC have to create it's own connection to the backup server. Would this better be achieved by using nfs for the connection between linux and the backup server? Thank you for any pointers or help with this. -- Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] how to get logon.bat run with Administrator rights in domain logons?
On win XP Pro workstations it would be so convenient if the domain logon script which is stored on the samba pdc could be made to run with Administrative (or System) privileges. I know that I can interactively run another security context by choosing "run as user" but how could I achieve this non-interactively and domain wide whilst a "limited account" is loggin in? Thanks for any pointers. Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] can Desktop.ini files be made to work on samba shares?
Is it possible to make Desktop.ini files active on samba shares? Ideally I would like to do two things: 1. make certain shares display special icons Desktop.ini: [.ShellClassInfo] IconFile=C:\WINDOWS\system32\SHELL32.dll IconIndex=27 ConfirmFileOp=0 2. have exploratory texts pop-up when users explore certain shares (similar to the messages that pop up when users go to the windows directory. Desktop.ini: [.ShellClassInfo] IconFile=C:\WINDOWS\system32\SHELL32.dll IconIndex=27 ConfirmFileOp=0 InfoTip=this is a warning text Using these files on local folders works jsut fine but on a samba share I can't get it to take effect. Thanks for any help with this. Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] 2.2.8a with kernel-2.4.22 has kernel oplock problems (NOT Failed to setup RT_SIGNAL_LEASE handler)
I have a samba problem on a redhat 9 box that appears to be clearly linked to a new kernel 2.4.22nptl when using "kernel oplocks = yes". I am trying to install a printer driver on a win98se box that tries loading the driver files from a share on the 2.2.8a server. The installation fails as win98se cannot read all the files as it would like to. I have two things I can do to avoid the problem. 1. if I set "kernel oplocks = no" 2. if I go back to the former kernel 2.4.20-19.9 without nptl then the operation does not fail. At first I thought it was just the annoying "Failed to setup RT_SIGNAL_LEASE handler" bug, but then I patched this as follows: --- samba-2.2.7a/source/smbd/oplock_linux.c.orig 2003-06-05 14:40:49.0 -0400 +++ samba-2.2.7a/source/smbd/oplock_linux.c 2003-06-06 13:34:29.0 -0400 @@ -40,7 +40,7 @@ #endif #ifndef RT_SIGNAL_LEASE -#define RT_SIGNAL_LEASE 33 +#define RT_SIGNAL_LEASE (SIGRTMIN+1) #endif #ifndef F_SETSIG --- samba-2.2.7a/source/smbd/notify_kernel.c.orig 2003-06-06 13:33:56.0 -0400 +++ samba-2.2.7a/source/smbd/notify_kernel.c2003-06-06 13:37:44.0 -0400 @@ -39,7 +39,7 @@ #ifndef RT_SIGNAL_NOTIFY -#define RT_SIGNAL_NOTIFY 34 +#define RT_SIGNAL_NOTIFY (SIGRTMIN+2) #endif #ifndef F_SETSIG That did get rid of the "Failed to setup RT_SIGNAL_LEASE handler" messages in the log for both kernels 2.4.20 + 2.4.22 but I still can't install the printer driver files from the samba share when "kernel oplocks = yes". I can't get to the bottom of this. I have a debug level 10 log file for this, would anybody be willing to look into it and tell me what I need to change? Many thanks in advance. Urs Rau Head of IT OM UK Headquarters -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: FW: [Samba] Samba 3.0.0 rpms
Stephen Collier wrote: The error on samba-3.0.0-1.i386.rpm on RH9 $ rpm -Fhv samba-3.0.0-1.i386.rpm warning: samba-3.0.0-1.i386.rpm: V3 DSA signature: NOKEY, key ID 2f87af6f That does not look like a samba or samba packaging problem at all. the redhat 9 release comes with a newer rpm packaging system and in that one it lloks as if rpm has it's own pgp/gpg key database. try importing the key for 2f87af6f into rpm and all should be well. gpg --recv-key 2f87af6f gpg -a --export 0x2f87af6f > /tmp/0x2f87af6f.asc rpm --import /tmp/0x2f87af6f.asc Hope this helps. Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] utility/script -> "Registry.pol" from "*.reg" or "*.ADM" ?
Does anybody have or know of a utility/(perl?)script that creates the w2k/xp AD GPO style "Registry.pol" files from the unix cmd line? The "Registry.pol & gpt.ini" file format is very very simple, "http://msdn.microsoft.com/library/default.asp?url=/library/en-us/policy/policy/registry_policy_file_format.asp"; so somebody must have written it, surely? My proof of concept tests show me that I could do a poor mans ADS only using the builtin (local)gpo service by simply "playing" around with the LGPO files Registry.pol (both for user or machine) and increasing the version number in gpt.ini, during user login or using wmi. And at the end of the update script/cycle do a "gpupdate /force", or possibly live with a reasonable short gpo refresh time. It works and allows me to use many gpo features, save software distribution, which I can do differently anyway. I am thinking of a (unix-side)commandline program that scans a "*.reg" export and creates a corresponding "Registry.pol" file or maybe also runs interactively and scans an "*.ADM" file to create the "Registry.pol" files. At the moment I have to use the win gui "gpedit.msc" (or gpmc.msc) to read the "*.adm" file in order to create the "Registry.pol" file. Any other ideas or pointers or ... greatly appreciated. Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Found RegToAdm util !
Samba admins, I have stumbled across a FREE & interesting utility that allows one to create Policy Templates straight from an registry export "*.reg" (unicode or ansi), thank you Yizhar Hurwitz. http://www.new-ofek.co.il/yizhar/ Hope somebody else finds this usefull too. Urs Rau PS: Now if anybody knows of a unix commandline util/script that creates both User and Machine "Registry.pol" files from either "*.reg" or "*.ADM" files, my day will be very happy. (see seperate email with subject: "utility/script -> "Registry.pol" from "*.reg" or "*.ADM" ?") -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Pseudo-GPO Support for Samba
Jerry Haltom wrote: I have created a GPO similar program specifically for deploying applications to workstations. Similar to how GPO can push software packages. I like to call it wpkg. (dpkg for Windows :) It's very simple, but, very effective, and it works for more than MSI's. Sounds very interesting. I take it you are about to offer it for inspection/download at some point in the near future? Or you are writing up some plan of action on how to write another (more comprehensive/flexible) one? And we are all waiting very patiently. ;-) Good work! Keep it up! Thanks for your efforts. Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] affordable "mid-way compromise" with samba 3.x and M$ ADSserver participation ?
Guys, A simple question from a naive guy ;-). Would it be possible and legal, in terms of M$ software licensing, to use a w2k or higher (2003?) ms win active direcotory server as the main active directory server BUT have all the clients connect to the samba 3.x which runs as a pdc and has joined the ADS domain? And IF this is technically possible would this "avoid" having to get any more licenses than the 5 (is that correct) that come with a fully licensed basic w2k/2003 server? In short is there any mileage in this sort of "affordable mid-way compromise"? Please don't flame me if this is the silliest question you have ever come across. ;-) I am only trying to survive in a seemingly more and more M$ dominated world. BUT am unwilling to fully yield. Many thanks in advance, Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Win XP home
Davide Parise wrote: How can I join a Win XP home edition to a samba domain? It seems it support only workgroups !! Correct. There is a very good write-up at http://samba.vernstok.nl/htmldocs/samba-pdc.html#id2893226 and again at http://samba.vernstok.nl/htmldocs/ProfileMgmt.html#id2991061 Hope this helps understanding the issue. Urs Rau -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] spurious domian login problems
We have a few win9x workstations, that have spurious login problems. They get the message: No domain server was available to validate your password you may not be able to gain access to some network resources. The passwords are definetly correct and the problem will sometimes disappear after 5 - 10 retries, but almost always after a full restart of the win9x PC, very occasionally it takes as many as 5 reboots before it logs in to the domina again. All I can find in the log.nmbd file around that time is a "code = 0x0" returned instead of the usual 0x12 or 0x7. Does this give anybody a clue as to what is going on. Or is looking at log.nmbd a waste of time. I simply can't find an entry that would be relevant in the log.smbd around that time. I am running at loglevel 3 how high should I go to get more details to help debug this problem? successfull logins appear to have either code 0x12 or 0x7 and only the failed logins appear to have code 0x0. [2003/01/11 18:32:20, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 192.168.1.122: code = 0x12 [2003/01/11 17:22:21, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 192.168.1.26: code = 0x7 [2003/01/04 11:51:06, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70) process_logon_packet: Logon from 192.168.1.197: code = 0x0 Any help appreciated. Urs RAU Head of Information Services OM UK HeadQuarters + | Operation Mobilisation, The Quinta, Weston Rhyn, OSWESTRY | | SY10 7lT, UK, FAX: +44-1691-778378, TEL: +44-1691-773388 | | Email: [EMAIL PROTECTED] | +---+ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
