dtrace of a Samba nbench run shows
Hi folks, I have been using dtrace, and particularly procsystime, to measure Samba system call usage stuff. This is what I get: cs-cc1# ./procsystime -n smbd Tracing... Hit Ctrl-C to end... ^C Elapsed Times for processes smbd, SYSCALL TIME (ns) sysarch 1492 thr_self 2636 __getcwd 5695 getsockname 5778 accept 6952 sendto 8019 getpeername 8273 setsockopt 9394 pipe 13567 kenv 15151 umask 16400 sigaction 23504 msync 24068 mprotect 26960 getpid 29888 socket 38078 dup2 42323 chdir 49643 getgroups 74299 wait4 108578 connect 148649 sigprocmask 150443 __sysctl 215389 getegid 243731 mmap 257379 setregid 260529 setgroups 270894 thr_new 376349 munmap 428773 fork 511601 sigreturn 668402 chown 703765 getuid 821748 chmod1175632 kill1230340 write1281535 geteuid1918738 rmdir2376245 mkdir2516070 fsync3346330 setreuid5205649 gettimeofday9212264 lseek9336442 pathconf 18606662 statfs 29714064 access 30073540 fstatfs 31360178 lstat 33902417 extattr_get_fd 38793210 fchmod 147266506 rename 156300564 fstat 234898224 utimes 237551881 getdirentries 253926535 extattr_set_link 371269699 pread 671050763 unlink 768327954 pwrite 825201124 fstatat 866823356 clock_gettime 1257134991 writev 1984839112 read 2922189298 close 6180434183 fcntl 7849631277 stat 7872399963 extattr_get_file 7887564205 ioctl 9034605338 open23145865857 select 274329462364 poll 753606057912 _umtx_op 1097794513187 So, what is _umtx_op? I guess I have to move to kqueue as well. -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Delete files with time stamp on Samba Server
I have a remote Samba Server where Windows machines place backup files once a day. The format is backup_2013-05-03_13.45.44_.zip Before the Windows client places the file it removes the file from the day before. In turn I do a backup of the backup files once every week(Friday) to another directory. This directory will eventually fill up and I need to make a check and remove the oldest file maybe once a week before the new file is copied, or put in other words I never want more than 4 files to be in this directory. My scripting skills are not at the level where I can figure this out, so I'll appreciate suggestions on how to solve this in the correct way. Thanks :-) /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Delete files with time stamp on Samba Server
On 20 May 2013 13:34, Leslie Jensen les...@eskk.nu wrote: I have a remote Samba Server where Windows machines place backup files once a day. The format is backup_2013-05-03_13.45.44_.**zip Before the Windows client places the file it removes the file from the day before. In turn I do a backup of the backup files once every week(Friday) to another directory. This directory will eventually fill up and I need to make a check and remove the oldest file maybe once a week before the new file is copied, or put in other words I never want more than 4 files to be in this directory. My scripting skills are not at the level where I can figure this out, so I'll appreciate suggestions on how to solve this in the correct way. Hi Leslie! I believe this is what you need: --- START --- #!/bin/sh KEEP='5' pg_dump -U gp /backups/gp.`date +%Y%m%d-%H%M%S`.sql N=1 for file in `ls -r /backups/gp.*` do [ $N -gt $KEEP ] rm -f $file N=`expr $N + 1` done --- END --- I am using this to keep 5 backup files... Modify as needed. Cheers, Miguel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Delete files with time stamp on Samba Server
2013-05-20 15:52, Miguel Barbosa Gonçalves skrev: On 20 May 2013 13:34, Leslie Jensen les...@eskk.nu wrote: I have a remote Samba Server where Windows machines place backup files once a day. The format is backup_2013-05-03_13.45.44_.**zip Before the Windows client places the file it removes the file from the day before. In turn I do a backup of the backup files once every week(Friday) to another directory. This directory will eventually fill up and I need to make a check and remove the oldest file maybe once a week before the new file is copied, or put in other words I never want more than 4 files to be in this directory. My scripting skills are not at the level where I can figure this out, so I'll appreciate suggestions on how to solve this in the correct way. Hi Leslie! I believe this is what you need: --- START --- #!/bin/sh KEEP='5' pg_dump -U gp /backups/gp.`date +%Y%m%d-%H%M%S`.sql N=1 for file in `ls -r /backups/gp.*` do [ $N -gt $KEEP ] rm -f $file N=`expr $N + 1` done --- END --- I am using this to keep 5 backup files... Modify as needed. Cheers, Miguel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Thanks Miguel I'll see what I can do with it. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD as Samba Server and Windows as Client
There are just so many things that could go wrong on a samba setup that it is beyond funny in my opinion. You have authentication method (kerberos, pam, txt), ports, winbind and dns just to list a few. I suggest you start samba in debug mode and enable full logging. The documentation from samba its self is probably going to be much more comprehensive: http://www.samba.org/samba/docs/man/manpages-3/smbd.8.html I would also try to connect with various clients like a linux, XP, vista or win7. These connection attempts should generate comprehensive logs when samba is running in debug mode. You can then start to get some idea why the connection is being refused by reading through the generated logs. Also, several how-to's already exist on the FreeBSD forums - as an example: http://forums.freebsd.org/showthread.php?t=36137 - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-as-Samba-Server-and-Windows-as-Client-tp5804306p5804418.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD as Samba Server and Windows as Client
Dear All , I could be able to connect a FreeBSD 9.1 amd64 computer as client to a Windows XP ( 32 bits ) by using information supplied by the mail http://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250500.html and I sent a mail http://lists.freebsd.org/pipermail/freebsd-doc/2013-April/021857.html to share my findings . Previously , I tried to make a FreeBSD 9.1 amd64 as Samba server and connect a Windows XP as a client computer . By using The FreeBSD Handbook , many documents from www.samba.org and Internet , I could not be able to access to the FreeBSD Samba server from Windows XP : Continuously I have received Access denied error message in Windows XP although in the server the related directory and files have mode rwx-rwx-rwx . The same message is produced even for Linux Samba Server . The examples given in the documents are partial statements without actually used files / statements in such a setting , and sometimes inconsistent or contradictory with each other because they are mostly written manually . If a working , applicable set of files / statements are supplied , it will be appreciated very much . After a successful implementation , I will send an e-mail about this set up as an example for the FreeBSD Handbook to share our information with other people in need . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD as Samba Server and Windows as Client
On Tue, Apr 16, 2013 at 12:20 PM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: Dear All , I could be able to connect a FreeBSD 9.1 amd64 computer as client to a Windows XP ( 32 bits ) by using information supplied by the mail http://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250500.html and I sent a mail http://lists.freebsd.org/pipermail/freebsd-doc/2013-April/021857.html to share my findings . Previously , I tried to make a FreeBSD 9.1 amd64 as Samba server and connect a Windows XP as a client computer . By using The FreeBSD Handbook , many documents from www.samba.org and Internet , I could not be able to access to the FreeBSD Samba server from Windows XP : Continuously I have received Access denied error message in Windows XP although in the server the related directory and files have mode rwx-rwx-rwx . The same message is produced even for Linux Samba Server . The examples given in the documents are partial statements without actually used files / statements in such a setting , and sometimes inconsistent or contradictory with each other because they are mostly written manually . If a working , applicable set of files / statements are supplied , it will be appreciated very much . After a successful implementation , I will send an e-mail about this set up as an example for the FreeBSD Handbook to share our information with other people in need . All I can tell you is that it is definitely possible using FreeBSD. The FreeNAS folks do exactly that as does the company I work for. I do not have the time to spend helping you get it going and I note that you do not tell us which version of Samba you are using, but it does work. Have you tried setting the permissions correctly on the directory you are sharing? Do you know if it is getting Access Denied trying to access the Share or trying to create a file. -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD as Samba Server and Windows as Client
On Tue, Apr 16, 2013 at 12:34 PM, Richard Sharpe realrichardsha...@gmail.com wrote: On Tue, Apr 16, 2013 at 12:20 PM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: Dear All , I could be able to connect a FreeBSD 9.1 amd64 computer as client to a Windows XP ( 32 bits ) by using information supplied by the mail http://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250500.html and I sent a mail http://lists.freebsd.org/pipermail/freebsd-doc/2013-April/021857.html to share my findings . Previously , I tried to make a FreeBSD 9.1 amd64 as Samba server and connect a Windows XP as a client computer . By using The FreeBSD Handbook , many documents from www.samba.org and Internet , I could not be able to access to the FreeBSD Samba server from Windows XP : Continuously I have received Access denied error message in Windows XP although in the server the related directory and files have mode rwx-rwx-rwx . The same message is produced even for Linux Samba Server . The examples given in the documents are partial statements without actually used files / statements in such a setting , and sometimes inconsistent or contradictory with each other because they are mostly written manually . If a working , applicable set of files / statements are supplied , it will be appreciated very much . After a successful implementation , I will send an e-mail about this set up as an example for the FreeBSD Handbook to share our information with other people in need . All I can tell you is that it is definitely possible using FreeBSD. The FreeNAS folks do exactly that as does the company I work for. I do not have the time to spend helping you get it going and I note that you do not tell us which version of Samba you are using, but it does work. Have you tried setting the permissions correctly on the directory you are sharing? Do you know if it is getting Access Denied trying to access the Share or trying to create a file. -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操) Samba Version : FreeBSD 9.1 amd64 package . There is no fault in FreeBSD because from a Linux computer , it is possible to access the Samba service . I tried FreeNAS , but installation did not work ( It was my first install , therefore , it is very likely that I made some mistakes ) . Windows is not able to see directory contents of Samba server . When directory is not visible , it is not possible to write into it . Perhaps in the Windows XP , some settings may be wrong or missing . For that reason , I wanted to have a COMPLETE settings applied , working example. There are the following pages : http://www.samba.org/samba/docs/using_samba/toc.html Using Samba, 2nd Edition http://www.samba.org/samba/docs/using_samba/ch02.html Chapter 2. Installing Samba on a Unix System http://www.samba.org/samba/docs/using_samba/ch03.html Chapter 3. Configuring Windows Clients http://www.samba.org/samba/docs/using_samba/ch05.html Chapter 5. Unix Clients Some Linux distributions have very well designed graphical Samba configuration applications . No one of them is working in the Windows side . My opinion is that , Samba installation is correct , but Windows side has problem which I do not know how to isolate it and to correct it . Only a working complete set up may be useful , because all of the examples are partial explanatory demonstrations . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD as Samba Server and Windows as Client
On 4/16/2013 2:20 PM, Mehmet Erol Sanliturk wrote: Dear All , I could be able to connect a FreeBSD 9.1 amd64 computer as client to a Windows XP ( 32 bits ) by using information supplied by the mail http://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250500.html and I sent a mail http://lists.freebsd.org/pipermail/freebsd-doc/2013-April/021857.html to share my findings . Previously , I tried to make a FreeBSD 9.1 amd64 as Samba server and connect a Windows XP as a client computer . By using The FreeBSD Handbook , many documents from www.samba.org and Internet , I could not be able to access to the FreeBSD Samba server from Windows XP : Continuously I have received Access denied error message in Windows XP although in the server the related directory and files have mode rwx-rwx-rwx . The same message is produced even for Linux Samba Server . The examples given in the documents are partial statements without actually used files / statements in such a setting , and sometimes inconsistent or contradictory with each other because they are mostly written manually . If a working , applicable set of files / statements are supplied , it will be appreciated very much . After a successful implementation , I will send an e-mail about this set up as an example for the FreeBSD Handbook to share our information with other people in need . Thank you very much . Mehmet Erol Sanliturk My guess is your firewall. Samba uses tcp and udp, you have to allow udp on ports 137 and 138. Turn off your firewall and try again. It's frustrated me a couple times when I've first set it up. Either that, or add `guest ok = Yes` lines to the shares. If you have a second non-windows computer available, I'd try with that. Windows makes some assumptions about what to remember, and sort of assumes the server's working properly from the beginning. Using another computer will make testing faster. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD as Samba Server and Windows as Client
On Tue, Apr 16, 2013 at 2:40 PM, Joshua Isom jri...@gmail.com wrote: On 4/16/2013 2:20 PM, Mehmet Erol Sanliturk wrote: Dear All , I could be able to connect a FreeBSD 9.1 amd64 computer as client to a Windows XP ( 32 bits ) by using information supplied by the mail http://lists.freebsd.org/**pipermail/freebsd-questions/** 2013-April/250500.htmlhttp://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250500.html and I sent a mail http://lists.freebsd.org/**pipermail/freebsd-doc/2013-**April/021857.htmlhttp://lists.freebsd.org/pipermail/freebsd-doc/2013-April/021857.html to share my findings . Previously , I tried to make a FreeBSD 9.1 amd64 as Samba server and connect a Windows XP as a client computer . By using The FreeBSD Handbook , many documents from www.samba.org and Internet , I could not be able to access to the FreeBSD Samba server from Windows XP : Continuously I have received Access denied error message in Windows XP although in the server the related directory and files have mode rwx-rwx-rwx . The same message is produced even for Linux Samba Server . The examples given in the documents are partial statements without actually used files / statements in such a setting , and sometimes inconsistent or contradictory with each other because they are mostly written manually . If a working , applicable set of files / statements are supplied , it will be appreciated very much . After a successful implementation , I will send an e-mail about this set up as an example for the FreeBSD Handbook to share our information with other people in need . Thank you very much . Mehmet Erol Sanliturk My guess is your firewall. Samba uses tcp and udp, you have to allow udp on ports 137 and 138. Turn off your firewall and try again. It's frustrated me a couple times when I've first set it up. Either that, or add `guest ok = Yes` lines to the shares. If you have a second non-windows computer available, I'd try with that. Windows makes some assumptions about what to remember, and sort of assumes the server's working properly from the beginning. Using another computer will make testing faster. In Windows , Firewall is OFF . There is no any other firewall in the network . From a Linux computer , it is possible to connect . Guest is allowed . In Windows , in its menus , during my settings , I could not see any mention of Ports . Therefore , it is necessary to know how to set such ports . It seems that , some values are not set in Windows . In documents , sometimes their writers , are not mentioning some points . These points may be not important for them but may be critical for a newly starter person . Documentation write-ups are full of such missing expertise information . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
SaMBa 4 - man pages
Hi all, When installing Samba4 on FreeBSD 9.1, the man pages are not installed. Does anyone know why this happens? Thanks!! -- Celso Vianna BSD User: 51318 http://www.bsdcounter.org Palmas/TO ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mounting a samba share on boot?
From: Polytropon free...@edvax.de To: Bill Tillman btillma...@yahoo.com Cc: freebsd-questions@freebsd.org freebsd-questions@freebsd.org Sent: Wednesday, December 12, 2012 12:40 AM Subject: Re: Mounting a samba share on boot? On Tue, 11 Dec 2012 14:08:38 -0800 (PST), Bill Tillman wrote: Typically, Samba is used so that Windows or other SMB type OS'es can access the server. That said, I would simplify all this with the way I have mine setup. You will of course need the shares configured in your smb.conf, then simply put a command in your /etc/rc.local or /etc/rc.d/ to launch smdb and nmbd. I don't rely on anything in /etc/fstab to use samba. It's all in my smb.conf file. Yes, that would be the other way round, which I thought would be less probable due to the question presented in the subject. Terms like mount [...] on boot suggests that FreeBSD would act as a SMB client here. Of course, the standard way to do things like this would usually be something like NFS, which is not very well supported in Windows land (and therefor requiring SMB stuff). Delegating the configuration into _one_ file (instead of spreading it across /etc/fstab, /etc/nsmb.conf and maybe some handcrafted /usr/local/etc/rc.d script) sounds like a much better approach. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I've heard from more than one person that Samba is no good. Including the IT guru here where I work. All I know is that I've been running it for years and without a single incident. I quietly and reliably allows my Windows workstations to access my FreeBSD server's like they were very expensive Windows file servers. Never messed with the printing side of it and don't need to . File sharing alone has been worth the investment in time to learn Samba. As for NFS, I have found, on my network at least that using the TCP and -i options to keep it from timing out has worked fine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mounting a samba share on boot?
On Wed, 12 Dec 2012 04:27:31 -0800 (PST) Bill Tillman articulated: On Tue, 11 Dec 2012 14:08:38 -0800 (PST), Bill Tillman wrote: Typically, Samba is used so that Windows or other SMB type OS'es can access the server. That said, I would simplify all this with the way I have mine setup. You will of course need the shares configured in your smb.conf, then simply put a command in your /etc/rc.local or /etc/rc.d/ to launch smdb and nmbd. I don't rely on anything in /etc/fstab to use samba. It's all in my smb.conf file. Yes, that would be the other way round, which I thought would be less probable due to the question presented in the subject. Terms like mount [...] on boot suggests that FreeBSD would act as a SMB client here. Of course, the standard way to do things like this would usually be something like NFS, which is not very well supported in Windows land (and therefor requiring SMB stuff). Delegating the configuration into _one_ file (instead of spreading it across /etc/fstab, /etc/nsmb.conf and maybe some handcrafted /usr/local/etc/rc.d script) sounds like a much better approach. NFS is available on Windows 7, it's just not installed by default. In order to activate the Client for NFS, go into the Control Panel, and go to Programs and Features. In the left hand column, you'll see a link for Turn Windows features on or off. Select that, and it will open a list box that shows all of the optional components built in to Windows 7. Some are already activated. Expand the entry for Services for NFS. There are two check boxes under that. Check them and hit OK. Windows will install those components and ask to reboot your system. Once you have rebooted, Client for NFS will be installed. To use it, go to Administrative Tools-Services for NFS to configure it. Alternatively, you can use the command line program 'nfsadmin' to configure. For other versions of Windows, see: How to install Client for NFS on Windows: http://support.microsoft.com/kb/324055 I have seen several setups with this sort of integration that worked just fine. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mounting a samba share on boot?
On 12/11/2012 10:25 AM, Hanafi Syahroini wrote: This can be done with appropriate entries in /etc/fstab. However, I'd recommend against doing so because, if the SMB server is unreachable when the FreeBSD system boots, the FreeBSD box will hang looking for the SMB connection. A better way is to put a custom script in /usr/local/etc/rc.d/ that initiates the SMB mounts there. This too could fail, but it doesn't prevent the OS From booting fully. -- --- Tim Daneliuk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mounting a samba share on boot?
On Tue, 11 Dec 2012 23:25:56 +0700, Hanafi Syahroini wrote: [nothing] First of all, it's not uncommon to place the question into the message body (which you did not), and using a descriptive subject (which you did). :-) So I assume your question is _how_ to mount a SMB share at boot. This can be easily done by adding the required line to the /etc/fstab file. Because network connection is required to perform the mount, you could use the late option in addition to other options you might need. See man mount for detais, as well as /etc/rc.d/mountlate. The line would be like this: //USERNAME@SERVERNAME/share /smb/share smbfs rw,late 0 0 In this example, SERVERNAME is the server to access, and share the name of the share; /smb/share will be the directory it will be mounted at. Access to multiple drive letters would look like this: //Administrator@WINPC/a$ /smb/a smbfs rw,late 0 0 //Administrator@WINPC/c$ /smb/c smbfs rw,late 0 0 //Administrator@WINPC/d$ /smb/d smbfs rw,late 0 0 //Administrator@WINPC/e$ /smb/e smbfs rw,late 0 0 //Administrator@WINPC/f$ /smb/f smbfs rw,late 0 0 Here WINPC is the name of the server. Using Administrator in this case is not safe, but no problem in settings where people don't care for security anyway. :-) Also see man smbfs and man fstab for details. It might be required to put additional information in /etc/nsmb.conf, for example: [default] workgroup=YOUR_WORKGROUP_NAME [SERVERNAME] addr=192.168.2.2 [SERVERNAME:USERNAME] password=TOPSECRET Substitute SERVERNAME, USERNAME and TOPSECRET for the organisational information and access credentials that apply. See man nsmb.conf for details. Further instructions can easily be found in the online docs: http://www.freebsd.org/doc/faq/book.html#mount-smb-share http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-samba.html Note that if you still encounter network problems, it's better to write a short rc.d style script that performs the mount_smb commands, and use the proper keywords to have it run when the network connection is up and running. See man rc.d for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mounting a samba share on boot?
From: Polytropon free...@edvax.de To: Hanafi Syahroini han...@zigma-jp.com Cc: freebsd-questions@freebsd.org Sent: Tuesday, December 11, 2012 11:57 AM Subject: Re: Mounting a samba share on boot? On Tue, 11 Dec 2012 23:25:56 +0700, Hanafi Syahroini wrote: [nothing] First of all, it's not uncommon to place the question into the message body (which you did not), and using a descriptive subject (which you did). :-) So I assume your question is _how_ to mount a SMB share at boot. This can be easily done by adding the required line to the /etc/fstab file. Because network connection is required to perform the mount, you could use the late option in addition to other options you might need. See man mount for detais, as well as /etc/rc.d/mountlate. The line would be like this: //USERNAME@SERVERNAME/share /smb/share smbfs rw,late 0 0 In this example, SERVERNAME is the server to access, and share the name of the share; /smb/share will be the directory it will be mounted at. Access to multiple drive letters would look like this: //Administrator@WINPC/a$ /smb/a smbfs rw,late 0 0 //Administrator@WINPC/c$ /smb/c smbfs rw,late 0 0 //Administrator@WINPC/d$ /smb/d smbfs rw,late 0 0 //Administrator@WINPC/e$ /smb/e smbfs rw,late 0 0 //Administrator@WINPC/f$ /smb/f smbfs rw,late 0 0 Here WINPC is the name of the server. Using Administrator in this case is not safe, but no problem in settings where people don't care for security anyway. :-) Also see man smbfs and man fstab for details. It might be required to put additional information in /etc/nsmb.conf, for example: [default] workgroup=YOUR_WORKGROUP_NAME [SERVERNAME] addr=192.168.2.2 [SERVERNAME:USERNAME] password=TOPSECRET Substitute SERVERNAME, USERNAME and TOPSECRET for the organisational information and access credentials that apply. See man nsmb.conf for details. Further instructions can easily be found in the online docs: http://www.freebsd.org/doc/faq/book.html#mount-smb-share http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-samba.html Note that if you still encounter network problems, it's better to write a short rc.d style script that performs the mount_smb commands, and use the proper keywords to have it run when the network connection is up and running. See man rc.d for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org That's a great answer but let me insert that most people, not all but most, do not use Samba to access a server from other FreeBSD servers. So I feel the two replies thus far are overkill. Typically, Samba is used so that Windows or other SMB type OS'es can access the server. That said, I would simplify all this with the way I have mine setup. You will of course need the shares configured in your smb.conf, then simply put a command in your /etc/rc.local or /etc/rc.d/ to launch smdb and nmbd. I don't rely on anything in /etc/fstab to use samba. It's all in my smb.conf file. However, Polytropon has presented a great answer here. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mounting a samba share on boot?
On Tue, 11 Dec 2012 14:08:38 -0800 (PST), Bill Tillman wrote: Typically, Samba is used so that Windows or other SMB type OS'es can access the server. That said, I would simplify all this with the way I have mine setup. You will of course need the shares configured in your smb.conf, then simply put a command in your /etc/rc.local or /etc/rc.d/ to launch smdb and nmbd. I don't rely on anything in /etc/fstab to use samba. It's all in my smb.conf file. Yes, that would be the other way round, which I thought would be less probable due to the question presented in the subject. Terms like mount [...] on boot suggests that FreeBSD would act as a SMB client here. Of course, the standard way to do things like this would usually be something like NFS, which is not very well supported in Windows land (and therefor requiring SMB stuff). Delegating the configuration into _one_ file (instead of spreading it across /etc/fstab, /etc/nsmb.conf and maybe some handcrafted /usr/local/etc/rc.d script) sounds like a much better approach. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Samba and handbook
According to http://www.se.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-samba.html One can use samba_enable=YES Or, for fine grain control: nmbd_enable=YES smbd_enable=YES 20121022: AFFECTS: users of net/samba36 AUTHOR: ti...@freebsd.org Startup rc.d/samba script was modified to address some problems with the fine control of supplimentary daemons. As a side effect now it's always necessary to specify in rc.conf: samba_enable=YES to get the script working. You can still control each of the daemons individualy, by disabling/enabling them with: nmbd_enable=NO smbd_enable=NO winbindd_enable=YES The Handbook information is out of date because of this and should be corrected. thanks :-) /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
utx.log doesn't update for Samba unmounts
Hello, I'm running 9.1-PRERELEASE (built Aug 1) with Samba 3.6 from ports. I've noticed that the last command's output shows still logged in for all previous smb connections since the last shutdown. However, smbstatus seems accurate, showing only a handful of users connected. For instance, right now, 'last' shows 500 users still logged in, when it's really only a few. I discovered this via a Nagios alert that I had a couple hundred users logged in. The last time I had active SMB/CIFS users was in May of this year, and I don't recall this happening then (judging from Nagios), but that was 9.0-RELEASE. Can anyone reproduce this or does anyone have any ideas? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: can't build Samba 35 on FreeBSD 9.0
On Wed, Aug 15, 2012 at 8:59 PM, James D. Parra jam...@musicreports.com wrote: Hello, I am trying to install Samba35 on FreeBSD 9.0 but I keep getting a build error. The text you gave us gives me the thought you are flailing in the dark. First off, use a port management tool eg portmaster. Learn how to use it fully including regularly reading /usr/ports/UPDATING The handbook has great information on managing ports, I suggest reading it closely if you want FreeBSD to be your friend. In this scenario, you would use portsnap fetch update(assuming you've once a portsnap extract once before) portmaster /usr/ports/net/samba35 The specific error in your message indicates some problem with ccache. What does your /etc/make.conf look like? -- Adam Vande More ~ Thanks all for your replies. I had copied the details from what I had done from, http://forums.freebsd.org/archive/index.php/t-21461.html. I knew what the OP meant so I had issued, portsnap fetch, then portsnap extract, on my system. I was able to get this to work on FreeBSD 8.2 and was hoping to also get this working on 9.0. Since I will be using Kerberos, I use, 'make KRB5_HOME=/usr/local install clean'. My /etc/make.conf file has the following; cat /etc/make.conf # Uncomment this if you want to do port builds with no interaction #BATCH=yes # Keep KDE4 in /usr/local, fixes sharing of icons / mime and others KDE4_PREFIX=/usr/local # added by use.perl 2012-06-28 21:39:00 PERL_VERSION=5.12.4 #To build Samba WITH_ADS=yes snip I do need ADS as I will be joining this server to our domain. For reference, here is the build error; libsmb/libsmb_setget.c: In function 'smbc_getOptionUseCCache': libsmb/libsmb_setget.c:427: error: 'SMB_CTX_FLAG_USE_CCACHE' undeclared (first use in this function) libsmb/libsmb_setget.c:427: error: (Each undeclared identifier is reported only once libsmb/libsmb_setget.c:427: error: for each function it appears in.) libsmb/libsmb_setget.c: In function 'smbc_setOptionUseCCache': libsmb/libsmb_setget.c:435: error: 'SMB_CTX_FLAG_USE_CCACHE' undeclared (first use in this function) The following command failed: cc -I/usr/local/include -O2 -pipe -DLDAP_DEPRECATED -fno-strict-aliasing -I. -I/usr/ports/net/samba35/work/samba-3.5.15/source3 -I/usr/ports/net/samba35/work/samba-3.5.15/source3/iniparser/src -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -DHAVE_CONFIG_H -I/usr/local/include -I/usr/local/include -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -I./../lib/popt -I/usr/local/include -DLDAP_DEPRECATED -I/usr/ports/net/samba35/work/samba-3.5.15/source3/lib -I.. -I../source4 -D_SAMBA_BUILD_=3 -D_SAMBA_BUILD_=3 -fPIC -DPIC -c libsmb/libsmb_setget.c -o libsmb/libsmb_setget.o gmake: *** [libsmb/libsmb_setget.o] Error 1 *** Error code 1 Stop in /usr/ports/net/samba35. *** Error code 1 Stop in /usr/ports/net/samba35. snip Thanks for your help. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
can't build Samba 35 on FreeBSD 9.0
Hello, I am trying to install Samba35 on FreeBSD 9.0 but I keep getting a build error. portsnap extract portsnap fetch update cd /usr/ports/devel/libtool make deinstall make install clean cd /usr/ports/security/krb5 make deinstall make KRB5_HOME=/usr/local install clean and finally; cd /usr/ports/net/samba35 make KRB5_HOME=/usr/local install clean With my fingers crossed I hoped for the best and yet I received the following error during compiling; snip Compiling libsmb/libsmb_setget.c libsmb/libsmb_setget.c: In function 'smbc_getOptionUseCCache': libsmb/libsmb_setget.c:427: error: 'SMB_CTX_FLAG_USE_CCACHE' undeclared (first use in this function) libsmb/libsmb_setget.c:427: error: (Each undeclared identifier is reported only once libsmb/libsmb_setget.c:427: error: for each function it appears in.) libsmb/libsmb_setget.c: In function 'smbc_setOptionUseCCache': libsmb/libsmb_setget.c:435: error: 'SMB_CTX_FLAG_USE_CCACHE' undeclared (first use in this function) The following command failed: cc -I/usr/local/include -O2 -pipe -DLDAP_DEPRECATED -fno-strict-aliasing -I. -I/usr/ports/net/samba35/work/samba-3.5.15/source3 -I/usr/ports/net/samba35/work/samba-3.5.15/source3/iniparser/src -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -DHAVE_CONFIG_H -I/usr/local/include -I/usr/local/include -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -I./../lib/popt -I/usr/local/include -DLDAP_DEPRECATED -I/usr/ports/net/samba35/work/samba-3.5.15/source3/lib -I.. -I../source4 -D_SAMBA_BUILD_=3 -D_SAMBA_BUILD_=3 -fPIC -DPIC -c libsmb/libsmb_setget.c -o libsmb/libsmb_setget.o gmake: *** [libsmb/libsmb_setget.o] Error 1 *** Error code 1 Stop in /usr/ports/net/samba35. *** Error code 1 Stop in /usr/ports/net/samba35. snip Does anyone have any solutions on how I can get Samba installed and resolve the above error? Many thanks in advance. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: can't build Samba 35 on FreeBSD 9.0
On 08/16/2012 04:59, James D. Parra wrote: Hello, I am trying to install Samba35 on FreeBSD 9.0 but I keep getting a build error. portsnap extract portsnap fetch update cd /usr/ports/devel/libtool make deinstall make install clean cd /usr/ports/security/krb5 make deinstall make KRB5_HOME=/usr/local install clean and finally; cd /usr/ports/net/samba35 make KRB5_HOME=/usr/local install clean With my fingers crossed I hoped for the best and yet I received the following error during compiling; snip Compiling libsmb/libsmb_setget.c libsmb/libsmb_setget.c: In function 'smbc_getOptionUseCCache': libsmb/libsmb_setget.c:427: error: 'SMB_CTX_FLAG_USE_CCACHE' undeclared (first use in this function) libsmb/libsmb_setget.c:427: error: (Each undeclared identifier is reported only once libsmb/libsmb_setget.c:427: error: for each function it appears in.) libsmb/libsmb_setget.c: In function 'smbc_setOptionUseCCache': libsmb/libsmb_setget.c:435: error: 'SMB_CTX_FLAG_USE_CCACHE' undeclared (first use in this function) The following command failed: cc -I/usr/local/include -O2 -pipe -DLDAP_DEPRECATED -fno-strict-aliasing -I. -I/usr/ports/net/samba35/work/samba-3.5.15/source3 -I/usr/ports/net/samba35/work/samba-3.5.15/source3/iniparser/src -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -DHAVE_CONFIG_H -I/usr/local/include -I/usr/local/include -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -I./../lib/popt -I/usr/local/include -DLDAP_DEPRECATED -I/usr/ports/net/samba35/work/samba-3.5.15/source3/lib -I.. -I../source4 -D_SAMBA_BUILD_=3 -D_SAMBA_BUILD_=3 -fPIC -DPIC -c libsmb/libsmb_setget.c -o libsmb/libsmb_setget.o gmake: *** [libsmb/libsmb_setget.o] Error 1 *** Error code 1 Stop in /usr/ports/net/samba35. *** Error code 1 Stop in /usr/ports/net/samba35. snip Does anyone have any solutions on how I can get Samba installed and resolve the above error? Many thanks in advance. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Did you already have a ports tree? If so, you only needed to #portsnap fetch update By portsnap extract you are overwriting the existing ports tree, not updating. And I don't think it's a good idea to make deinstall from the ports tree other than the one from which you did make install. Better use pkg_delete (add -f, if it doesn't want to remove the package/port). You may now have leftover from the older installation (say, some libraries). And you reinstalled libtool this way, which is invoked when building libraries. I would first make sure there are no leftovers, all the dependencies are up to date, and then deal with the build problem (if it still exists). And why do you set KRB5_HOME? Will you have kerberos? -Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: can't build Samba 35 on FreeBSD 9.0
On Wed, Aug 15, 2012 at 8:59 PM, James D. Parra jam...@musicreports.comwrote: Hello, I am trying to install Samba35 on FreeBSD 9.0 but I keep getting a build error. The text you gave us gives me the thought you are flailing in the dark. First off, use a port management tool eg portmaster. Learn how to use it fully including regularly reading /usr/ports/UPDATING The handbook has great information on managing ports, I suggest reading it closely if you want FreeBSD to be your friend. In this scenario, you would use portsnap fetch update(assuming you've once a portsnap extract once before) portmaster /usr/ports/net/samba35 The specific error in your message indicates some problem with ccache. What does your /etc/make.conf look like? -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
building Samba on 8.2 fails
Hello, I had installed Samba35 and had it working with PAM and SSH, however after a reboot PAM broke. Kept getting the error; in openpam_load_module(): no /usr/local/lib/pam_winbind.so found The file was actually in that path. Never the less, I tried re-installing; portsnap extract portsnap fetch update cd /usr/ports/devel/libtool make deinstall make install clean cd /usr/ports/security/krb5 make deinstall make KRB5_HOME=/usr/local install clean and finally; cd /usr/ports/net/samba35 make KRB5_HOME=/usr/local install clean With my fingers crossed I hoped for the best and yet I received the following error during compiling; snip Compiling libsmb/libsmb_setget.c libsmb/libsmb_setget.c: In function 'smbc_getOptionUseCCache': libsmb/libsmb_setget.c:427: error: 'SMB_CTX_FLAG_USE_CCACHE' undeclared (first use in this function) libsmb/libsmb_setget.c:427: error: (Each undeclared identifier is reported only once libsmb/libsmb_setget.c:427: error: for each function it appears in.) libsmb/libsmb_setget.c: In function 'smbc_setOptionUseCCache': libsmb/libsmb_setget.c:435: error: 'SMB_CTX_FLAG_USE_CCACHE' undeclared (first use in this function) The following command failed: cc -I/usr/local/include -O2 -pipe -DLDAP_DEPRECATED -fno-strict-aliasing -I. -I/usr/ports/net/samba35/work/samba-3.5.15/source3 -I/usr/ports/net/samba35/work/samba-3.5.15/source3/iniparser/src -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -DHAVE_CONFIG_H -I/usr/local/include -I/usr/local/include -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -I./../lib/popt -I/usr/local/include -DLDAP_DEPRECATED -I/usr/ports/net/samba35/work/samba-3.5.15/source3/lib -I.. -I../source4 -D_SAMBA_BUILD_=3 -D_SAMBA_BUILD_=3 -fPIC -DPIC -c libsmb/libsmb_setget.c -o libsmb/libsmb_setget.o gmake: *** [libsmb/libsmb_setget.o] Error 1 *** Error code 1 Stop in /usr/ports/net/samba35. *** Error code 1 Stop in /usr/ports/net/samba35. snip Does anyone have any solutions on how I can get Samba installed and resolve the above error? Many thanks in advance. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
lpd+samba question
is there any simple way to get data about workstation that prints using lpd from samba? what i need is to get IP/name of workstation that queued a print job to lpd subsystem through samba. or is the only way to change everything to print to lpd directly using lpd protocol? quite a bit of work but possible. I want to do accounting, not just how many pages are printed on each printer (done), but WHO printed it. No problem for local user, but not with samba. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: lpd+samba question
I didn't try by myself, but what about something like print command = /usr/bin/lpr -P%p -J%J -U%I -r %f in smb.conf? I'm sorry to say that you additionally probably have to change /usr/src/usr.sbin/lpr/common_source/ctlinfo.c near line 87 to #define OTHER_USERID_CHARS -_. /* special chars valid in a userid */ and to recompile lpd: cd /usr/src/usr.sbin/lpr make clean make install At less I've to do so to make the dot . a valid character within a user name. Hope this helps and best regards Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, kheu...@gwdg.de On Thu, 19 Jul 2012, Wojciech Puchar wrote: is there any simple way to get data about workstation that prints using lpd from samba? what i need is to get IP/name of workstation that queued a print job to lpd subsystem through samba. or is the only way to change everything to print to lpd directly using lpd protocol? quite a bit of work but possible. I want to do accounting, not just how many pages are printed on each printer (done), but WHO printed it. No problem for local user, but not with samba. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: lpd+samba question
I didn't try by myself, but what about something like print command = /usr/bin/lpr -P%p -J%J -U%I -r %f in smb.conf? I'm sorry to say that you additionally probably have to change /usr/src/usr.sbin/lpr/common_source/ctlinfo.c near line 87 to #define OTHER_USERID_CHARS -_. /* special chars valid in a userid */ and to recompile lpd: cd /usr/src/usr.sbin/lpr make clean make install This is exactly what i asked for. Thank you very much for help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba acting oddly.
On 06-05-12 16:08, Graeme Dargie wrote: I have a problem with Samba, well I think it is samba as one machine I have access to when I try to perform an action like create a new folder in my home folder windows spouts that I need permission and would I like to try again. I guess some background would be useful at this point, I have 3 FreeBSD machines that were running 8.2 AMD 64, some kind souls on this list were able to help me get Samba working using Active Directory, I upgraded to 9.0 when it became available and everything seemed to be fine. I happened to be needing to create a perl script that would allow two users to chat over a network, so rather than fiddling about with Linux and VM`s .. I just used two of my FreeBSD machines, this is when I noticed the issue. Only one machine shows this problem, the others let me happily create / delete stuff in the home folder other shares on the problematic machine are fine. The configuration files for all 3 machines is included below, but I just cannot seen to see why 2 work and 1 does as all three are running Samba35-3.5.6.2 so any help or pointers would be welcome. Regards Graeme Machine Eris - samba works perfectly Smb.conf looks like this [global] workgroup = UNIVERSE realm = UNIVERSE.GALAXY.LCL netbiosname = ERIS interfaces = re0 security = ads allow trusted domains = yes idmap uid = 5000-1 #idmap gid = 15000-2 winbind gid = 5000-1 template homedir = /usr/home/%U template shell = /bin/csh winbind cache time = 3600 winbind nested groups = yes winbind use default domain = yes winbind separator = | winbind enum users = yes winbind enum groups = yes winbind offline logon = yes syslog only = Yes socket options = SO_RCVBUF=131072 SO_SNDBUF=131072 TCP_NODELAY use sendfile = yes read raw = yes use sendfile = yes local master = no use sendfile = yes dns proxy = no username map = /usr/local/samba/usermap # ACL Support map acl inherit = yes #acl group inherit = yes acl group control = yes # LOGGING log file = /var/log/samba/%m log level = 1 max log size = 1000 syslog = 2 ### recycle bin code # bin vfs object = recycle recycle:repository = .RecycleBin/%U recycle:keeptree = Yes recycle:touch = Yes recycle:versions = Yes recycle:maxsize = 0 recycle:exclude = *.tmp recycle:exclude_dir = /tmp recycle:noversions = *.ppt [homes] readonly=no other shares below Machine Proteus - samba working a charm ... [global] workgroup = UNIVERSE realm = UNIVERSE.GALAXY.LCL netbiosname = PROTEUS interfaces = re0 security = ads allow trusted domains = yes idmap uid = 5000-1 #idmap gid = 15000-2 winbind gid = 5000-1 template homedir = /usr/home/%U template shell = /bin/csh winbind cache time = 3600 winbind nested groups = yes winbind use default domain = yes winbind separator = | winbind enum users = yes winbind enum groups = yes winbind offline logon = yes syslog only = Yes socket options = TCP_NODELAY SO_RCVBUF=65536 SO_SNDBUF=65536 use sendfile = yes read raw = yes use sendfile = yes local master = no use sendfile = yes dns proxy = no username map = /usr/local/samba/usermap # ACL Support map acl inherit = yes #acl group inherit = yes acl group control = yes # LOGGING log file = /var/log/samba/%m log level = 1 max log size = 1000 syslog = 2 [homes] read only = No Both of these work with no issues. However Amalthea which is the machine showing the problem, the smb.conf is the following [global] workgroup = UNIVERSE realm = UNIVERSE.GALAXY.LCL netbiosname = amalthea interfaces = nfe0 security = ads allow trusted domains = yes idmap uid = 5000-1 #idmap gid = 15000-2 winbind gid = 5000-1 template homedir = /usr/home/%U template shell = /bin/csh winbind cache time = 3600 winbind nested groups = yes winbind use default domain = yes winbind separator = | winbind enum users = yes winbind enum groups = yes winbind offline logon = yes syslog only = Yes socket options = TCP_NODELAY SO_RCVBUF=65536 SO_SNDBUF=65536 use sendfile = yes read raw = yes use sendfile = yes local master = no use sendfile = yes dns proxy = no username map = /usr/local/samba/usermap # ACL Support map acl inherit = yes #acl group inherit = yes acl group control = yes # LOGGING log file = /var/log/samba/%m log level = 1 max log size = 1000syslog = 2 ### recycle bin code # bin vfs object = recycle recycle:repository = .RecycleBin/%U recycle:keeptree = Yes recycle:touch = Yes recycle:versions = Yes recycle:maxsize = 0 recycle:exclude = *.tmp recycle:exclude_dir = /tmp recycle:noversions = *.ppt [homes] readonly=no ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org This is not the solution, but there are some things i
Samba acting oddly.
I have a problem with Samba, well I think it is samba as one machine I have access to when I try to perform an action like create a new folder in my home folder windows spouts that I need permission and would I like to try again. I guess some background would be useful at this point, I have 3 FreeBSD machines that were running 8.2 AMD 64, some kind souls on this list were able to help me get Samba working using Active Directory, I upgraded to 9.0 when it became available and everything seemed to be fine. I happened to be needing to create a perl script that would allow two users to chat over a network, so rather than fiddling about with Linux and VM`s .. I just used two of my FreeBSD machines, this is when I noticed the issue. Only one machine shows this problem, the others let me happily create / delete stuff in the home folder other shares on the problematic machine are fine. The configuration files for all 3 machines is included below, but I just cannot seen to see why 2 work and 1 does as all three are running Samba35-3.5.6.2 so any help or pointers would be welcome. Regards Graeme Machine Eris - samba works perfectly Smb.conf looks like this [global] workgroup = UNIVERSE realm = UNIVERSE.GALAXY.LCL netbiosname = ERIS interfaces = re0 security = ads allow trusted domains = yes idmap uid = 5000-1 #idmap gid = 15000-2 winbind gid = 5000-1 template homedir = /usr/home/%U template shell = /bin/csh winbind cache time = 3600 winbind nested groups = yes winbind use default domain = yes winbind separator = | winbind enum users = yes winbind enum groups = yes winbind offline logon = yes syslog only = Yes socket options = SO_RCVBUF=131072 SO_SNDBUF=131072 TCP_NODELAY use sendfile = yes read raw = yes use sendfile = yes local master = no use sendfile = yes dns proxy = no username map = /usr/local/samba/usermap # ACL Support map acl inherit = yes #acl group inherit = yes acl group control = yes # LOGGING log file = /var/log/samba/%m log level = 1 max log size = 1000 syslog = 2 ### recycle bin code # bin vfs object = recycle recycle:repository = .RecycleBin/%U recycle:keeptree = Yes recycle:touch = Yes recycle:versions = Yes recycle:maxsize = 0 recycle:exclude = *.tmp recycle:exclude_dir = /tmp recycle:noversions = *.ppt [homes] readonly=no other shares below Machine Proteus - samba working a charm ... [global] workgroup = UNIVERSE realm = UNIVERSE.GALAXY.LCL netbiosname = PROTEUS interfaces = re0 security = ads allow trusted domains = yes idmap uid = 5000-1 #idmap gid = 15000-2 winbind gid = 5000-1 template homedir = /usr/home/%U template shell = /bin/csh winbind cache time = 3600 winbind nested groups = yes winbind use default domain = yes winbind separator = | winbind enum users = yes winbind enum groups = yes winbind offline logon = yes syslog only = Yes socket options = TCP_NODELAY SO_RCVBUF=65536 SO_SNDBUF=65536 use sendfile = yes read raw = yes use sendfile = yes local master = no use sendfile = yes dns proxy = no username map = /usr/local/samba/usermap # ACL Support map acl inherit = yes #acl group inherit = yes acl group control = yes # LOGGING log file = /var/log/samba/%m log level = 1 max log size = 1000 syslog = 2 [homes] read only = No Both of these work with no issues. However Amalthea which is the machine showing the problem, the smb.conf is the following [global] workgroup = UNIVERSE realm = UNIVERSE.GALAXY.LCL netbiosname = amalthea interfaces = nfe0 security = ads allow trusted domains = yes idmap uid = 5000-1 #idmap gid = 15000-2 winbind gid = 5000-1 template homedir = /usr/home/%U template shell = /bin/csh winbind cache time = 3600 winbind nested groups = yes winbind use default domain = yes winbind separator = | winbind enum users = yes winbind enum groups = yes winbind offline logon = yes syslog only = Yes socket options = TCP_NODELAY SO_RCVBUF=65536 SO_SNDBUF=65536 use sendfile = yes read raw = yes use sendfile = yes local master = no use sendfile = yes dns proxy = no username map = /usr/local/samba/usermap # ACL Support map acl inherit = yes #acl group inherit = yes acl group control = yes # LOGGING log file = /var/log/samba/%m log level = 1 max log size = 1000syslog = 2 ### recycle bin code # bin vfs object = recycle recycle:repository = .RecycleBin/%U recycle:keeptree = Yes recycle:touch = Yes recycle:versions = Yes recycle:maxsize = 0 recycle:exclude = *.tmp recycle:exclude_dir = /tmp recycle:noversions = *.ppt [homes] readonly=no ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Samba 3.6.4 winbindd
Has anyone out there gotten winbindd from Samba 3.6.anything to work on FreeBSD 9.0-STABLE? It starts up with no obvious problems--although with Samba's usual cryptic error messages it's hard for me to tell--and then just sits there doing nothing. Wbinfo commands time out and pam_winbind.so doesn't work. When I run /usr/local/etc/rc.d/samba stop, it hangs waiting for winbindd to die, and I have to kill -KILL winbindd. I'm using security = domain. Other settings, logs, etc. available upon request. I've had to drop back to Samba 3.5.14_1 to get most things to work, but I really need to go to 3.6.* for the NTLMv2 support. -- J. Porter Clark j...@porterclark.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Mounting a samba share on boot?
___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mounting a samba share on boot?
On Sun, 11 Mar 2012 20:20:15 +0400, Льоша Лоїк wrote:
{ nothing }
Even though you wrote nothing, I assume that the subject
Mounting a samba share on boot? contains your question.
Answer:
You can put the required line in /etc/fstab, and provide
access details (workgroup, user, password and such stuff)
in /etc/nsmb.conf.
See the manpages for fstab, nsmb.conf and mount_smbfs for
details.
If you encounter problems with networking _not_ being up
when the mount is performed, see the late option described
in man mount. This option is often used for network-mounted
file systems.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0, Samba and two NICs
On Fri, Feb 24, 2012 at 3:45 PM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: On 02/24/12 21:39, Ronny Mandal wrote: Hi! I have been running Samba on FreeBSD 9.0 with a wireless card. A share is connected to my W7 computer. To get more speed between the computers, I decided to activate the 1GBit- Ethernet on the FreeBSD and establish a direct connection (cross-link) to the W7. I gave the new connection a static IP/subnet: 10.0.0.2/255.0.0.0 for the FreeBSD and 10.0.0.1/255.0.0.0 for the W7. SSH works fine, however Samba is utilizing the wireless card. My smb.conf looks something like this: .. ;The 192-address is the wireless, ath0. 10.0.0.2 is age0 interfaces = 127.0.0.1 192.168.0.232 10.0.0.2 bind interfaces only = yes ; the two latter is the IPs of the W7 hosts allow = 127.0.0.1 192.168.0.117 10.0.0.1 If I remove the 192* in the hosts allow, my W7 looses access via smb. netstat tells me that it is listening to both interfaces. What might be wrong? What address is the w7 using? If it is using 192.X, that could be the problem. That or some variation... such as the w7 using wireless and 192.x? Sorry about the late answer and missing info. The W7 is using both, i.e. wireless and wired. Strangely enough, it works now. Here is what I did: The interface parameter; I put the 10.* before the 192.* and stopped and started the samba-service. After that, the wired card were utilized when I copied to and from the share. interfaces = 192.168.0.232 10.0.0.2 127.0.0.1 changed to interfaces = 10.0.0.2 192.168.0.232 127.0.0.1 (I tried this earlier, but it seems that /usr/local/etc/rc.d/samba restart did not properly re-read the configuration.) Regards, Ronny Mandal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
9.0, Samba and two NICs
Hi! I have been running Samba on FreeBSD 9.0 with a wireless card. A share is connected to my W7 computer. To get more speed between the computers, I decided to activate the 1GBit- Ethernet on the FreeBSD and establish a direct connection (cross-link) to the W7. I gave the new connection a static IP/subnet: 10.0.0.2/255.0.0.0 for the FreeBSD and 10.0.0.1/255.0.0.0 for the W7. SSH works fine, however Samba is utilizing the wireless card. My smb.conf looks something like this: .. ;The 192-address is the wireless, ath0. 10.0.0.2 is age0 interfaces = 127.0.0.1 192.168.0.232 10.0.0.2 bind interfaces only = yes ; the two latter is the IPs of the W7 hosts allow = 127.0.0.1 192.168.0.117 10.0.0.1 If I remove the 192* in the hosts allow, my W7 looses access via smb. netstat tells me that it is listening to both interfaces. What might be wrong? Thanks. -- Best regards, Ronny Mandal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.0, Samba and two NICs
On 02/24/12 21:39, Ronny Mandal wrote: Hi! I have been running Samba on FreeBSD 9.0 with a wireless card. A share is connected to my W7 computer. To get more speed between the computers, I decided to activate the 1GBit- Ethernet on the FreeBSD and establish a direct connection (cross-link) to the W7. I gave the new connection a static IP/subnet: 10.0.0.2/255.0.0.0 for the FreeBSD and 10.0.0.1/255.0.0.0 for the W7. SSH works fine, however Samba is utilizing the wireless card. My smb.conf looks something like this: .. ;The 192-address is the wireless, ath0. 10.0.0.2 is age0 interfaces = 127.0.0.1 192.168.0.232 10.0.0.2 bind interfaces only = yes ; the two latter is the IPs of the W7 hosts allow = 127.0.0.1 192.168.0.117 10.0.0.1 If I remove the 192* in the hosts allow, my W7 looses access via smb. netstat tells me that it is listening to both interfaces. What might be wrong? What address is the w7 using? If it is using 192.X, that could be the problem. That or some variation... such as the w7 using wireless and 192.x? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
need a weird samba configuration
Any Samba gurus here? I have a file server running samba34-3.4.14 as a domain member server with security = domain. winbindd is not started and all Windows users are resolved to Unix uids/gids via getpwnam() as described in http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/idmapper.html#id2604553 Now I need to start winbindd for other purposes, not connected with smbd and the file service. How do I configure smb.conf so that smbd should not consult winbind and should continue using getpwnam() for Windows logon name - Unix uid/gid mapping? In other words, how do I disable the idmap functionality and use existing Unix uids/gids with winbindd running? TIA for any input. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Files End Up Read-Only With Samba
I am running FreeBSD-8.2-STABLE-amd64, last update was a few weeks ago. I run Samba-3.6 on this server and it has served me well for my Windows clients to store and share files. All was working fine until recently I've began to notice that whenever I save a file to this server, they always end up with permissions which force me to open them in RO mode when I access them later. The message I'm seeing on the Windows clients is that the file is locked by another user. I check and the owners of the file are root:my_user_account. The permissions are set to rwxr-xr-x. I'm not sure why the root account shows up in the ownership and like I said this was working fine before. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Default Samba port?
From: Robert Simmons rsimmo...@gmail.com To: freebsd-questions@freebsd.org Sent: Sunday, November 13, 2011 10:36 AM Subject: Re: Default Samba port? On Sun, Nov 13, 2011 at 7:37 AM, Peter Harrison four.harris...@googlemail.com wrote: Can anyone advise me the appropriate Samba port to install - the handbook refers to samba34, but I see samba35 and samba36 in in ports. This is for a home server, so I'm not necessarily looking for production standard, but something that just works on RELEASE-8.2 amd64. samba36 is the current stable version. The other two are kept for legacy compatibility. 35 and 34 are the last version in those branches. Don't worry about them. The handbook has not been updated for two major revisions of samba. This is a comment for the others on the list, not directly at you: maybe ports like this should have a directory samba that always points to the most recent stable version. Then the handbook would not need to be updated to reflect version changes like this. It would only need to be updated if the actual instructions change or become outdated? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I second the motion. Then when you do something like whereis samba, it won't come back empty and force you to search in /usr/ports for the desired port directory. As for the original question, I'd install samba36, which is the latest port. The configuration is still the same as previous releases so go for the latest one. Samba has some security issues but it rocks as a file server for *nix machines. I've used it with great success to allow M$ clients to share files. I do not use it for print services however, only file sharing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Default Samba port?
Sorry for top posting - my 'phone makes it awkward. Thanks for the s= uggestion. What default package would be delivered in this way on 8.2-R? -- Peter Harrison _ On 13 Nov 2011 14:39, pete wright nomadlo= g...@gmail.com wrote: On Sun, Nov 13, 2011 at 4:37 AM, Pe= ter Harrison four.harris...@googlemail.com wrote: = Hello list, Can anyone advise me the appropriate Samb= a port to install - the handbook refers to samba34, but I see samba35 and s= amba36 in in ports. This is for a home server, so I'm not necessarily looki= ng for production standard, but something that just works on RELEASE-8.2amd64. your best bet may be to install a prebuilt p= ackage via: pgk_add -r samba that is unless you need som= e non-standard knobs tuned. -pete -- pete wright www.nycbug.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Default Samba port?
Sorry for top posting - curse you 'phone mail client! OK that's exac= tly what I needed to know. Thanks. -- Peter Harrison _ On 13 Nov= 2011 15:37, Robert Simmons rsimmo...@gmail.com wrote: On Sun, Nov 13, 2011 at 7:37 AM, Peter Harrison four.harrisons= @googlemail.com wrote: Can anyone advise me the appropriate = Samba port to install - the handbook refers to samba34, but I see samba35 a= nd samba36 in in ports. This is for a home server, so I'm not necessarily l= ooking for production standard, but something that just works on RELEASE-= 8.2 amd64. samba36 is the current stable version. The other t= wo are kept for legacy compatibility. 35 and 34 are the last version= in those branches. Don't worry about them. The handbook has not be= en updated for two major revisions of samba. This is a c= omment for the others on the list, not directly at you: maybe ports l= ike this should have a directory samba that always points to the most= recent stable version. Then the handbook would not need to be updat= ed to reflect version changes like this. It would only need to be up= dated if the actual instructions change or become outdated? ___= freebsd-questions@freebs= d.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-= questions To unsubscribe, send any mail to freebsd-questions-unsubsc r...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Default Samba port?
Hello list, Can anyone advise me the appropriate Samba port to install - the handbook refers to samba34, but I see samba35 and samba36 in in ports. This is for a home server, so I'm not necessarily looking for production standard, but something that just works on RELEASE-8.2 amd64. Thanks, Peter Harrison.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Default Samba port?
On Sun, Nov 13, 2011 at 4:37 AM, Peter Harrison four.harris...@googlemail.com wrote: Hello list, Can anyone advise me the appropriate Samba port to install - the handbook refers to samba34, but I see samba35 and samba36 in in ports. This is for a home server, so I'm not necessarily looking for production standard, but something that just works on RELEASE-8.2 amd64. your best bet may be to install a prebuilt package via: pgk_add -r samba that is unless you need some non-standard knobs tuned. -pete -- pete wright www.nycbug.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Default Samba port?
On Sun, Nov 13, 2011 at 7:37 AM, Peter Harrison four.harris...@googlemail.com wrote: Can anyone advise me the appropriate Samba port to install - the handbook refers to samba34, but I see samba35 and samba36 in in ports. This is for a home server, so I'm not necessarily looking for production standard, but something that just works on RELEASE-8.2 amd64. samba36 is the current stable version. The other two are kept for legacy compatibility. 35 and 34 are the last version in those branches. Don't worry about them. The handbook has not been updated for two major revisions of samba. This is a comment for the others on the list, not directly at you: maybe ports like this should have a directory samba that always points to the most recent stable version. Then the handbook would not need to be updated to reflect version changes like this. It would only need to be updated if the actual instructions change or become outdated? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Samba/CIFS, what I'm serving?
Hi, I've installed Samba on my server to share some directories to Windows machines. It is working very well. Since a couple of days, I noted the whole server's performance was slow, then I started to check open ports, stopped some services, until samba was the only service still working (my wife's windows box had some shared files opened). I wonder if there's a way to configure CIFS to speed this up. Leonardo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problem with Samba
I probably should be asking this on the Samba forum; however, I thought I would start here. A few days ago the Samba shares on my FreeBSD-8.2 amd64 machine stopped showing up on my Windows machines. All of them to be precise. I removed all of the old Samba logs after having shut it down and then restarted it. This error message is being printed in the log.nmdb file: [2011/10/08 12:30:30, 0] nmbd/nmbd_mynames.c:35(my_name_register_failed) my_name_register_failed: Failed to register my name SCORPIO20 on subnet 192.168.1.101. [2011/10/08 12:30:30, 0] nmbd/nmbd_namelistdb.c:307(standard_fail_register) standard_fail_register: Failed to register/refresh name SCORPIO20 on subnet 192.168.1.101 [2011/10/08 12:30:30, 0] nmbd/nmbd_mynames.c:35(my_name_register_failed) my_name_register_failed: Failed to register my name SCORPIO03 on subnet 192.168.1.101. [2011/10/08 12:30:30, 0] nmbd/nmbd_namelistdb.c:307(standard_fail_register) standard_fail_register: Failed to register/refresh name SCORPIO03 on subnet 192.168.1.101 [2011/10/08 12:30:30, 0] nmbd/nmbd_mynames.c:35(my_name_register_failed) my_name_register_failed: Failed to register my name SCORPIO00 on subnet 192.168.1.101. [2011/10/08 12:30:30, 0] nmbd/nmbd_namelistdb.c:307(standard_fail_register) standard_fail_register: Failed to register/refresh name SCORPIO00 on subnet 192.168.1.101 This only started a few days ago. I do need to get this network back up however. -- Carmel ✌ carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem with Samba (SOLVED)
I discover the problem. A soon to be former employee decided to change the name of the router to the same name as the FreeBSD server. Why, I do not know. Once I discovered this, I reverted the name to its original state, rebooted the router and all is well. -- Carmel ✌ carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba
On Wed, Oct 5, 2011 at 11:29 PM, Kruppa, Peter Ulrich ulr...@pukruppa.de wrote: [snip] Just one idea: did you activate the firewall on your Windows client somehow? That might happen during some kind of updates and block samba from client side. Nope, SEP says 139 is allowed, the one thing I haven't done yet is a reboot of that windows client, I will try that later today. -- Chris Brennan A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/ GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problem with samba 35
Hi; System: FBSD 8.2 STABLE amd64 2011/10/05 11:26:25.632002, 0] smbd/close.c:296(close_remove_share_mode) smbd[40272]: close_remove_share_mode: Could not get share mode lock for file I keep getting these messages and the system at the store (win) that uses the shares keep getting all sorts of problems problems. Tried everything I could think of without success !!! This didn't happen with samba 3.0.36. Can someone help me, please ?? Thanks Src Ports updated on 04/10/2011 smb.conf [global] netbios name = LosanGW workgroup = LOSAN server string = LOSAN Inet Server log file = /var/log/samba-log.%m max log size = 50 max xmit = 65535 domain master = yes local master = yes preferred master = yes ; os level = 65 name resolve order = host wins bcast security = share ; deadtime = 15 socket options = TCP_NODELAY dns proxy = No hosts allow = 10.10.10., 127. interfaces = 10.10.10.1 share modes = yes lock directory = /usr/local/etc/samba/locks [deposito] comment = Losan path = /deposito read only = No guest ok = Yes public = yes -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Samba
Greetings! I have FreeBSD8.2 running on an x86 box and samba sharing a hardware raid1 array with zfs ontop and something strange happened today. Samba stopped accepting connections for some reason and I can't figure out why. I'm not sure if this is freebsd-specific or if it's a samba-only issue. But I can note that it had been working fine for months, the box itself has been up for 23 days w/o incident. I don't get it, it was working this morning, I changed nothing (in fact, this is the first time I logged in as root in several days and there is no outside access to this box). I connected to it this morning to map it's shares on my laptop and then noticed I couldn't connect to those very same shares on my desktop. As you can see, samba is running and the port is open [root@ziggy ~]# ps auxf | grep -e smbd -e nmbd root 42252 0.0 0.2 7636 3704 ?? Ss3:53PM 0:00.07 /usr/local/sbin/nmbd -D -s /usr/local/etc/smb.conf root 42256 0.0 0.4 14616 7844 ?? Is3:53PM 0:00.02 /usr/local/sbin/smbd -D -s /usr/local/etc/smb.conf root 42258 0.0 0.4 14616 7776 ?? I 3:53PM 0:00.00 /usr/local/sbin/smbd -D -s /usr/local/etc/smb.conf root 42472 0.0 0.1 3500 1248 0 S+4:05PM 0:00.00 grep -e smbd -e nmbd [root@ziggy ~]# nmap -sT -p139 ziggy Starting Nmap 5.59BETA1 ( http://nmap.org ) at 2011-10-05 16:05 EDT Nmap scan report for ziggy (192.168.0.3) Host is up (0.0022s latency). rDNS record for 192.168.0.3: ziggy.xaerolimit.net PORTSTATE SERVICE 139/tcp open netbios-ssn Nmap done: 1 IP address (1 host up) scanned in 0.09 seconds [root@ziggy ~]# So I don't get what gives. -- Chris Brennan A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/ GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba
On 05.10.2011 22:08, Chris Brennan wrote: Greetings! I have FreeBSD8.2 running on an x86 box and samba sharing a hardware raid1 array with zfs ontop and something strange happened today. Samba stopped accepting connections for some reason and I can't figure out why. I'm not sure if this is freebsd-specific or if it's a samba-only issue. But I can note that it had been working fine for months, the box itself has been up for 23 days w/o incident. I don't get it, it was working this morning, I changed nothing (in fact, this is the first time I logged in as root in several days and there is no outside access to this box). I connected to it this morning to map it's shares on my laptop and then noticed I couldn't connect to those very same shares on my desktop. As you can see, samba is running and the port is open Just one idea: did you activate the firewall on your Windows client somehow? That might happen during some kind of updates and block samba from client side. Greetings Peter. [root@ziggy ~]# ps auxf | grep -e smbd -e nmbd root 42252 0.0 0.2 7636 3704 ?? Ss3:53PM 0:00.07 /usr/local/sbin/nmbd -D -s /usr/local/etc/smb.conf root 42256 0.0 0.4 14616 7844 ?? Is 3:53PM 0:00.02 /usr/local/sbin/smbd -D -s /usr/local/etc/smb.conf root 42258 0.0 0.4 14616 7776 ?? I 3:53PM 0:00.00 /usr/local/sbin/smbd -D -s /usr/local/etc/smb.conf root 42472 0.0 0.1 3500 1248 0 S+4:05PM 0:00.00 grep -e smbd -e nmbd [root@ziggy ~]# nmap -sT -p139 ziggy Starting Nmap 5.59BETA1 ( http://nmap.org ) at 2011-10-05 16:05 EDT Nmap scan report for ziggy (192.168.0.3) Host is up (0.0022s latency). rDNS record for 192.168.0.3: ziggy.xaerolimit.net PORT STATE SERVICE 139/tcp open netbios-ssn Nmap done: 1 IP address (1 host up) scanned in 0.09 seconds [root@ziggy ~]# So I don't get what gives. -- Chris Brennan A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/ GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Peter Ulrich Kruppa Wuppertal Germany ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Samba question
Hi All I am sure there is a simple answer to this but I google has not overly helped. I am trying to mount a samba share that is on a FreeBSD 8.2 server to another FreeBSD 8.2 server, Mount_smbfs -I IP //user@host/share /mountpoint It then asks for a password, I enter the users password and then get mount_smbfs: unable to open connection: syserr = Authentication error Dmesg is showing smb_co_lock: recursive lock for object 1 I have samba integrated with Active Directory, so I then thought ah maybe adding the user to AD would help, so I have done so using the same password etc still no joy, I have make sure the user has access rights on the samba share, restarted samba and the same error persists, any ideas ? Regards Graeme ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba question
On Sat, 10 Sep 2011 11:53:48 +0100, Graeme Dargie wrote: I am trying to mount a samba share that is on a FreeBSD 8.2 server to another FreeBSD 8.2 server, Mount_smbfs -I IP //user@host/share /mountpoint It then asks for a password, I enter the users password and then get mount_smbfs: unable to open connection: syserr = Authentication error Dmesg is showing smb_co_lock: recursive lock for object 1 I have samba integrated with Active Directory, so I then thought ah maybe adding the user to AD would help, so I have done so using the same password etc still no joy, I have make sure the user has access rights on the samba share, restarted samba and the same error persists, any ideas ? Sorry, my indivudal knowledge on Windows related things is very limited, but maybe you need to add some information into /etc/nsmb.conf? Maybe like this: [default] workgroup=YOUR_WORKGROUP_NAME [SERVERNAME] addr=192.168.2.2 [SERVERNAME:USERNAME] password=TOPSECRET where SERVERNAME and USERNAME correspond to the server's name and the username you use to access the share (with the proper password). See man nsmb.conf for details. Parts of those information should then be reflected in /etc/fstab, maybe like this: //user@SERVERNAME/share /smb/share smbfs rw,noauto 0 0 This should allow you to use # mount /smb/share a bit easier (and automatically, if desired). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba question
Polytropon wrote: On Sat, 10 Sep 2011 11:53:48 +0100, Graeme Dargie wrote: I am trying to mount a samba share that is on a FreeBSD 8.2 server to another FreeBSD 8.2 server, Mount_smbfs -I IP //user@host/share /mountpoint It then asks for a password, I enter the users password and then get mount_smbfs: unable to open connection: syserr = Authentication error Dmesg is showing smb_co_lock: recursive lock for object 1 I have samba integrated with Active Directory, so I then thought ah maybe adding the user to AD would help, so I have done so using the same password etc still no joy, I have make sure the user has access rights on the samba share, restarted samba and the same error persists, any ideas ? Sorry, my indivudal knowledge on Windows related things is very limited, but maybe you need to add some information into /etc/nsmb.conf? Maybe like this: [default] workgroup=YOUR_WORKGROUP_NAME [SERVERNAME] addr=192.168.2.2 [SERVERNAME:USERNAME] password=TOPSECRET where SERVERNAME and USERNAME correspond to the server's name and the username you use to access the share (with the proper password). See man nsmb.conf for details. Parts of those information should then be reflected in /etc/fstab, maybe like this: //user@SERVERNAME/share /smb/share smbfs rw,noauto 0 0 This should allow you to use # mount /smb/share a bit easier (and automatically, if desired). Although it has been ages since I played with this, one thing I do recall: It matters that where indicated above the characters _must_ be in upper case. When I used to use such a setup I found it wouldn't work without it. Never knew exactly quite why. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Samba and Active Directory
Hello list, I have tried putting this on the samba mail list seems that no knows or is willing to share, having got good help with freebsd on here before, I figured its worth a shot, apologises if it is not 100% OT. I am sure this has been asked a million times but here goes for +1 I am looking for help, or pointers to a good resource to get FreeBSD 8.2 and Samba 3.5 working within a Win 2008 AD environment, the samba how to got me so far, but I am missing something somewhere as none of the shares defined within the smb.conf will connect without asking for a username and password. Regards Graeme ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Samba and Active Directory
Hello list, I have tried putting this on the samba mail list seems that no knows or is willing to share, having got good help with freebsd on here before, I figured its worth a shot, apologises if it is not 100% OT. I am sure this has been asked a million times but here goes for +1 I am looking for help, or pointers to a good resource to get FreeBSD 8.2 and Samba 3.5 working within a Win 2008 AD environment, the samba how to got me so far, but I am missing something somewhere as none of the shares defined within the smb.conf will connect without asking for a username and password. Regards Graeme I made a little effort helping somebody on the FreeBSD forum. http://forums.freebsd.org/showthread.php?t=20007 Use the directions i (Sylhouette) made in the above thread. It should get you into a running state. Regards Johan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Timing out SAMBA authentication
Hi. I am connecting to a Samba server from a mac running OSX 10.6.6 on my LAN and up until about a month ago it has been running smoothly. The sever is appearing in Finder but when connecting I get asked my username and password. After entering my details I get Connecting for about 5-10 seconds before the shares are presented, then I am able to mount and work with the shares. Interestingly if I don't mot the share quickly the mac reports the share is no longer available? This evening I have been doing some diagnosis to see whats happening, I opened a terminal session on the samba server and to connect to the share using; smbclient localhost\\[share] I get asked the password, after 20 seconds the connection fails with the error: Receiving SMB: Server stopped responding session setup failed: Call timed out: server did not respond after 2 milliseconds I'm assuming this is why there is a delay in mounting the share though my Mac. Im pretty sure I haven't changed anything. I have googled the web and the only constructive thing I have come across so far is the encrypt password entry in smb.conf. I tried this but made no difference. smb.conf: [global] netbios name=Leopard workgroup=WORKGROUP security = user load printers = no log file = /var/log/samba.log max logsize = 50 time server = yes read raw = yes write raw = yes socket options = TCP_NODELAY IPTOS_LOWDELAY wins support = yes local master = yes domain master = yes os level = 65 [homes] read only=no guest ok=no browsable=no [share] path=/usr/home/share read only=no guest ok=no force group = share security mask = 0660 force security mode = 660 directory security mask = 0770 force directory security mode = 0770 Any advise would be appreciated especially if someone has resolved this. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: the GIMP and Samba
On Wed, 5 Jan 2011 23:36:12 +0100 Polytropon free...@edvax.de wrote: Welcome to the glory of rapid application development and modern programming! :-) Somebody could write a letter to the ACM: Dynamic Linking Considered Harmful ... or sth in that vicinity -- Christopher J. Ruwe TZ GMT + 1 signature.asc Description: PGP signature
the GIMP and Samba
Can someone enlighten me as to why the GIMP package would require libsmbclient? This strikes me as the very height of software bloat absurdity. Maybe I'm missing something. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpXAcYF9nPLh.pgp Description: PGP signature
Re: the GIMP and Samba
On Wed, 5 Jan 2011 15:19:39 -0700, Chad Perrin per...@apotheon.com wrote: Can someone enlighten me as to why the GIMP package would require libsmbclient? This strikes me as the very height of software bloat absurdity. Maybe I'm missing something. Welcome to the glory of rapid application development and modern programming! :-) According to your question: I am confident that the SMB dependency is brought into Gimp by the gutenprint module (can't even tell you exactly what it does, may have something to do with CUPS I also don't have any use for). CUPS seems to be hardcoded into Gimp even if you don't use it (due to a normal printer). The SMB dependency is also used by several Gnome-related dependencies, such as Gnome-VFS, a part of nearly every file open dialog in Gtk. The /var/db/pkg/portname/+REQUIRED_BY file tells you about the next higher stage of dependency (maybe another library or a primary program - the thing you actually want to use). Note that observations like this are the reason you have to constantly buy a new computer in order to keep doing the same things at the same average speed. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: the GIMP and Samba
There's prolly a 10 line function the developer didn't want to write. I've seen some case where it takes more code to link to other packages than just write what's needed. Drives me crazy to have to install apps that have nothing to do with the app I really need... -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Chad Perrin Sent: Wednesday, January 05, 2011 4:20 PM To: FreeBSD Questions Subject: the GIMP and Samba Can someone enlighten me as to why the GIMP package would require libsmbclient? This strikes me as the very height of software bloat absurdity. Maybe I'm missing something. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: the GIMP and Samba
On Wed, 5 Jan 2011, Chad Perrin wrote: Can someone enlighten me as to why the GIMP package would require libsmbclient? This strikes me as the very height of software bloat absurdity. Maybe I'm missing something. package = pre-built, off-the-rack, one-size-fits-all. I don't know where the dependency comes in, but gimp withtout libsmbclient works here. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: the GIMP and Samba
Quoth Warren Block on Wednesday, 05 January 2011: On Wed, 5 Jan 2011, Chad Perrin wrote: Can someone enlighten me as to why the GIMP package would require libsmbclient? This strikes me as the very height of software bloat absurdity. Maybe I'm missing something. package = pre-built, off-the-rack, one-size-fits-all. I don't know where the dependency comes in, but gimp withtout libsmbclient works here. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Gutenprint support is an OPTION in gimp -- perhaps turning that off relieves you of the dependency? -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpyDMxKd1loL.pgp Description: PGP signature
Re: the GIMP and Samba
On Wed, 5 Jan 2011 15:03:02 -0800, Chip Camden sterl...@camdensoftware.com wrote: Gutenprint support is an OPTION in gimp -- perhaps turning that off relieves you of the dependency? Or maybe it's an option to gnomevfs... or something related to Gtk 2 in general... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: the GIMP and Samba
On Thu, 6 Jan 2011, Polytropon wrote: On Wed, 5 Jan 2011 15:03:02 -0800, Chip Camden sterl...@camdensoftware.com wrote: Gutenprint support is an OPTION in gimp -- perhaps turning that off relieves you of the dependency? Or maybe it's an option to gnomevfs... or something related to Gtk 2 in general... It's not gutenprint (which I have installed), at least not directly. devel/gnome-vfs does have a Samba option, which is disabled here. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD samba+winbind
Hi! Thanks for your reply! Sorry, but that didn't help. I even tried installing samba 3.4 (also form ports). With the same configuration as Samba 3.5 there was no idmapping at all. I'll try to raise loglevel to see what happens. With Samba 3.5 and loglevel 10 there were no significant errors and I think the problem is with nssd and nss_winbind.so (some specific behavior for getting all users - getent). Best wishes, Ivo Timur I. Bakeyev wrote: Hi, Ivo! Just a wild guess - could it be the result of moving lockdir in Samba3.5 port from /var/db/samba34 back to /var/db/samba ? Can you check, that, by renaming appropriate directory? Regards, Timur. On Mon, Nov 22, 2010 at 10:15 PM, Ivo Karabojkov i...@kit-bg.com wrote: Perhaps I couldn't get any attention with my problem or I couldn't explain it in enough details. As you probably read, IDMapping works OK. It seems that my problem occurs in nsswitch. In my /etc/nsswitch.conf I have: group: files winbind #group_compat: nis hosts: files dns networks: files passwd: files winbind #passwd_compat: nis shells: files services: compat services_compat: nis protocols: files rpc: files wbinfo -u / -g / -i DOMAIN_user works OK. Name service switch works almost OK, since system utilities like id, pw /usershow/, chown, ls resolve domain usernames - IDMapped UIDs OK. But getent passwd and getent group return only local (system) users /groups. Any clue how to make this work too? Ivo Karabojkov wrote: Dear Sirs, I am having troubles with IDMapping users from Server 2003 AD to my FreeBSD 8.1 Samba 3.5. Well, most of Samba documentation should be considered outdated, I had total failure with RID backend for IDMap. The only working (so far) for me is the default: tdb. I have set nsswitch.conf, pam.d and so on correctly. And here is my problem: everything works almost fine, wbinfo shows my domain accounts, I am able to set these accounts and groups as owners of files. Commands like ls, chown, id show AD accounts correctly. pw, getent - show only local system accounts. I need Samba only for file sharing with ACLs, no PAM authentication or something more. So, technically, it works but since I can't see ALL accounts with getent I think something is wrong. IDMapped accounts are with uid and gid 1 I think I am missing something very small and simple, so I hope someone will help me! Thanks in advance, Ivo -- View this message in context: http://old.nabble.com/FreeBSD-samba%2Bwinbind-tp30252640p30282675.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- View this message in context: http://old.nabble.com/FreeBSD-samba%2Bwinbind-tp30252640p30366636.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD samba+winbind
Hi, Ivo! Just a wild guess - could it be the result of moving lockdir in Samba3.5 port from /var/db/samba34 back to /var/db/samba ? Can you check, that, by renaming appropriate directory? Regards, Timur. On Mon, Nov 22, 2010 at 10:15 PM, Ivo Karabojkov i...@kit-bg.com wrote: Perhaps I couldn't get any attention with my problem or I couldn't explain it in enough details. As you probably read, IDMapping works OK. It seems that my problem occurs in nsswitch. In my /etc/nsswitch.conf I have: group: files winbind #group_compat: nis hosts: files dns networks: files passwd: files winbind #passwd_compat: nis shells: files services: compat services_compat: nis protocols: files rpc: files wbinfo -u / -g / -i DOMAIN_user works OK. Name service switch works almost OK, since system utilities like id, pw /usershow/, chown, ls resolve domain usernames - IDMapped UIDs OK. But getent passwd and getent group return only local (system) users /groups. Any clue how to make this work too? Ivo Karabojkov wrote: Dear Sirs, I am having troubles with IDMapping users from Server 2003 AD to my FreeBSD 8.1 Samba 3.5. Well, most of Samba documentation should be considered outdated, I had total failure with RID backend for IDMap. The only working (so far) for me is the default: tdb. I have set nsswitch.conf, pam.d and so on correctly. And here is my problem: everything works almost fine, wbinfo shows my domain accounts, I am able to set these accounts and groups as owners of files. Commands like ls, chown, id show AD accounts correctly. pw, getent - show only local system accounts. I need Samba only for file sharing with ACLs, no PAM authentication or something more. So, technically, it works but since I can't see ALL accounts with getent I think something is wrong. IDMapped accounts are with uid and gid 1 I think I am missing something very small and simple, so I hope someone will help me! Thanks in advance, Ivo -- View this message in context: http://old.nabble.com/FreeBSD-samba%2Bwinbind-tp30252640p30282675.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Samba Access Like Windows Explorer
Is it possible to access samba shares much like windows explorer does? The ultimate solution would be UNC names with browsing. I would very much like to have my freebsd client see the network namespace in as similar fashion to windows as possible. I also would like to avoid having to duplicate the hierarchy of mount points (for mount_smbfs) on every freebsd client in order to achieve this. Nautilus access the samba shares this way, but I want this work on the command line. Plus I prefer Thunar, which doesn't do samba access at all. As it stands, I think I will have to mount all samba shares on a freebsd client into a top level directory named for the server name, with mount points sprinkled about. Thanks, Jason C. Wells ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba Access Like Windows Explorer
Jason C. Wells wrote: Is it possible to access samba shares much like windows explorer does? The ultimate solution would be UNC names with browsing. I would very much like to have my freebsd client see the network namespace in as similar fashion to windows as possible. I also would like to avoid having to duplicate the hierarchy of mount points (for mount_smbfs) on every freebsd client in order to achieve this. Nautilus access the samba shares this way, but I want this work on the command line. Plus I prefer Thunar, which doesn't do samba access at all. As it stands, I think I will have to mount all samba shares on a freebsd client into a top level directory named for the server name, with mount points sprinkled about. There two ways. I do it in Dolphin on KDE all the time. KDE has a kio_slave for smb:/ - that is it looks like this in the address bar: smb://testbed.test.zip/web/ - where the /web is a share This is a GUI'fied way of hiding the CLI smbclient. It can be bookmarked, as well as made into icons in the left side of Dolphin for easy clicking. Smbclient works just fine from a command prompt as well. The other way is to mount shares as file systems. This can be done with entries in fstab and an nsmb.conf file. If you were to pursue this route know that the workgroup/server/share info should be all Upper Case. Such is displayed in the example nsmb.conf but it isn't immediately apparent that upper case _must_ be used. Otherwise you end up chasing your tail wondering why it won't connect/mount. Me I used to do mounts in fstab, but lately just use the kio_slave and smbclient approach because it does what I need. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More On Samba And Softupdates
On 11/21/2010 2:16 PM, Adam Vande More wrote: On Sun, Nov 21, 2010 at 10:56 AM, Tim Daneliuk tun...@tundraware.com mailto:tun...@tundraware.com wrote: This drive is being used as a backup drive for all the workstations on this particular network, and reliable is much more important than slightly faster. As someone already said, SU is probably not the culprit here. I've used Samba + SU for a long time with no such problems although I have no current setups to verify. SU substantially increases disk IO, it's not 'slightly faster' it's much faster. The error you see is probably the result of flaky drive or controller as the additional IO provided by SU allows the flakiness to show through. Although from what you describe my choice for the drive would be gjournal + UFS. If you've got a lot of asynchronous IO that's a better solution. It looks like this may have been a loose cable. After reseating the cable and reinitializing the drive, it seems to be fine. I turned on softupdates and all seems well ... Thanks for responding... -- Tim Daneliuk tun...@tundraware.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD samba+winbind
Perhaps I couldn't get any attention with my problem or I couldn't explain it in enough details. As you probably read, IDMapping works OK. It seems that my problem occurs in nsswitch. In my /etc/nsswitch.conf I have: group: files winbind #group_compat: nis hosts: files dns networks: files passwd: files winbind #passwd_compat: nis shells: files services: compat services_compat: nis protocols: files rpc: files wbinfo -u / -g / -i DOMAIN_user works OK. Name service switch works almost OK, since system utilities like id, pw /usershow/, chown, ls resolve domain usernames - IDMapped UIDs OK. But getent passwd and getent group return only local (system) users /groups. Any clue how to make this work too? Ivo Karabojkov wrote: Dear Sirs, I am having troubles with IDMapping users from Server 2003 AD to my FreeBSD 8.1 Samba 3.5. Well, most of Samba documentation should be considered outdated, I had total failure with RID backend for IDMap. The only working (so far) for me is the default: tdb. I have set nsswitch.conf, pam.d and so on correctly. And here is my problem: everything works almost fine, wbinfo shows my domain accounts, I am able to set these accounts and groups as owners of files. Commands like ls, chown, id show AD accounts correctly. pw, getent - show only local system accounts. I need Samba only for file sharing with ACLs, no PAM authentication or something more. So, technically, it works but since I can't see ALL accounts with getent I think something is wrong. IDMapped accounts are with uid and gid 1 I think I am missing something very small and simple, so I hope someone will help me! Thanks in advance, Ivo -- View this message in context: http://old.nabble.com/FreeBSD-samba%2Bwinbind-tp30252640p30282675.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
More On Samba And Softupdates
The other day I mentioned I had a problem with a Samba-shared drive that was just installed blowing up. When I rebuilt it, I forgot to enable softupdates but the drive seems to be working flawlessly. I understand it is possible to do this after-the-fact with tunefs. Some questions: Do I have to unmount the drive to do it? What benefit will I get if I turn on softupdates? This drive is being used as a backup drive for all the workstations on this particular network, and reliable is much more important than slightly faster. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More On Samba And Softupdates
On Sun, Nov 21, 2010 at 10:56 AM, Tim Daneliuk tun...@tundraware.comwrote: This drive is being used as a backup drive for all the workstations on this particular network, and reliable is much more important than slightly faster. As someone already said, SU is probably not the culprit here. I've used Samba + SU for a long time with no such problems although I have no current setups to verify. SU substantially increases disk IO, it's not 'slightly faster' it's much faster. The error you see is probably the result of flaky drive or controller as the additional IO provided by SU allows the flakiness to show through. Although from what you describe my choice for the drive would be gjournal + UFS. If you've got a lot of asynchronous IO that's a better solution. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More On Samba And Softupdates
Tim Daneliuk wrote: The other day I mentioned I had a problem with a Samba-shared drive that was just installed blowing up. When I rebuilt it, I forgot to enable softupdates but the drive seems to be working flawlessly. I understand it is possible to do this after-the-fact with tunefs. Some questions: Do I have to unmount the drive to do it? What benefit will I get if I turn on softupdates? This drive is being used as a backup drive for all the workstations on this particular network, and reliable is much more important than slightly faster. As per man tunefs: The tunefs utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. The benefit is not just speed, but better concurrent multi-user throughput. Operations which would block other I/O finish sooner so the next task can begin without waiting. I actually run mine with aio_load=YES in loader.conf in conjunction with the following in smb.conf: aio read size = 16384 aio write size = 16384 aio write behind = true block size = 16384 use sendfile = Yes Minor performance tweaks aside, should you continue to see the error(s) described in the other mail I sincerely suspect softupdates is not the culprit. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: More On Samba And Softupdates
On Sun, Nov 21, 2010 at 2:16 PM, Adam Vande More amvandem...@gmail.comwrote: Although from what you describe my choice for the drive would be gjournal + UFS. If you've got a lot of asynchronous IO that's a better solution. Instead of asynchronous, I meant multi-threaded. gjournal + UFS handles concurrency better. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Softupdates And Samba
I installed another SATA drive on a FreeBSD 8.1-STABLE box here last night. After the disk prep, I mounted it and then shared the whole drive via Samba. This morning when I came in, the machine had horked all over itself and I saw this in the log after the reboot: Nov 20 01:06:59 ozzie kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=34066054 3 Nov 20 01:06:59 ozzie kernel: ad6: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10 NID_NOT_FOUND LBA=340660543 Nov 20 01:06:59 ozzie kernel: g_vfs_done():ad6s1d[WRITE(offset=174418165760, length=131072)]e rror = 5 Nov 20 02:15:07 ozzie kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=14580695 35 Nov 20 02:15:07 ozzie kernel: ad6: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10 NID_NOT_FOUND LBA=1458069535 Nov 20 02:15:07 ozzie kernel: g_vfs_done():ad6s1d[WRITE(offset=746531569664, length=131072)]e rror = 5 I reformatted and remounted the drive and accidentally forgot to enable softupdates. It seems to now be working fine. Is there a known interaction with softupdates and Samba such that I should not use them in this case, or could this just have been a loose cable or something? The drive is pretty new ( 6mo) and it's never been a problem when I used it on an NTFS system previously. TIA, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Softupdates And Samba
Tim Daneliuk wrote: I installed another SATA drive on a FreeBSD 8.1-STABLE box here last night. After the disk prep, I mounted it and then shared the whole drive via Samba. This morning when I came in, the machine had horked all over itself and I saw this in the log after the reboot: Nov 20 01:06:59 ozzie kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=34066054 3 Nov 20 01:06:59 ozzie kernel: ad6: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10 NID_NOT_FOUND LBA=340660543 Nov 20 01:06:59 ozzie kernel: g_vfs_done():ad6s1d[WRITE(offset=174418165760, length=131072)]e rror = 5 Nov 20 02:15:07 ozzie kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=14580695 35 Nov 20 02:15:07 ozzie kernel: ad6: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=10 NID_NOT_FOUND LBA=1458069535 Nov 20 02:15:07 ozzie kernel: g_vfs_done():ad6s1d[WRITE(offset=746531569664, length=131072)]e rror = 5 I reformatted and remounted the drive and accidentally forgot to enable softupdates. It seems to now be working fine. Is there a known interaction with softupdates and Samba such that I should not use them in this case, or could this just have been a loose cable or something? The drive is pretty new ( 6mo) and it's never been a problem when I used it on an NTFS system previously. TIA, I can't speak to -Stable, as I bounce from -Release to -Release. But I have used Samba with softupdates for years and never experienced any problem which might be related to such a combination. While it exists the possibility of flaky controller/driver bug I would look towards a hardware situation first. First thing I'd do is get a bootable CD with the drive manufacturer's diagnostics on it. Western Digital has a bootable .iso you can download if it happens to be a WD. Do the destructive write all zeros comprehensive test and look for any errors, particularly surface defects. I do this with any used drive before using it again. Oh yeah - swap in a new cable first. Plug it in and out several times to scratch through any thin film layer of corrosion which may have formed on the copper. RAID controller and a so-called Green drive? They are very prone to falling offline, as per: http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1397 Most of the time you can get away with running a desktop drive on a RAID controller and not have problems, but the potential exists. In lieu of this, you could also install smartmontools and look at the drive with various smartctl tests. I take numbers from smart testing with a grain of salt. I generally see them as an additional data point rather than trying to split hairs into a conclusion. The thing you would be trying to discern here is if the bad sector remap area has filled. When this happens the drive can no longer hide bad sectors from the OS. I'd bet it's something simple like a bad cable. Also recall the first rule of maintenance: If it works, don't Fix It! :-) -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD samba+winbind
Dear Sirs, I am having troubles with IDMapping users from Server 2003 AD to my FreeBSD 8.1 Samba 3.5. Well, most of Samba documentation should be considered outdated, I had total failure with RID backend for IDMap. The only working (so far) for me is the default: tdb. I have set nsswitch.conf, pam.d and so on correctly. And here is my problem: everything works almost fine, wbinfo shows my domain accounts, I am able to set these accounts and groups as owners of files. Commands like ls, chown, id show AD accounts correctly. pw, getent - show only local system accounts. I need Samba only for file sharing with ACLs, no PAM authentication or something more. So, technically, it works but since I can't see ALL accounts with getent I think something is wrong. IDMapped accounts are with uid and gid 1 I think I am missing something very small and simple, so I hope someone will help me! Thanks in advance, Ivo -- View this message in context: http://old.nabble.com/FreeBSD-samba%2Bwinbind-tp30252640p30252640.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mount_smbfs problem after upgrade Samba 3.4 - 3.5
On 11/03/10 00:04, Bartosz Stec wrote: Hi, Hello! I'm doing a major overhaul of our Samba servers including an upgrade to the latest port version, 3.5.6. I'm getting most things in place but a remaining problem is that I cannot any longer use mount_smbfs: mount_smbfs -I 192.168.1.8 //peo at mars http://lists.freebsd.org/mailman/listinfo/freebsd-questions/inter /home/mnt Password: mount_smbfs: unable to open connection: syserr = Authentication error Samba server log says: mbd/sesssetup.c:1703(reply_sesssetup_and_X) reply_sesssetup_and_X: Attempted encrypted session setup without negprot denied! smbclient works fine and so does connecting to the shares from Windows and Konqerour like smb://192.168.1.8/. smb://192.168.1.8/%22. Anybody on the list with enough knowledge of Samba that could take a shot at this? Apparently something changed between version 3.4 and 3.5 of Samba. My knowledge about Samba is limited at best, but it seems that I found possible couse and working override (solution?). Check this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=151887 If this fixes your problem too, please submit followup - more information port maintainer gets, less time he's gonna need to fix this. Yes, it fixed my problem. Submitting followup, thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
re: mount_smbfs problem after upgrade Samba 3.4 - 3.5
Hi, Hello! I'm doing a major overhaul of our Samba servers including an upgrade to the latest port version, 3.5.6. I'm getting most things in place but a remaining problem is that I cannot any longer use mount_smbfs: mount_smbfs -I 192.168.1.8 //peo at mars http://lists.freebsd.org/mailman/listinfo/freebsd-questions/inter /home/mnt Password: mount_smbfs: unable to open connection: syserr = Authentication error Samba server log says: mbd/sesssetup.c:1703(reply_sesssetup_and_X) reply_sesssetup_and_X: Attempted encrypted session setup without negprot denied! smbclient works fine and so does connecting to the shares from Windows and Konqerour like smb://192.168.1.8/. smb://192.168.1.8/%22. Anybody on the list with enough knowledge of Samba that could take a shot at this? Apparently something changed between version 3.4 and 3.5 of Samba. My knowledge about Samba is limited at best, but it seems that I found possible couse and working override (solution?). Check this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=151887 If this fixes your problem too, please submit followup - more information port maintainer gets, less time he's gonna need to fix this. -- Bartosz Stec ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mount_smbfs problem after upgrade Samba 3.4 - 3.5
Hi, I'm doing a major overhaul of our Samba servers including an upgrade to the latest port version, 3.5.6. I'm getting most things in place but a remaining problem is that I cannot any longer use mount_smbfs: mount_smbfs -I 192.168.1.8 //p...@mars/inter /home/mnt Password: mount_smbfs: unable to open connection: syserr = Authentication error Samba server log says: mbd/sesssetup.c:1703(reply_sesssetup_and_X) reply_sesssetup_and_X: Attempted encrypted session setup without negprot denied! smbclient works fine and so does connecting to the shares from Windows and Konqerour like smb://192.168.1.8/. Anybody on the list with enough knowledge of Samba that could take a shot at this? Apparently something changed between version 3.4 and 3.5 of Samba. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mount_smbfs problem after upgrade Samba 3.4 - 3.5
On 10/31/10 14:06, Per olof Ljungmark wrote: Hi, I'm doing a major overhaul of our Samba servers including an upgrade to the latest port version, 3.5.6. I'm getting most things in place but a remaining problem is that I cannot any longer use mount_smbfs: mount_smbfs -I 192.168.1.8 //p...@mars/inter /home/mnt Password: mount_smbfs: unable to open connection: syserr = Authentication error Samba server log says: mbd/sesssetup.c:1703(reply_sesssetup_and_X) reply_sesssetup_and_X: Attempted encrypted session setup without negprot denied! smbclient works fine and so does connecting to the shares from Windows and Konqerour like smb://192.168.1.8/. Anybody on the list with enough knowledge of Samba that could take a shot at this? Apparently something changed between version 3.4 and 3.5 of Samba. Thanks! Just noted another post from yesterday, same issue: Issue wit Samba 3.5.6 and Mac OS X 10.5 I've filed a bug report to see if the maintainer could have a look. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba PDC roaming profiles problem
Op 2-8-2010 21:26, David N schreef:
On 2 August 2010 21:32, Alex de Kruijffal...@specialisterren.nl wrote:
Hi,
I've setup a LDAP backend Samba PDC. I can gain access to shares and
login with a user that is in LDAP, but have a prblem setting up the
roaming profile stuff. I've been trying to solve this problem for some
time now, and have tried everything I could think of, but without much
luck. I keep getting the following error messages:
Windows cannot locate the server copy of your roaming profile and is
attempting to log you on with your local profile. Changes to the profile
will not be copied to the server when you logoff. Plausible causes of
this error include network problem or insufficient security rights. If
this problem persists, contact your network administrators. DETAILS -
The network path was not found.
Followed by:
Windows cannot find the local profile and is logging on with a tempory
profiles. Changes to this profile will be lost when you logoff.
Here is my smb.conf:
[global]
security = user
name resolve order = wins lmhosts hosts bcast
deadtime = 15
map to guest = Never
csc policy = disable
hosts allow = 127. 192.168.
server string =
workgroup = Nieuwegein
time server = yes
wins support = yes
domain master = yes
domain logons = yes
encrypt passwords = yes
local master = yes
logon drive = Z:
logon path = \\%L\profiles\%U
preferred master = yes
os level = 255
encrypt passwords = yes
passdb backend = ldapsam:ldap://localhost/
enable privileges = Yes
pam password change = yes
passwd program = /usr/local/sbin/smbldap-passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n
*all*authentication*tokens*updated*
unix password sync = Yes
ldap delete dn = Yes
ldap ssl = Off
ldap passwd sync = Yes
ldap admin dn = cn=admin,dc=specialisterren,dc=nl
ldap suffix = dc=specialisterren,dc=nl
ldap group suffix = ou=Groups
ldap idmap suffix = ou=Users
ldap machine suffix = ou=Computers
ldap user suffix = ou=Users
idmap backend = ldap:ldap://localhost
idmap uid = 1-2
idmap gid = 1-2
add user script = /usr/local/sbin/smbldap-useradd -a -m %u
delete user script = /usr/local/sbin/smbldap-userdel %u
add group script = /usr/local/sbin/smbldap-groupadd -p %g
delete group script = /usr/local/sbin/smbldap-groupdel %g
add user to group script = /usr/local/sbin/smbldap-groupmod -m
%u %g
delete user from group script = /usr/local/sbin/smbldap-groupmod
-x %u %g
set primary group script = /usr/local/sbin/smbldap-usermod -g %g
%u
add machine script = /usr/local/sbin/smbldap-useradd -w %u
template homedir = /home/%U
template shell = /bin/csh
getwd cache = yes
socket options = SO_KEEPALIVE TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=819
use sendfile = yes
mangle prefix = 6 # How to mangle Long Filenames in to 8.3 DOS
log level = 1
log file = /var/log/samba/log.%m
max log size = 50
syslog = 0
[template]
# edited out, has no path
[homes]
comment = Home users
inherit owner = yes
dos filemode = yes
writable = yes
read list = @wheel @Domain Admins
valid users = %S
create mask = 0740
directory mask = 0750
aio read size = 16384
[netlogon]
comment = Network Logon Service
path = /disk/netlogon
browseable = no
read only = yes
aio read size = 16384
[profiles]
comment = Roaming Profiles Directory
path = /disk/profiles
administrative share = true
browseable = no
writable = yes
create mask = 0600
directory mask = 0700
aio read size = 16384
public = yes
# The root preexec command performs:
# mkdir -pm 750 /disk/profiles/%U-%a; chown %U /disk/profiles/%U-%a
# I started off without this.
root preexec = /root/sbin/profiles.sh %U %a
# edited out other shares
ldapsearch gives me:
# tester, Users, specialisterren.nl
dn: uid=tester,ou=Users,dc=specialisterren,dc=nl
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: shadowAccount
objectClass: sambaSamAccount
cn: tester
sn: tester
givenName: tester
uid: tester
uidNumber: 10005
gidNumber: 513
homeDirectory: /home/tester
loginShell: /bin/sh
gecos: Tes ter
sambaLogonTime: 0
(Edited out the other stuff)
I can acces \\Server\profiles, \\Server\netlogon using my tester
account. /etc/passwd contains no line with the user tester. And I can
login under SSH with the tester account.
ll -d /disk/{netlogon,profiles}gives me:
drwxr-xr-x 2 root wheel 512 Mar 16 11:09 /disk/netlogon/
drwxrwxrwt 2 root wheel 512 Aug 2 12:41 /disk/profiles/
Alex
Re: Samba PDC roaming profiles problem
On Tue, Aug 03, 2010 at 12:22:33PM +0200, Alex de Kruijff typed: I've enabled debugging in Windows Domain using: http://support.microsoft.com/default.aspx?scid=kb;en-us;221833 I find it strange that it first tries \\%L\profiles\testers. This is the log. USERENV(2ec.2f0) 12:08:35:468 LoadUserProfile: Entering, hToken = 0x960, lpProfileInfo = 0x6e3e0 USERENV(2ec.2f0) 12:08:35:468 LoadUserProfile: [lot's of MS logs snipped] I really think these kind of logs could be much better analyzed at a samba or MS mailing list. cheers, Ruben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
[solved] Re: Samba PDC roaming profiles problem
Op 3-8-2010 14:35, Ruben de Groot schreef: On Tue, Aug 03, 2010 at 12:22:33PM +0200, Alex de Kruijff typed: I've enabled debugging in Windows Domain using: http://support.microsoft.com/default.aspx?scid=kb;en-us;221833 I find it strange that it first tries \\%L\profiles\testers. This is the log. USERENV(2ec.2f0) 12:08:35:468 LoadUserProfile: Entering, hToken = 0x960, lpProfileInfo = 0x6e3e0 USERENV(2ec.2f0) 12:08:35:468 LoadUserProfile: [lot's of MS logs snipped] I really think these kind of logs could be much better analyzed at a samba or MS mailing list. cheers, Ruben Hi, I solved it. Without LDAP one is able to use %L, %U and %a in the logon path, but if one uses LDAP then this path is no longer processed by Samba, but instead passed literally to Windows. So far my solution is to change all LDAP entries. This also means I should name multiple servers (on different networks) with the same hostname. Its a bit more limiting the smb.conf, but it works. Yours, Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [solved] Re: Samba PDC roaming profiles problem
On Tue, Aug 03, 2010 at 02:43:24PM +0200, Alex de Kruijff typed: I solved it. Without LDAP one is able to use %L, %U and %a in the logon path, but if one uses LDAP then this path is no longer processed by Samba, but instead passed literally to Windows. So far my solution is to change all LDAP entries. This also means I should name multiple servers (on different networks) with the same hostname. Its a bit more limiting the smb.conf, but it works. Ah, I see. Been there. Do you have the logon path etc options still in smb.conf or are you using ldap attributes (like sambaProfilePath, sambaHomeDrive) for each individual account? I found the latter to be more flexible in the long run (though a little harder to set up and administrate initially) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Samba PDC roaming profiles problem
Hi,
I've setup a LDAP backend Samba PDC. I can gain access to shares and
login with a user that is in LDAP, but have a prblem setting up the
roaming profile stuff. I've been trying to solve this problem for some
time now, and have tried everything I could think of, but without much
luck. I keep getting the following error messages:
Windows cannot locate the server copy of your roaming profile and is
attempting to log you on with your local profile. Changes to the profile
will not be copied to the server when you logoff. Plausible causes of
this error include network problem or insufficient security rights. If
this problem persists, contact your network administrators. DETAILS -
The network path was not found.
Followed by:
Windows cannot find the local profile and is logging on with a tempory
profiles. Changes to this profile will be lost when you logoff.
Here is my smb.conf:
[global]
security = user
name resolve order = wins lmhosts hosts bcast
deadtime = 15
map to guest = Never
csc policy = disable
hosts allow = 127. 192.168.
server string =
workgroup = Nieuwegein
time server = yes
wins support = yes
domain master = yes
domain logons = yes
encrypt passwords = yes
local master = yes
logon drive = Z:
logon path = \\%L\profiles\%U
preferred master = yes
os level = 255
encrypt passwords = yes
passdb backend = ldapsam:ldap://localhost/
enable privileges = Yes
pam password change = yes
passwd program = /usr/local/sbin/smbldap-passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n
*all*authentication*tokens*updated*
unix password sync = Yes
ldap delete dn = Yes
ldap ssl = Off
ldap passwd sync = Yes
ldap admin dn = cn=admin,dc=specialisterren,dc=nl
ldap suffix = dc=specialisterren,dc=nl
ldap group suffix = ou=Groups
ldap idmap suffix = ou=Users
ldap machine suffix = ou=Computers
ldap user suffix = ou=Users
idmap backend = ldap:ldap://localhost
idmap uid = 1-2
idmap gid = 1-2
add user script = /usr/local/sbin/smbldap-useradd -a -m %u
delete user script = /usr/local/sbin/smbldap-userdel %u
add group script = /usr/local/sbin/smbldap-groupadd -p %g
delete group script = /usr/local/sbin/smbldap-groupdel %g
add user to group script = /usr/local/sbin/smbldap-groupmod -m
%u %g
delete user from group script = /usr/local/sbin/smbldap-groupmod
-x %u %g
set primary group script = /usr/local/sbin/smbldap-usermod -g %g
%u
add machine script = /usr/local/sbin/smbldap-useradd -w %u
template homedir = /home/%U
template shell = /bin/csh
getwd cache = yes
socket options = SO_KEEPALIVE TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=819
use sendfile = yes
mangle prefix = 6 # How to mangle Long Filenames in to 8.3 DOS
log level = 1
log file = /var/log/samba/log.%m
max log size = 50
syslog = 0
[template]
# edited out, has no path
[homes]
comment = Home users
inherit owner = yes
dos filemode = yes
writable = yes
read list = @wheel @Domain Admins
valid users = %S
create mask = 0740
directory mask = 0750
aio read size = 16384
[netlogon]
comment = Network Logon Service
path = /disk/netlogon
browseable = no
read only = yes
aio read size = 16384
[profiles]
comment = Roaming Profiles Directory
path = /disk/profiles
administrative share = true
browseable = no
writable = yes
create mask = 0600
directory mask = 0700
aio read size = 16384
public = yes
# The root preexec command performs:
# mkdir -pm 750 /disk/profiles/%U-%a; chown %U /disk/profiles/%U-%a
# I started off without this.
root preexec = /root/sbin/profiles.sh %U %a
# edited out other shares
ldapsearch gives me:
# tester, Users, specialisterren.nl
dn: uid=tester,ou=Users,dc=specialisterren,dc=nl
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: shadowAccount
objectClass: sambaSamAccount
cn: tester
sn: tester
givenName: tester
uid: tester
uidNumber: 10005
gidNumber: 513
homeDirectory: /home/tester
loginShell: /bin/sh
gecos: Tes ter
sambaLogonTime: 0
(Edited out the other stuff)
I can acces \\Server\profiles, \\Server\netlogon using my tester
account. /etc/passwd contains no line with the user tester. And I can
login under SSH with the tester account.
ll -d /disk/{netlogon,profiles}gives me:
drwxr-xr-x 2 root wheel 512 Mar 16 11:09 /disk/netlogon/
drwxrwxrwt 2 root wheel 512 Aug 2 12:41 /disk/profiles/
Alex
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba PDC roaming profiles problem
Alex de Kruijff wrote: Hi, I've setup a LDAP backend Samba PDC. I can gain access to shares and login with a user that is in LDAP, but have a prblem setting up the roaming profile stuff. I've been trying to solve this problem for some time now, and have tried everything I could think of, but without much luck. I keep getting the following error messages: Windows cannot locate the server copy of your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Plausible causes of this error include network problem or insufficient security rights. If this problem persists, contact your network administrators. DETAILS - The network path was not found. Followed by: Windows cannot find the local profile and is logging on with a tempory profiles. Changes to this profile will be lost when you logoff. Sorry - but I can't speak to anything about the LDAP setup as I probably don't know enough about it. One thing that strikes me though, is Windows uses DNS SRV records to locate services and populate variables. The naming scheme is fairly convoluted and Windows centric. On a Windows box use network monitor to capture what the box is trying to do. If you see it doing a lot of look ups for SRV records and failing it might be something to investigate. The network monitor version that ships with the desktop will only grab traffic for that particular machine, but is enough for the purpose. The version that comes with the server is able to promiscuously examine all traffic. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba PDC roaming profiles problem
On 2 August 2010 21:32, Alex de Kruijff al...@specialisterren.nl wrote:
Hi,
I've setup a LDAP backend Samba PDC. I can gain access to shares and
login with a user that is in LDAP, but have a prblem setting up the
roaming profile stuff. I've been trying to solve this problem for some
time now, and have tried everything I could think of, but without much
luck. I keep getting the following error messages:
Windows cannot locate the server copy of your roaming profile and is
attempting to log you on with your local profile. Changes to the profile
will not be copied to the server when you logoff. Plausible causes of
this error include network problem or insufficient security rights. If
this problem persists, contact your network administrators. DETAILS -
The network path was not found.
Followed by:
Windows cannot find the local profile and is logging on with a tempory
profiles. Changes to this profile will be lost when you logoff.
Here is my smb.conf:
[global]
security = user
name resolve order = wins lmhosts hosts bcast
deadtime = 15
map to guest = Never
csc policy = disable
hosts allow = 127. 192.168.
server string =
workgroup = Nieuwegein
time server = yes
wins support = yes
domain master = yes
domain logons = yes
encrypt passwords = yes
local master = yes
logon drive = Z:
logon path = \\%L\profiles\%U
preferred master = yes
os level = 255
encrypt passwords = yes
passdb backend = ldapsam:ldap://localhost/
enable privileges = Yes
pam password change = yes
passwd program = /usr/local/sbin/smbldap-passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n
*all*authentication*tokens*updated*
unix password sync = Yes
ldap delete dn = Yes
ldap ssl = Off
ldap passwd sync = Yes
ldap admin dn = cn=admin,dc=specialisterren,dc=nl
ldap suffix = dc=specialisterren,dc=nl
ldap group suffix = ou=Groups
ldap idmap suffix = ou=Users
ldap machine suffix = ou=Computers
ldap user suffix = ou=Users
idmap backend = ldap:ldap://localhost
idmap uid = 1-2
idmap gid = 1-2
add user script = /usr/local/sbin/smbldap-useradd -a -m %u
delete user script = /usr/local/sbin/smbldap-userdel %u
add group script = /usr/local/sbin/smbldap-groupadd -p %g
delete group script = /usr/local/sbin/smbldap-groupdel %g
add user to group script = /usr/local/sbin/smbldap-groupmod -m
%u %g
delete user from group script = /usr/local/sbin/smbldap-groupmod
-x %u %g
set primary group script = /usr/local/sbin/smbldap-usermod -g %g
%u
add machine script = /usr/local/sbin/smbldap-useradd -w %u
template homedir = /home/%U
template shell = /bin/csh
getwd cache = yes
socket options = SO_KEEPALIVE TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=819
use sendfile = yes
mangle prefix = 6 # How to mangle Long Filenames in to 8.3 DOS
log level = 1
log file = /var/log/samba/log.%m
max log size = 50
syslog = 0
[template]
# edited out, has no path
[homes]
comment = Home users
inherit owner = yes
dos filemode = yes
writable = yes
read list = @wheel @Domain Admins
valid users = %S
create mask = 0740
directory mask = 0750
aio read size = 16384
[netlogon]
comment = Network Logon Service
path = /disk/netlogon
browseable = no
read only = yes
aio read size = 16384
[profiles]
comment = Roaming Profiles Directory
path = /disk/profiles
administrative share = true
browseable = no
writable = yes
create mask = 0600
directory mask = 0700
aio read size = 16384
public = yes
# The root preexec command performs:
# mkdir -pm 750 /disk/profiles/%U-%a; chown %U /disk/profiles/%U-%a
# I started off without this.
root preexec = /root/sbin/profiles.sh %U %a
# edited out other shares
ldapsearch gives me:
# tester, Users, specialisterren.nl
dn: uid=tester,ou=Users,dc=specialisterren,dc=nl
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: shadowAccount
objectClass: sambaSamAccount
cn: tester
sn: tester
givenName: tester
uid: tester
uidNumber: 10005
gidNumber: 513
homeDirectory: /home/tester
loginShell: /bin/sh
gecos: Tes ter
sambaLogonTime: 0
(Edited out the other stuff)
I can acces \\Server\profiles, \\Server\netlogon using my tester
account. /etc/passwd contains no line with the user tester. And I can
login under SSH with the tester account.
ll -d /disk/{netlogon,profiles}gives me:
drwxr-xr-x 2 root wheel 512 Mar 16 11:09 /disk/netlogon/
drwxrwxrwt 2 root wheel 512 Aug 2 12:41 /disk/profiles/
Alex
___
freebsd-questions@freebsd.org mailing list
http
Re: samba pam_smbpass passwd seg fault
Hi! On Mon, Jul 19, 2010 at 4:44 AM, Michael McGrew mmcgr...@mail.csuchico.edu wrote: I'm trying to sync the local unix account passwords to the samba smbpass db using pam. When i run passwd, after it's done it seg faults and produces a core dump. The odd thing is that it works, the users local unix password gets synced to the smbpass db, but it seg faults. Below are my relevant config files. Is this a bug or am I doing something wrong? The relevant information would be the version of the samba you are using and analysis of the coredump. Make sure your samba is compiled with debug information. Timur. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
On Sun, Jul 18, 2010 at 10:42 PM, David Brodbeck g...@gull.us wrote: On Jul 7, 2010, at 10:12 AM, David Brodbeck wrote: On Wed, July 7, 2010 2:20 am, mcoyles wrote: David - have a look here... http://lists.freebsd.org/pipermail/freebsd-current/2010-April/016405.html OK, I see. It looks like rtld is part of world, not a port, so then the question becomes, why didn't freebsd-update update it for me? Is there a way I can force a binary upgrade, or do I need to download the source and rebuild things that way? I ended up downloading the 7.3 livefs ISO, booting off of it, and replacing /libexec/ld-elf.so.1 with the one from the CD. That fixed the problem. I suspect the reason freebsd-update didn't upgrade it properly is it appears it's impossible to replace this file on a running system, even in single-user mode. Maybe there should be something in the release notes about a 7.2 - 7.3 upgrade being impossible to do properly except by booting from CD? make installworld happily does it, so can you - by renaming file to the *.old and then putting new on in it's place. So, it could be that freebsd-update isn't sophisticated enough to do such a trick. Timur. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: samba pam_smbpass passwd seg fault
Thank you for the response, I have the latest port version of samba, samba34-3.4.8. The core does not give much info here is a snippet of the end of the trace. Here is a link to the end of the truss trace of the process. http://mmcgrew.net/out #636 0x792f6e69622f7273 in ?? () #637 0x0064777373617070 in ?? () #638 0x247c8d48002454ff in ?? () #639 0x01a1c0c748006a10 in ?? () #640 0x66fdebf4050f in ?? () #641 0x90909066 in ?? () #642 0x7fffec18 in ?? () #643 0x0001 in ?? () #644 0x7fffec28 in ?? () #645 0x0010 in ?? () Cannot access memory at address 0x8000 /var/log/messages Jul 19 10:11:49 kernel: Jul 19 10:11:49 kernel: pid 58460 (passwd), uid 0: exited on signal 11 On Mon, Jul 19, 2010 at 1:31 AM, Timur I. Bakeyev ti...@com.bat.ru wrote: Hi! On Mon, Jul 19, 2010 at 4:44 AM, Michael McGrew mmcgr...@mail.csuchico.edu wrote: I'm trying to sync the local unix account passwords to the samba smbpass db using pam. When i run passwd, after it's done it seg faults and produces a core dump. The odd thing is that it works, the users local unix password gets synced to the smbpass db, but it seg faults. Below are my relevant config files. Is this a bug or am I doing something wrong? The relevant information would be the version of the samba you are using and analysis of the coredump. Make sure your samba is compiled with debug information. Timur. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
On Mon, July 19, 2010 1:37 am, Timur I. Bakeyev wrote: On Sun, Jul 18, 2010 at 10:42 PM, David Brodbeck g...@gull.us wrote: On Jul 7, 2010, at 10:12 AM, David Brodbeck wrote: On Wed, July 7, 2010 2:20 am, mcoyles wrote: David - have a look here... http://lists.freebsd.org/pipermail/freebsd-current/2010-April/016405.html OK, I see. It looks like rtld is part of world, not a port, so then the question becomes, why didn't freebsd-update update it for me? Is there a way I can force a binary upgrade, or do I need to download the source and rebuild things that way? I ended up downloading the 7.3 livefs ISO, booting off of it, and replacing /libexec/ld-elf.so.1 with the one from the CD. That fixed the problem. I suspect the reason freebsd-update didn't upgrade it properly is it appears it's impossible to replace this file on a running system, even in single-user mode. Maybe there should be something in the release notes about a 7.2 - 7.3 upgrade being impossible to do properly except by booting from CD? make installworld happily does it, so can you - by renaming file to the *.old and then putting new on in it's place. So, it could be that freebsd-update isn't sophisticated enough to do such a trick. That doesn't work, unfortunately. Once you rename ld-elf.so.1 to ld-elf.so.1.old, trying to run any further commands -- even mv and cp -- fails with an error. (I didn't write down which one; something about failing to load the ELF interpreter, I think.) I know, I managed to cripple my system that way. I had to boot a LiveCD to recover, because it couldn't even load /bin/sh to get into single-user mode. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
In the last episode (Jul 19), David Brodbeck said: On Mon, July 19, 2010 1:37 am, Timur I. Bakeyev wrote: On Sun, Jul 18, 2010 at 10:42 PM, David Brodbeck g...@gull.us wrote: On Jul 7, 2010, at 10:12 AM, David Brodbeck wrote: On Wed, July 7, 2010 2:20 am, mcoyles wrote: David - have a look here... http://lists.freebsd.org/pipermail/freebsd-current/2010-April/016405.html OK, I see. It looks like rtld is part of world, not a port, so then the question becomes, why didn't freebsd-update update it for me? Is there a way I can force a binary upgrade, or do I need to download the source and rebuild things that way? I ended up downloading the 7.3 livefs ISO, booting off of it, and replacing /libexec/ld-elf.so.1 with the one from the CD. That fixed the problem. I suspect the reason freebsd-update didn't upgrade it properly is it appears it's impossible to replace this file on a running system, even in single-user mode. Maybe there should be something in the release notes about a 7.2 - 7.3 upgrade being impossible to do properly except by booting from CD? make installworld happily does it, so can you - by renaming file to the *.old and then putting new on in it's place. So, it could be that freebsd-update isn't sophisticated enough to do such a trick. That doesn't work, unfortunately. Once you rename ld-elf.so.1 to ld-elf.so.1.old, trying to run any further commands -- even mv and cp -- fails with an error. (I didn't write down which one; something about failing to load the ELF interpreter, I think.) I know, I managed to cripple my system that way. I had to boot a LiveCD to recover, because it couldn't even load /bin/sh to get into single-user mode. A better method would be to copy (not move) the file to a backup location, then either use mv or install to install the new version. Also, the programs in /rescue/ are statically linked so they can be used to recover if you end up losing ld-elf.so.1 or other critical shared libs. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
On Mon, July 19, 2010 12:47 pm, Dan Nelson wrote: In the last episode (Jul 19), David Brodbeck said: That doesn't work, unfortunately. Once you rename ld-elf.so.1 to ld-elf.so.1.old, trying to run any further commands -- even mv and cp -- fails with an error. (I didn't write down which one; something about failing to load the ELF interpreter, I think.) I know, I managed to cripple my system that way. I had to boot a LiveCD to recover, because it couldn't even load /bin/sh to get into single-user mode. A better method would be to copy (not move) the file to a backup location, then either use mv or install to install the new version. Also, the programs in /rescue/ are statically linked so they can be used to recover if you end up losing ld-elf.so.1 or other critical shared libs. That was actually what I tried first, but I got a file in use error when I tried to overwrite it with the new version. Good to know about /rescue. I'll remember that next time something like this happens. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
On Jul 7, 2010, at 10:12 AM, David Brodbeck wrote: On Wed, July 7, 2010 2:20 am, mcoyles wrote: Today I tried using portupgrade -R -f samba34 to rebuild samba and all of its dependencies, but I'm still getting the same error. I'm a little surprised that a minor version upgrade broke this so thoroughly. I went back over the release notes to see if I missed any obvious caveats about upgrading, but if I did, I'm not seeing it. David - have a look here... http://lists.freebsd.org/pipermail/freebsd-current/2010-April/016405.html OK, I see. It looks like rtld is part of world, not a port, so then the question becomes, why didn't freebsd-update update it for me? Is there a way I can force a binary upgrade, or do I need to download the source and rebuild things that way? I ended up downloading the 7.3 livefs ISO, booting off of it, and replacing /libexec/ld-elf.so.1 with the one from the CD. That fixed the problem. I suspect the reason freebsd-update didn't upgrade it properly is it appears it's impossible to replace this file on a running system, even in single-user mode. Maybe there should be something in the release notes about a 7.2 - 7.3 upgrade being impossible to do properly except by booting from CD? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
samba pam_smbpass passwd seg fault
I'm trying to sync the local unix account passwords to the samba smbpass db using pam. When i run passwd, after it's done it seg faults and produces a core dump. The odd thing is that it works, the users local unix password gets synced to the smbpass db, but it seg faults. Below are my relevant config files. Is this a bug or am I doing something wrong? /usr/local/etc/smb.conf security = user passdb backend = smbpasswd cat /etc/pam.d/passwd # # $FreeBSD: src/etc/pam.d/passwd,v 1.3.36.1 2010/02/10 00:26:20 kensmith Exp $ # # PAM configuration for the passwd service # # passwd(1) does not use the auth, account or session services. # password #password requisite pam_passwdqc.so enforce=users passwordrequiredpam_unix.so no_warn try_first_pass nullok passwordoptional/usr/local/lib/pam_smbpass.so try_first_pass smbconf=/usr/local/etc/smb.conf [r...@localhost ~]# passwd Changing local password for root New Password: Retype New Password: Segmentation fault: 11 (core dumped) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
On Sat, July 3, 2010 2:49 pm, David Brodbeck wrote: Today I upgraded my system from FreeBSD 7.2-RELEASE to FreeBSD 7.3- RELEASE using freebsd-update. Samba no longer runs. I get the following error messages: Starting nmbd. /libexec/ld-elf.so.1: /usr/local/sbin/nmbd: invalid PT_PHDR Starting smbd. /libexec/ld-elf.so.1: /usr/local/sbin/smbd: invalid PT_PHDR My upgrade sequence was to run 'freebsd-update upgrade -r 7.3-RELEASE' and 'freebsd-update install', followed by a reboot, then 'freebsd- update install' again, followed by a second reboot. I tried rebuilding the Samba port, thinking maybe it was an ABI change, but it still doesn't work. Can someone point me in the right direction? Today I tried using portupgrade -R -f samba34 to rebuild samba and all of its dependencies, but I'm still getting the same error. I'm a little surprised that a minor version upgrade broke this so thoroughly. I went back over the release notes to see if I missed any obvious caveats about upgrading, but if I did, I'm not seeing it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
Today I tried using portupgrade -R -f samba34 to rebuild samba and all of its dependencies, but I'm still getting the same error. I'm a little surprised that a minor version upgrade broke this so thoroughly. I went back over the release notes to see if I missed any obvious caveats about upgrading, but if I did, I'm not seeing it. David - have a look here... http://lists.freebsd.org/pipermail/freebsd-current/2010-April/016405.html Cheers! Marci ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
On Wed, July 7, 2010 2:20 am, mcoyles wrote: Today I tried using portupgrade -R -f samba34 to rebuild samba and all of its dependencies, but I'm still getting the same error. I'm a little surprised that a minor version upgrade broke this so thoroughly. I went back over the release notes to see if I missed any obvious caveats about upgrading, but if I did, I'm not seeing it. David - have a look here... http://lists.freebsd.org/pipermail/freebsd-current/2010-April/016405.html OK, I see. It looks like rtld is part of world, not a port, so then the question becomes, why didn't freebsd-update update it for me? Is there a way I can force a binary upgrade, or do I need to download the source and rebuild things that way? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
I apologize if this has been asked before; I tried searching the list, but the search engine on lists.freebsd.org keeps giving me an error message. Today I upgraded my system from FreeBSD 7.2-RELEASE to FreeBSD 7.3- RELEASE using freebsd-update. Samba no longer runs. I get the following error messages: Starting nmbd. /libexec/ld-elf.so.1: /usr/local/sbin/nmbd: invalid PT_PHDR Starting smbd. /libexec/ld-elf.so.1: /usr/local/sbin/smbd: invalid PT_PHDR My upgrade sequence was to run 'freebsd-update upgrade -r 7.3-RELEASE' and 'freebsd-update install', followed by a reboot, then 'freebsd- update install' again, followed by a second reboot. I tried rebuilding the Samba port, thinking maybe it was an ABI change, but it still doesn't work. Can someone point me in the right direction? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
