Re: [Samba] Logon Scripts for Mandrake 9.0
From: David Sexton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Fri, 17 Jan 2003 12:16:00 -0500 Subject: [Samba] Logon Scripts for Mandrake 9.0 I was wondering if some one could help me make some basic login scripts and tell me where to place them. I know nothing about them. I am trying to get my windows based mechines to login to my Mandrake 9.0 server This isn't really a samba question, as you can write the login scripts as batch files on a windows machine, and copy them to your samba server. I am sure a google search would turn up a few examples. But most uses for login scripts include mapping shares (net use, see 'net help use' on a windows mahcine) or importing registry settings (regedit /s regfile.reg) or copying files etc. If you need to customise logins scripts per-user, per-machine, per-OS, you may want to try ntlogon, which is in the Mandrake contribs (set yourself up at http://plf.zarb.org/~nanardon if you haven't yet, and you should be able to 'urpmi ntlogon'). Edit the file /etc/ntlogon.conf, it's pretty self-explanatory. Also, uncomment the lines for ntlogon in the netlogon share of the default smb.conf in Mandrake. If you have mangled yours, take a look at: http://ranger.dnsalias.com/mandrake/samba/smb-domain-controller.conf I have windows ME and XP i got ME to login but XP won't. Can some one help That may be a different issue. Firstly, I don't think you can join XP Home to a domain (any domain, NT/2k/samba). Secondly, XP Pro, like NT and 2k requires machine accounts (check that your 'add user script' is setup), and that you join the domain with the root account (unless you are using an LDAP backend on 2.2.x). So, you would need to do 'smbpasswd -a' as root, and when joining the machine use 'root' as the username, and the password you entered for 'smbpasswd -a'. Finally, XP won't connect to a server that doesn't support signing/sealing unless you apply the registry patch, available in the samba-doc package: [bgmilne@bgmilne bgmilne]$ rpm -ql samba-doc |grep -i signorseal /usr/share/doc/samba-doc-2.2.6/docs/Registry/WinXP_SignOrSeal.reg Finally, make sure you have run updates (I have't on this machine as you can see above ...) Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] UNIX/SAMBA file permission interaction
Hi Everyone, Just prior to christmas I asked a question relating to the interaction of SAMBA with UNIX permissions. The answer I got back was to set the sticky bit on the folder in question. I did this and sure enough SAMBA then followed the behaviour I expected. Can any one explain to me why? For those of you baffled, this is what occurs: Without the sticky bit set on a folder that has rwx set for ogw a file can be deleted from within this folder (using Windows Explorer) regardless of whether you are the owner or part of the group that this file belongs to. (as long as rw is set for the owner) If you use an application to modify this same file the application behaves as expected and prohibits you from modifying the file. If you set the sticky bit on the folder, Windows Explorer then behaves as it should (as does the application), and if you are not the owner or part of the group that the file belongs to you can not delete the file. I'm sorry, I must be missing something as this does not make sense. Surely I would have expected SAMBA to adhere to the UNIX permissions without the sticky bit being set on the folder. -- David Beards Technical Manager Networks and Systems CFA 8 Lakeside Drive Burwood East 3151 Ph: 9262 8204 Mobile: 0419 519 366 CAUTION - This message is intended for the use of the individual or entity named above and may contain information that is confidential or privileged. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited and that you must not take any action in reliance on it. If you have received this communication in error, please notify CFA immediately and destroy the original message. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Trusted domains in 3.0
Hello, it appears that interdomain trusts don't work in 3.0alpha, because when I am trying to create a trust to my Samba domain on a W2K domain TRUSTDOMAIN PDC, Samba tries to getpwnam() of TRUSTDOMAIN\Administrator, and if it doesn't exist, samba says that domain TRUSTDOMAIN not found, so adding trust on Win2K fails with message something weird like Wrong parameter given. I tried to create a user TRUSTDOMAIN\Administrator in my LDAP (which getpwnam() asks via NSS), but getpwnam() doesn't find such username. Am I doing something wrong? Any ideas how to make the trust work are appreciated. Best regards, -- Anton Voronin Intersvyaz JSC http://www.chelcom.ru +7 (3512) 655199 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Win95 client can see everyone but linux box
Hi, I'm lucky enough to have samba working fine on SuSE 8.0, sharing a printer with several windows computers. Earlier today I even had my new wireless card working on a Win95 laptop and it could see the whole network, and I wirelessly printed from my living room. COOL. Unfortunately, I screwed it up. The wireless card seems to conflict with the old pcmcia (wired) card and so I uninstalled and reinstalled that card several times in an attempt to make both work at once. (No luck so far.) Somehow this process messed up my wireless printing. Now when clicking on Network Neighborhood the Win95 Client usually at first says the network is unavailable/unreachable and then after a bit more clicking will see the other two windows computers on the network, but not the linux box where the printer is attached. The other two windows computers can see everything in their network neighborhood's, so I don't think the linux box itself is messed up. It must be something about that darn Win95 laptop. And it WAS working earlier. Anyone have a guess at what I screwed up and how I can get it working again? Thanks for any help. (It's actually my wife's laptop and it won't be too good for me to have messed this up!) Brian -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] UNIX/SAMBA file permission interaction
On Sat, Jan 18, 2003 at 10:44:35PM +1100, David Beards wrote: Without the sticky bit set on a folder that has rwx set for ogw a file can be deleted from within this folder (using Windows Explorer) regardless of whether you are the owner or part of the group that this file belongs to. (as long as rw is set for the owner) If you use an application to modify this same file the application behaves as expected and prohibits you from modifying the file. If you set the sticky bit on the folder, Windows Explorer then behaves as it should (as does the application), and if you are not the owner or part of the group that the file belongs to you can not delete the file. I'm sorry, I must be missing something as this does not make sense. Surely I would have expected SAMBA to adhere to the UNIX permissions without the sticky bit being set on the folder. Samba is adhering to the UNIX permissions, that's how directory permissions work. rw on the directory means that you (everyone, in your case) can add/remove directory entries. Deleting a file is nothing more than removing a directory entry, so you can do it because you're modifying the directory and not the file. Setting the sticky bit on a directory changes this behavior to only allow the owner of the file and the owner of the directory to delete the file. If you're curious, the sticky bit used to have another meaning (which is where the name came from). I'm not clear on the details, but it had something to do with keeping an executable's code segment in memory even if there wasn't an instance running. I'm not sure if any current variety of UNIX still implements that behavior, but I think most/all of them do support sticky bits on directories (it's particularly important for /tmp and /var/tmp). -- Michael Heironimus -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing from Win2000 to Linux
I don't understand your print shares. That doesn't mean they are
incorrect, it just means I don't use this method for configuring my
smb.conf.
Here is the easiest way I know.
If you can print fine from the linux box, that means that the linux box can
handle postscript files, since postscript is THE printing language on linux.
Therefore, send all your windows files to the same queue you print from in
linux. And, on the windows box, select HP laserjet III plus as your driver.
This is a generic postscript driver, that is, it will convert your document
into a generic postscript file. This file can be read with gv, for
example. The file is then transferred to the spool directory specified
in your print share, whence it is printed with lpr.
I hate to depend on automatic, behind the scenes tricks to solve my
printing problems, since you will never stop having printing problems and
you might as well understand what is happening.
Here is what I do. I use lprng but cups should not be too different, I would
hope. There are some permissions problems in cups that I haven't seen in
lprng.
[global]
encrypt passwords = yes
netbios name = HAMMER2
interfaces = 192.168.0.2
security = SHARE
guest account = ftp
[ps]
path = /tmp
read only = No
create mask = 0700
guest ok = yes
hosts allow = 192.168.
printable = Yes
printing = lprng
print command = echo %J %p %s/tmp/junkJ;\
a=`echo '%J' | sed s/^.*- //` ;\
echo This is truncated $a /tmp/junkJ;\
/usr/bin/lpr -Pps -J$a %s;\
rm %s
lpq command = /usr/bin/lpq -Pps
lprm command = /usr/bin/lprm -Pps %j
lppause command = /usr/sbin/lpc hold ps %j
lpresume command = /usr/sbin/lpc release ps %j
share modes = No
use client driver = yes
I explicitly define all the printing commands. Just paranoid,
I guess. It really isn't needed, if everything is working according to
plan. Note: printing = parameter is a share level parameter.
man smb.conf
:/ printing
I don't think share modes does anything but I am too lazy to find out.
Just be sure the ps queue can handle postscript jobs, and you should be
close to a solution.
I won't give you my printcap file, since I use lprng and that might have
a different format from cups, for all I know.
Joel
So, On Sat, Jan 18, 2003 at 09:37:56AM +0100, Michael Herber wrote:
I have two computers here - one with Win2000 and the other with SuSE
8.1. My goal is that I can print from Win to my printer connected on the
Linux machine.
Now I tried quite a few things but nothing will work. First of all, here
my smb.conf:
# Samba config file created using SWAT
# from 0.0.0.0 (0.0.0.0)
# Date: 2003/01/11 16:17:19
# Global parameters
[global]
security = share
guest account = nobody
guest ok = Yes
printing = cups
printer name = lp
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
load printers = Yes
[homes]
comment = Home Directories
valid users = %S
read only = Yes
guest ok = No
veto files =
browseable = No
fstype = FAT
[printers]
comment = All Printers
browseable = yes
public = yes
guest ok = yes
writable = yes
printable = yes
path = /var/spool/samba
[print$]
comment = Printer Drivers
browsable = yes
guest ok = yes
read only = yes
I know that there are two possibilities to install the printer on the
Win machine:
1. When I try to install it as local printer, I select Standard
TCP/IP-Port and enter the ip of the Linux computer e.g.
129.168.0.20). The next dialogue tells me that the device can't be
found an I can select the type of device (e.g. generic network card).
So I stopped here because oviously, this doesn't work correctly.
2. As network printer. Windows finds my Linux, even the printer, but
tells me that the server doesn't offer a correct driver for the printer.
I can then install a driver on the local machine, that means the Windows
one, right? Now I downloaded the right driver and select the .inf-file.
But then a dialogue tells me that the driver isn't the correct one for
this version of windows or not available. So no chance here too.
But I know from other users in the net that it is possible to print from
Win 2000 to Linux correctly. So is somebody here who can help me till
this really works?
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Win95 client can see everyone but linux box
I suspect you either removed TCP/IP or made NETBEUI your default protocol. I believe you can designate Win95's default network protocol via the network icon in the control panel. Sorry, I can't tell you exactly where, I have no machines running 95. Try the various advanced buttons/tabs in the TCP/IP stack bound to that adapter. Also, make certain you don't have both cards installed, it'll just server to confuse the situation. - Original Message - From: Brian [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, January 18, 2003 6:16 AM Subject: [Samba] Win95 client can see everyone but linux box Hi, I'm lucky enough to have samba working fine on SuSE 8.0, sharing a printer with several windows computers. Earlier today I even had my new wireless card working on a Win95 laptop and it could see the whole network, and I wirelessly printed from my living room. COOL. Unfortunately, I screwed it up. The wireless card seems to conflict with the old pcmcia (wired) card and so I uninstalled and reinstalled that card several times in an attempt to make both work at once. (No luck so far.) Somehow this process messed up my wireless printing. Now when clicking on Network Neighborhood the Win95 Client usually at first says the network is unavailable/unreachable and then after a bit more clicking will see the other two windows computers on the network, but not the linux box where the printer is attached. The other two windows computers can see everything in their network neighborhood's, so I don't think the linux box itself is messed up. It must be something about that darn Win95 laptop. And it WAS working earlier. Anyone have a guess at what I screwed up and how I can get it working again? Thanks for any help. (It's actually my wife's laptop and it won't be too good for me to have messed this up!) Brian -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing from Win2000 to Linux
One interesting trick. To see which commands smbd supports for printing,
run:
strings `which smbd` | grep command
You will see commands to pause the entire queue, which I have left out of my
share. If you wanted to fine tune a queue, you could define all these
commands to do just what you like. For example, you might like to make
the printing command also mail a message saying that a user has printed a
file.
This could be made part of your printing command:
echo user %U has printed a file %J from client %m | mail -s JobDone administrator
You might also make pausing the queue impossible from a samba client. So,
you could define:
queuepause command = echo You cannot do this | smbclient -M %m
(I haven't tried this one.)
Joel
On Sat, Jan 18, 2003 at 08:41:39AM -0500, Joel Hammer wrote:
I don't understand your print shares. That doesn't mean they are
incorrect, it just means I don't use this method for configuring my
smb.conf.
Here is the easiest way I know.
If you can print fine from the linux box, that means that the linux box can
handle postscript files, since postscript is THE printing language on linux.
Therefore, send all your windows files to the same queue you print from in
linux. And, on the windows box, select HP laserjet III plus as your driver.
This is a generic postscript driver, that is, it will convert your document
into a generic postscript file. This file can be read with gv, for
example. The file is then transferred to the spool directory specified
in your print share, whence it is printed with lpr.
I hate to depend on automatic, behind the scenes tricks to solve my
printing problems, since you will never stop having printing problems and
you might as well understand what is happening.
Here is what I do. I use lprng but cups should not be too different, I would
hope. There are some permissions problems in cups that I haven't seen in
lprng.
[global]
encrypt passwords = yes
netbios name = HAMMER2
interfaces = 192.168.0.2
security = SHARE
guest account = ftp
[ps]
path = /tmp
read only = No
create mask = 0700
guest ok = yes
hosts allow = 192.168.
printable = Yes
printing = lprng
print command = echo %J %p %s/tmp/junkJ;\
a=`echo '%J' | sed s/^.*- //` ;\
echo This is truncated $a /tmp/junkJ;\
/usr/bin/lpr -Pps -J$a %s;\
rm %s
lpq command = /usr/bin/lpq -Pps
lprm command = /usr/bin/lprm -Pps %j
lppause command = /usr/sbin/lpc hold ps %j
lpresume command = /usr/sbin/lpc release ps %j
share modes = No
use client driver = yes
I explicitly define all the printing commands. Just paranoid,
I guess. It really isn't needed, if everything is working according to
plan. Note: printing = parameter is a share level parameter.
man smb.conf
:/ printing
I don't think share modes does anything but I am too lazy to find out.
Just be sure the ps queue can handle postscript jobs, and you should be
close to a solution.
I won't give you my printcap file, since I use lprng and that might have
a different format from cups, for all I know.
Joel
So, On Sat, Jan 18, 2003 at 09:37:56AM +0100, Michael Herber wrote:
I have two computers here - one with Win2000 and the other with SuSE
8.1. My goal is that I can print from Win to my printer connected on the
Linux machine.
Now I tried quite a few things but nothing will work. First of all, here
my smb.conf:
# Samba config file created using SWAT
# from 0.0.0.0 (0.0.0.0)
# Date: 2003/01/11 16:17:19
# Global parameters
[global]
security = share
guest account = nobody
guest ok = Yes
printing = cups
printer name = lp
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
load printers = Yes
[homes]
comment = Home Directories
valid users = %S
read only = Yes
guest ok = No
veto files =
browseable = No
fstype = FAT
[printers]
comment = All Printers
browseable = yes
public = yes
guest ok = yes
writable = yes
printable = yes
path = /var/spool/samba
[print$]
comment = Printer Drivers
browsable = yes
guest ok = yes
read only = yes
I know that there are two possibilities to install the printer on the
Win machine:
1. When I try to install it as local printer, I select Standard
TCP/IP-Port and enter the ip of the Linux computer e.g.
129.168.0.20). The next dialogue tells me that the device can't be
found an I can select the type of device (e.g. generic network card).
So I stopped here because oviously, this doesn't work correctly.
2. As network printer. Windows finds my Linux, even the printer, but
tells me that the server doesn't offer a correct driver for the
Re: [Samba] File Creation Dates Question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 18 Jan 2003, Mike McMullen wrote: Hi all, I searched the archives for a solution to this issue but didn't find any thing. I have an office with a mix of PCs running ME and XP that use Samba 2.2.7 under RH Linux 7.3 as an archive for mortgage information. When documents are moved to the Samba share, the file creation timestamp on the Linux box reflects the time the files were created on the PCs. What I need is for the creation timestamp to be when it was created on the Linux box by the copy or move. We have some scripts that execute every 20 minutes that use find to locate new files added within that time frame. Files are falling through the cracks because the script sees the original PC creation time and not the Linux creation time. Any insight on how to remedy this will be great appreciated! You might be able to use the map archive parameter to help out. The creation date on a file on a Samba share is really the mod time of the file. Unix file systems only store 3 times (atime, ctime, mtime). cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc ISBN 0-672-32269-2 SAMS Teach Yourself Samba in 24 Hours 2ed 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+KXMDIR7qMdg1EfYRAsUlAJ92SvnrUrgJ+azEQ5k35017kcMOZQCgy0ZW /dlNHmQjJL+29/n+uXKAK3w= =nMks -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Re: SMB+LDAP Question ...
On Fri, 17 Jan 2003 19:31:46 +0100 Thomas Nilsen [EMAIL PROTECTED] wrote: I think I'll sit down and write a complete howto on getting all of this working together. Most existing howto's seems to only include bits of the puzzle. That'd be ++great! :)) If you really do, could you post the link here, please? Thx in advance! Max -- The first time any man's freedom is trodden on, we're all damaged. Cpt. Picard, The Drumhead, StarTrek TNG http://homex.subnet.at/~max/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] An addendum to my PDC troubles.
OK, I lied a bit about not being able to add users. I can do that just fine, if I remember to set the UID above 1000. I still cannot add a computer or log in as root with a client machine. I can change password just fine from WIN2000/XP for all users, including root. I get the error message The system cannot find message text for message number 0x%1 inthe message file for %2 only if I type in the correct password for root, an incorrect password gives me the proper response. Thry to use the normal Administrator alias is no goo either. All other functions are great, and I didn't lose any user settings in the migration. Logs can be provided on request, smb.conf too, though there shouldn't be anything wrong with that, it's nearly the same as the one I have on my home PDC, and it works fine. Anyway, any help is always welcome. Thanks Hans ___ All emails incoming and outgoing from SBS Forestry Inc. are scanned by Kaspersky Antivirus. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] File Creation Dates Question
Just free associating here. The parameter dos filetimes may relate to your situation. If samba does not have an easy way of doing this, you might get creative. You might use force create mode to change the permissions of the file when it is transferred (created?) to the samba share. For example, you might make any new file transferred up to be unreadable by anyone but the owner. Or, you could use force user to make it owned by some bogus owner like newfile (which may have to exist). Then, every minute, on the server run a script which touch'es any file with those ownership or permissions characteristics. This script could also change the file permission/ownership back to what they should be. Joel On Sat, Jan 18, 2003 at 01:35:31AM -0800, Mike McMullen wrote: Hi all, I searched the archives for a solution to this issue but didn't find any thing. I have an office with a mix of PCs running ME and XP that use Samba 2.2.7 under RH Linux 7.3 as an archive for mortgage information. When documents are moved to the Samba share, the file creation timestamp on the Linux box reflects the time the files were created on the PCs. What I need is for the creation timestamp to be when it was created on the Linux box by the copy or move. We have some scripts that execute every 20 minutes that use find to locate new files added within that time frame. Files are falling through the cracks because the script sees the original PC creation time and not the Linux creation time. Any insight on how to remedy this will be great appreciated! Mike Mike McMullen CIO - Baton, Inc. 7637 Fair Oaks Blvd Suite #2 Carmichael, CA 95608 Tel: 1-866-515-4421 or 916-944-7790 ext. 2 Fax: 1-866-843-8795 or 916-944-8422 Email: [EMAIL PROTECTED] Web: www.loanprocessing.net From chaos comes true genius... -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] An addendum to my PDC troubles.
Hans, What happens when you run: smbpasswd root What is the output of: strings smbd | grep /smbpasswd assuming you are in the directory that contains your smbd binary. What are the permissions on your smbpasswd file? Have you verified that you do not have mulitple instances of smbpasswd on your system? - John T. On Sat, 18 Jan 2003, Hans Rasmussen wrote: OK, I lied a bit about not being able to add users. I can do that just fine, if I remember to set the UID above 1000. I still cannot add a computer or log in as root with a client machine. I can change password just fine from WIN2000/XP for all users, including root. I get the error message The system cannot find message text for message number 0x%1 inthe message file for %2 only if I type in the correct password for root, an incorrect password gives me the proper response. Thry to use the normal Administrator alias is no goo either. All other functions are great, and I didn't lose any user settings in the migration. Logs can be provided on request, smb.conf too, though there shouldn't be anything wrong with that, it's nearly the same as the one I have on my home PDC, and it works fine. Anyway, any help is always welcome. Thanks Hans ___ All emails incoming and outgoing from SBS Forestry Inc. are scanned by Kaspersky Antivirus. -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] File Creation Dates Question
I didn't say this, but the find command would be the way to locate files with certain ownership or time characteristics. For example, if you changed the permissions to octal 000 on each file as it came in from the PC, the following command would find then for you: cd samba_directory for i in `find . -maxdepth 1 -perm 000 -type f` do touch $i chmod 770 $i done Have this as a cron job, running with root privilege maybe, every minute. Joel On Sat, Jan 18, 2003 at 12:08:22PM -0500, Joel Hammer wrote: Just free associating here. The parameter dos filetimes may relate to your situation. If samba does not have an easy way of doing this, you might get creative. You might use force create mode to change the permissions of the file when it is transferred (created?) to the samba share. For example, you might make any new file transferred up to be unreadable by anyone but the owner. Or, you could use force user to make it owned by some bogus owner like newfile (which may have to exist). Then, every minute, on the server run a script which touch'es any file with those ownership or permissions characteristics. This script could also change the file permission/ownership back to what they should be. Joel On Sat, Jan 18, 2003 at 01:35:31AM -0800, Mike McMullen wrote: Hi all, I searched the archives for a solution to this issue but didn't find any thing. I have an office with a mix of PCs running ME and XP that use Samba 2.2.7 under RH Linux 7.3 as an archive for mortgage information. When documents are moved to the Samba share, the file creation timestamp on the Linux box reflects the time the files were created on the PCs. What I need is for the creation timestamp to be when it was created on the Linux box by the copy or move. We have some scripts that execute every 20 minutes that use find to locate new files added within that time frame. Files are falling through the cracks because the script sees the original PC creation time and not the Linux creation time. Any insight on how to remedy this will be great appreciated! Mike Mike McMullen CIO - Baton, Inc. 7637 Fair Oaks Blvd Suite #2 Carmichael, CA 95608 Tel: 1-866-515-4421 or 916-944-7790 ext. 2 Fax: 1-866-843-8795 or 916-944-8422 Email: [EMAIL PROTECTED] Web: www.loanprocessing.net From chaos comes true genius... -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] File Creation Dates Question
Here is what man smb.conf has to say: dos filetimes (S) Under DOS and Windows, if a user can write to a file they can change the timestamp on it. Under POSIX semantics, only the owner of the file or root may change the timestamp. By default, Samba runs with POSIX semantics and refuses to change the timestamp on a file if the user smbd is acting on behalf of is not the file owner. Setting this option to true allows DOS semantics and smbd will change the file timestamp as DOS requires. Default: dos filetimes = no Now, it may be that the user smbd is running under doesn't own the file. But, it may be that dos filetimes won't, at least by themselves, solve this problem. See my other post about a brute force workaround. Joel On Sat, Jan 18, 2003 at 09:34:08AM -0800, Mike McMullen wrote: Hi Joel, Thanks for the response. I have set dos filetimes = yes in the conf file but that doesn't seem to have an effect. Thanks, Mike - Original Message - From: Joel Hammer [EMAIL PROTECTED] To: Mike McMullen [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, January 18, 2003 9:08 AM Subject: Re: [Samba] File Creation Dates Question Just free associating here. The parameter dos filetimes may relate to your situation. If samba does not have an easy way of doing this, you might get creative. You might use force create mode to change the permissions of the file when it is transferred (created?) to the samba share. For example, you might make any new file transferred up to be unreadable by anyone but the owner. Or, you could use force user to make it owned by some bogus owner like newfile (which may have to exist). Then, every minute, on the server run a script which touch'es any file with those ownership or permissions characteristics. This script could also change the file permission/ownership back to what they should be. Joel On Sat, Jan 18, 2003 at 01:35:31AM -0800, Mike McMullen wrote: Hi all, I searched the archives for a solution to this issue but didn't find any thing. I have an office with a mix of PCs running ME and XP that use Samba 2.2.7 under RH Linux 7.3 as an archive for mortgage information. When documents are moved to the Samba share, the file creation timestamp on the Linux box reflects the time the files were created on the PCs. What I need is for the creation timestamp to be when it was created on the Linux box by the copy or move. We have some scripts that execute every 20 minutes that use find to locate new files added within that time frame. Files are falling through the cracks because the script sees the original PC creation time and not the Linux creation time. Any insight on how to remedy this will be great appreciated! Mike Mike McMullen CIO - Baton, Inc. 7637 Fair Oaks Blvd Suite #2 Carmichael, CA 95608 Tel: 1-866-515-4421 or 916-944-7790 ext. 2 Fax: 1-866-843-8795 or 916-944-8422 Email: [EMAIL PROTECTED] Web: www.loanprocessing.net From chaos comes true genius... -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] File Creation Dates Question
Hi Joel, I had already set dos filetimes=yes. I still see the same behavior. As a test I tried copying a file from one pc to another pc. The file creation timestamp on the copy retains the original file creation time. Seems like a strange behavior to me. Mike - Original Message - From: Joel Hammer [EMAIL PROTECTED] To: Mike McMullen [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, January 18, 2003 9:58 AM Subject: Re: [Samba] File Creation Dates Question Here is what man smb.conf has to say: dos filetimes (S) Under DOS and Windows, if a user can write to a file they can change the timestamp on it. Under POSIX semantics, only the owner of the file or root may change the timestamp. By default, Samba runs with POSIX semantics and refuses to change the timestamp on a file if the user smbd is acting on behalf of is not the file owner. Setting this option to true allows DOS semantics and smbd will change the file timestamp as DOS requires. Default: dos filetimes = no Now, it may be that the user smbd is running under doesn't own the file. But, it may be that dos filetimes won't, at least by themselves, solve this problem. See my other post about a brute force workaround. Joel On Sat, Jan 18, 2003 at 09:34:08AM -0800, Mike McMullen wrote: Hi Joel, Thanks for the response. I have set dos filetimes = yes in the conf file but that doesn't seem to have an effect. Thanks, Mike - Original Message - From: Joel Hammer [EMAIL PROTECTED] To: Mike McMullen [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, January 18, 2003 9:08 AM Subject: Re: [Samba] File Creation Dates Question Just free associating here. The parameter dos filetimes may relate to your situation. If samba does not have an easy way of doing this, you might get creative. You might use force create mode to change the permissions of the file when it is transferred (created?) to the samba share. For example, you might make any new file transferred up to be unreadable by anyone but the owner. Or, you could use force user to make it owned by some bogus owner like newfile (which may have to exist). Then, every minute, on the server run a script which touch'es any file with those ownership or permissions characteristics. This script could also change the file permission/ownership back to what they should be. Joel On Sat, Jan 18, 2003 at 01:35:31AM -0800, Mike McMullen wrote: Hi all, I searched the archives for a solution to this issue but didn't find any thing. I have an office with a mix of PCs running ME and XP that use Samba 2.2.7 under RH Linux 7.3 as an archive for mortgage information. When documents are moved to the Samba share, the file creation timestamp on the Linux box reflects the time the files were created on the PCs. What I need is for the creation timestamp to be when it was created on the Linux box by the copy or move. We have some scripts that execute every 20 minutes that use find to locate new files added within that time frame. Files are falling through the cracks because the script sees the original PC creation time and not the Linux creation time. Any insight on how to remedy this will be great appreciated! Mike Mike McMullen CIO - Baton, Inc. 7637 Fair Oaks Blvd Suite #2 Carmichael, CA 95608 Tel: 1-866-515-4421 or 916-944-7790 ext. 2 Fax: 1-866-843-8795 or 916-944-8422 Email: [EMAIL PROTECTED] Web: www.loanprocessing.net From chaos comes true genius... -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Can't add print drivers for existing printers
On Friday 17 January 2003 12:53 pm, D. Aaron McCaleb wrote: Either way, the procedure I stated was wrong should have been qualified. Ian's procedure differed from the one recommended in some of the Samba texts (most of which -are- sadly out of date) that I had read. I was only speaking from my experience. I checked, again, after receiving your correction and found that it would work, sorta. If I clicked New Driver from the advanced tab after saying no to install a print driver, it only installed the driver for _that_ version of client. It never prompted for other clients. The sharing tab, from what I could tell, only loaded drivers for other versions onto the _client_ for downloading from the client, itself...not from the server. The only way I was able to get drivers for other versions of windows onto the server was the procedure I listed. I was also able to upload print drivers (for XP, 2000 98) using your procedure, which solved my problem completely. Thank you very much. :^) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] An addendum to my PDC troubles.
Hi John. Thanks for the response. smbpasswd root lets me change the root password, I've verified that by looking at the smbpasswd file afterwards, the time stamp has chaged and the password hash is different. I'll have to give you the output of string later, I'm not at work at the moment and I haven't set up SSH access yet. The permissions on smbpasswd are read and write for root, read for everybody else. There is another smbpasswd on the system, I did an upgrade from the stock mandrake to a custom 2.2.7a build. I did make sure that I am dealing with the correct files though. I did hack passdb.h to remove the RID mapping in order to keep everybodies old RID during the migration. RID directly maps to UID now. I followed instruction from earlier posts in the mailing list. It's entirely possible (probable?) that I voodoo'd that too much. Hans - Original Message - From: John H Terpstra [EMAIL PROTECTED] To: Hans Rasmussen [EMAIL PROTECTED] Cc: Samba [EMAIL PROTECTED] Sent: Saturday, January 18, 2003 9:08 AM Subject: Re: [Samba] An addendum to my PDC troubles. Hans, What happens when you run: smbpasswd root What is the output of: strings smbd | grep /smbpasswd assuming you are in the directory that contains your smbd binary. What are the permissions on your smbpasswd file? Have you verified that you do not have mulitple instances of smbpasswd on your system? - John T. On Sat, 18 Jan 2003, Hans Rasmussen wrote: OK, I lied a bit about not being able to add users. I can do that just fine, if I remember to set the UID above 1000. I still cannot add a computer or log in as root with a client machine. I can change password just fine from WIN2000/XP for all users, including root. I get the error message The system cannot find message text for message number 0x%1 inthe message file for %2 only if I type in the correct password for root, an incorrect password gives me the proper response. Thry to use the normal Administrator alias is no goo either. All other functions are great, and I didn't lose any user settings in the migration. Logs can be provided on request, smb.conf too, though there shouldn't be anything wrong with that, it's nearly the same as the one I have on my home PDC, and it works fine. Anyway, any help is always welcome. Thanks Hans ___ All emails incoming and outgoing from SBS Forestry Inc. are scanned by Kaspersky Antivirus. -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba ___ All emails incoming and outgoing from SBS Forestry Inc. are scanned by Kaspersky Antivirus. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] UNIX/SAMBA file permission interaction
If you're curious, the sticky bit used to have another meaning (which is where the name came from). I'm not clear on the details, but it had something to do with keeping an executable's code segment in memory even if there wasn't an instance running. I'm not sure if any current variety of UNIX still implements that behavior, but I think most/all of them do support sticky bits on directories (it's particularly important for /tmp and /var/tmp). -- Michael Heironimus I'm showing my age I guess but... ;-) The sticky bit was used as you say to keep an executables code segment in memory. Back in the days when minicomputers had a whopping 64k or even 128k of core memory, you set the sticky bit so that applications that were run often started faster (image runup) and you used less memory and vmemory because the code segment could be shared. It was called the sticky bit because it stuck around in memory. Mike Mike McMullen CIO - Baton, Inc. 7637 Fair Oaks Blvd Suite #2 Carmichael, CA 95608 Tel: 1-866-515-4421 or 916-944-7790 ext. 2 Fax: 1-866-843-8795 or 916-944-8422 Email: [EMAIL PROTECTED] Web: www.loanprocessing.net From chaos comes true genius... -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Adding a machine; I think I am onto something
Parameters are: Samba 2.2.7a PDC setup with LDAP includeing posix authentication for Linux. OK, the tutorial I've based my setup on is the Mandrake tutorial found at http://www.mandrakesecure.net/en/docs/ldap-auth.php Works great for autenticateing Linux from LDAP but it is really sparse on the Samba side of things. Esepcially when it comes to adding machine trust accounts. So anyway I have some theories I would like verified. I've found that I can add a posix based machine name and that works fine BUT it only works in ou=People. The system cannot find a machine account in ou=Computers. Seems to me that several things have occured: Jan 18 14:08:42 enigma smbd[12254]: [2003/01/18 14:08:42, 0] passdb/pdb_ldap.c:pdb_getsampwnam(859) Jan 18 14:08:42 enigma smbd[12254]: LDAP search ((uid=spartack_)(objectclass=sambaAccount)) returned 0 entries. 1. Search for a uid=spartack$ which also has objectclass=sambaAccount. Jan 18 14:08:42 enigma smbd[12254]: [2003/01/18 14:08:42, 0] rpc_server/srv_netlog_nt.c:get_md4pw(176) 2. Get the password. Jan 18 14:08:42 enigma smbd[12254]: get_md4pw: Workstation spartack$: no account in domain 3. Can't find the account.(of course because the user has not been added by the 'add user script' setting in smb.conf yet.) Jan 18 14:08:49 enigma smbd[12255]: [2003/01/18 14:08:49, 0] passdb/pdb_ldap.c:pdb_getsampwnam(859) Jan 18 14:08:49 enigma smbd[12255]: LDAP search ((uid=spartack_)(objectclass=sambaAccount)) returned 0 entries. Jan 18 14:08:50 enigma smbd[12255]: [2003/01/18 14:08:50, 0] rpc_server/srv_samr_nt.c:_api_samr_create_user(1929) Jan 18 14:08:50 enigma smbd[12255]: User spartack$ does not exist in system password file (usually /etc/passwd). Cannot add account without a valid local system user. 4. Try again only execute the 'add user script' first. Theoretically, it did not find one because there is no objectClass sambaAccount in the entry HOWEVER, I know from previous attempts it does find the posix only Computer account when it is placed in ou=People. Is there perhaps a different search performed the fist time around despite the log entry or is my understanding of ((uid=spartack_)(objectclass=sambaAccount)) flawed? So am I on target here? I can solve the problem if I can understand it. :-) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] UNIX/SAMBA file permission interaction
Thanks Michael, After receiving this it prompted me to try something different, this time on the UNIX level. For some reason I was under the belief that regardless of the directory permissions the file permissions stood. i.e. if I had a file with permission 644 and I was not the owner then I would not be permitted to delete it. However having tried it I find that Solaris prompts me if I wish to overwrite the default protection. I then tried editing the file and got back the result permission denied. Thanks for the push in the right direction. I've been dealing with Unix for around 10 years now and I've just been shown I still don't really understand how it is working Once again thanks. (And hopefully these emails will help others understand how it works.) David Michael Heironimus wrote: On Sat, Jan 18, 2003 at 10:44:35PM +1100, David Beards wrote: Without the sticky bit set on a folder that has rwx set for ogw a file can be deleted from within this folder (using Windows Explorer) regardless of whether you are the owner or part of the group that this file belongs to. (as long as rw is set for the owner) If you use an application to modify this same file the application behaves as expected and prohibits you from modifying the file. If you set the sticky bit on the folder, Windows Explorer then behaves as it should (as does the application), and if you are not the owner or part of the group that the file belongs to you can not delete the file. I'm sorry, I must be missing something as this does not make sense. Surely I would have expected SAMBA to adhere to the UNIX permissions without the sticky bit being set on the folder. Samba is adhering to the UNIX permissions, that's how directory permissions work. rw on the directory means that you (everyone, in your case) can add/remove directory entries. Deleting a file is nothing more than removing a directory entry, so you can do it because you're modifying the directory and not the file. Setting the sticky bit on a directory changes this behavior to only allow the owner of the file and the owner of the directory to delete the file. If you're curious, the sticky bit used to have another meaning (which is where the name came from). I'm not clear on the details, but it had something to do with keeping an executable's code segment in memory even if there wasn't an instance running. I'm not sure if any current variety of UNIX still implements that behavior, but I think most/all of them do support sticky bits on directories (it's particularly important for /tmp and /var/tmp). -- Michael Heironimus -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- David Beards Technical Manager Networks and Systems CFA 8 Lakeside Drive Burwood East 3151 Ph: 9262 8204 Mobile: 0419 519 366 CAUTION - This message is intended for the use of the individual or entity named above and may contain information that is confidential or privileged. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited and that you must not take any action in reliance on it. If you have received this communication in error, please notify CFA immediately and destroy the original message. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Adding a machine; I think I am onto something
I meditated long and hard on how to do this separation on 2.2.7a, even going so far as to code most of the patch, but ran into the stone wall that the search for the computer account is ALWAYS done as a search for a user account (just with a different name - meaning the trailing $), so I'd have to recode a lot of the stuff that searches for user accounts to handle that. Also, the way the user account is searched for is spread throughout, and calls to getpwent() are made as well to find it, and THAT I definitely could not change, since it is the correct behavior. What's actually needed is full separation of the search for users and computers, and that's not worth it (IMHO) in 2.2.7a if 3.0alpha has it already (I believe it does). I'd rather contribute to 3.0alpha and help get it out the door quicker than try to expand functionality on 2.2.7a. Just my 2 cent's worth! :) Best Diego On Sat, 2003-01-18 at 16:56, Jim wrote: Parameters are: Samba 2.2.7a PDC setup with LDAP includeing posix authentication for Linux. OK, the tutorial I've based my setup on is the Mandrake tutorial found at http://www.mandrakesecure.net/en/docs/ldap-auth.php Works great for autenticateing Linux from LDAP but it is really sparse on the Samba side of things. Esepcially when it comes to adding machine trust accounts. So anyway I have some theories I would like verified. I've found that I can add a posix based machine name and that works fine BUT it only works in ou=People. The system cannot find a machine account in ou=Computers. Seems to me that several things have occured: Jan 18 14:08:42 enigma smbd[12254]: [2003/01/18 14:08:42, 0] passdb/pdb_ldap.c:pdb_getsampwnam(859) Jan 18 14:08:42 enigma smbd[12254]: LDAP search ((uid=spartack_)(objectclass=sambaAccount)) returned 0 entries. 1. Search for a uid=spartack$ which also has objectclass=sambaAccount. Jan 18 14:08:42 enigma smbd[12254]: [2003/01/18 14:08:42, 0] rpc_server/srv_netlog_nt.c:get_md4pw(176) 2. Get the password. Jan 18 14:08:42 enigma smbd[12254]: get_md4pw: Workstation spartack$: no account in domain 3. Can't find the account.(of course because the user has not been added by the 'add user script' setting in smb.conf yet.) Jan 18 14:08:49 enigma smbd[12255]: [2003/01/18 14:08:49, 0] passdb/pdb_ldap.c:pdb_getsampwnam(859) Jan 18 14:08:49 enigma smbd[12255]: LDAP search ((uid=spartack_)(objectclass=sambaAccount)) returned 0 entries. Jan 18 14:08:50 enigma smbd[12255]: [2003/01/18 14:08:50, 0] rpc_server/srv_samr_nt.c:_api_samr_create_user(1929) Jan 18 14:08:50 enigma smbd[12255]: User spartack$ does not exist in system password file (usually /etc/passwd). Cannot add account without a valid local system user. 4. Try again only execute the 'add user script' first. Theoretically, it did not find one because there is no objectClass sambaAccount in the entry HOWEVER, I know from previous attempts it does find the posix only Computer account when it is placed in ou=People. Is there perhaps a different search performed the fist time around despite the log entry or is my understanding of ((uid=spartack_)(objectclass=sambaAccount)) flawed? So am I on target here? I can solve the problem if I can understand it. :-) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Adding a machine; I think I am onto something
Am Sam, 2003-01-18 um 23.56 schrieb Jim: So anyway I have some theories I would like verified. I've found that I can add a posix based machine name and that works fine BUT it only works in ou=People. The system cannot find a machine account in ou=Computers. Is ou=Computers below ou=People? If not, neither Samba nor pam will notice it. Theoretically, it did not find one because there is no objectClass sambaAccount in the entry HOWEVER, I know from previous attempts it does find the posix only Computer account when it is placed in ou=People. Is there perhaps a different search performed the fist time around despite the log entry or is my understanding of ((uid=spartack_)(objectclass=sambaAccount)) flawed? Samba itself doesn't lookup posix things in LDAP. That is the job of nsswitch/pam. You have to configure in your libnss-ldap.conf a searchbase that includes ou=People and ou=Computers as well. regards Dariush -- PGP Fingerprint: 0x886C99A1 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Core dump of net -- fix to ldap.c
I've been having a problem with net crashing in SAMBA_3_0 and OpenLDAP
2.0.27:
assertion entry != NULL failed: file getvalues.c, line 93, function
ldap_get_values_len
Abort trap (core dumped)
I traced the problem to the ads_set_machine_sd routine in ldap.c. It
wasn't checking the return from ads_first_entry, which was returning a
NULL in my tests.
Here's the fix. LDAP_NO_RESULTS_RETURNED may not be the best error
code, but it's descriptive.
# cvs diff -pu ldap.c
Index: ldap.c
===
RCS file: /cvsroot/samba/source/libads/ldap.c,v
retrieving revision 1.55.2.13
diff -p -u -r1.55.2.13 ldap.c
--- ldap.c 3 Jan 2003 08:28:02 - 1.55.2.13
+++ ldap.c 18 Jan 2003 14:44:33 -
@@ -1430,6 +1430,11 @@ ADS_STATUS ads_set_machine_sd(ADS_STRUCT
if (!ADS_ERR_OK(ret)) return ret;
msg = ads_first_entry(ads, res);
+if (!msg) { /* KJC */
+ret = ADS_ERROR(LDAP_NO_RESULTS_RETURNED);
+ goto ads_set_sd_error;
+ }
+
ads_pull_sid(ads, msg, attrs[1], sid);
if (!(ctx = talloc_init(sec_io_desc))) {
ret = ADS_ERROR(LDAP_NO_MEMORY);
Ken
Re: samba-vms digest, Vol 1 #370 - 7 msgs (Mensagemencaminhada)
Estarei em férias até 20 de Janeiro. Neste Período os correios recebidos por mim estão sendo encaminhados para Afonso Estevão Torres. Atenciosamente, Cristina Roque
CVS update: samba/docs/textdocs
Date: Sat Jan 18 08:14:39 2003 Author: jht Update of /home/cvs/samba/docs/textdocs In directory dp.samba.org:/tmp/cvs-serv15499 Added Files: CreatingGroupProfiles-Win9X.txt Log Message: Merge from 3.0.0 tree. Revisions: CreatingGroupProfiles-Win9X.txt 1.1 = 1.2 http://www.samba.org/cgi-bin/cvsweb/samba/docs/textdocs/CreatingGroupProfiles-Win9X.txt?r1=1.1r2=1.2
CVS update: samba/source/rpc_server
Date: Sat Jan 18 20:41:19 2003 Author: jmcd Update of /home/cvs/samba/source/rpc_server In directory dp.samba.org:/tmp/cvs-serv2035 Modified Files: srv_pipe.c Log Message: Fix some debug levels (were set to 0 with RPC module patch), and change one fprintf(stderr,...) to DEBUG. Revisions: srv_pipe.c 1.101 = 1.102 http://www.samba.org/cgi-bin/cvsweb/samba/source/rpc_server/srv_pipe.c?r1=1.101r2=1.102
CVS update: samba/examples/LDAP
Date: Sun Jan 19 03:51:32 2003 Author: jerry Update of /data/cvs/samba/examples/LDAP In directory dp.samba.org:/tmp/cvs-serv32728 Removed Files: export_smbpasswd.pl import_smbpasswd.pl Log Message: only supporting the Net::LDAP module now Revisions: export_smbpasswd.pl 1.2 = NONE http://www.samba.org/cgi-bin/cvsweb/samba/examples/LDAP/export_smbpasswd.pl?rev=1.2 import_smbpasswd.pl 1.2 = NONE http://www.samba.org/cgi-bin/cvsweb/samba/examples/LDAP/import_smbpasswd.pl?rev=1.2
