PDC migration: printing trouble. Summary.
in [Samba]
|
From: Gerald (Jerry) Carter on 11 Apr 2008 09:50 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Björn Jacke wrote: | On 2008-04-11 at 13:52 +0200 Helmut Hullen sent off: |> No patch attached. | | yes, it's useless as long as Mailman is removing the attached patch | each time. | | Look at the mail header: | | X-Content-Filtered-By: Mailman/MimeDel 2.1.5 | | If Mailman thinks a mail has bogous attachments it should remove and | bounce back the complete mailbut the mail should not be silently | altered. Jerry (are you the list maintainer?), can you have look at | the problem please? Tim normally deals with the postfix/mailman interaction. If he doesn't have time I'll look into it next week. cheers, jerry - -- ===================================================================== Samba ------- http://www.samba.org Likewise Software --------- http://www.likewisesoftware.com "What man is a man who does not make the world better?" --Balian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH/2rRIR7qMdg1EfYRAnBUAJ9y1gVYQBVtpOjzk0ddzqSKOAN68gCgyPiA I0V9rmX2ahGEvDJUJNv9eiQ= =Z8hO -----END PGP SIGNATURE----- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
From: Tim Potter on 11 Apr 2008 18:40 On Fri, 2008-04-11 at 08:42 -0500, Gerald (Jerry) Carter wrote: > Björn Jacke wrote: > | On 2008-04-11 at 13:52 +0200 Helmut Hullen sent off: > |> No patch attached. > | > | yes, it's useless as long as Mailman is removing the attached patch > | each time. > | > | Look at the mail header: > | > | X-Content-Filtered-By: Mailman/MimeDel 2.1.5 > | > | If Mailman thinks a mail has bogous attachments it should remove and > | bounce back the complete mailîbut the mail should not be silently > | altered. Jerry (are you the list maintainer?), can you have look at > | the problem please? > > Tim normally deals with the postfix/mailman interaction. > If he doesn't have time I'll look into it next week. The current behaviour of the samba list is to strip attachments that aren't multipart/{mixed,alternative,signed}, various digital signature types and text/plain. There doesn't seem to be an official MIME type for patches, after a quick browse through the list at: http://www.iana.org/assignments/media-types/ What MIME type is your mailer sending? Tim. > > > > > cheers, jerry > - -- > ===================================================================== > Samba ------- http://www.samba.org > Likewise Software --------- http://www.likewisesoftware.com > "What man is a man who does not make the world better?" --Balian > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFH/2rRIR7qMdg1EfYRAnBUAJ9y1gVYQBVtpOjzk0ddzqSKOAN68gCgyPiA > I0V9rmX2ahGEvDJUJNv9eiQ= > =Z8hO > -----END PGP SIGNATURE----- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
From: Ryan Novosielski on 6 May 2008 03:30 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Remy Zandwijk wrote: > Second: all printers had an 'invalid users' setting in the share > definition. > It turned out that this considerably stresses the CPU. It took about 10 > seconds for the properties to show up for a 'HP 4250PS driver' printer. > While > truss-ing the smbd process, we saw that the smbpasswd file was opened > for 85 > times (from the click on 'properties' to when the properties appeared). I > think that's a lot. We have around 4700 entries in the smbpasswd file, so I > can imagine why it takes long for the properties to show up when 6 invalid > users are configured. Only one would expect that the smbpasswd file is > opened > just 6 to 10 times, and not 85 times. I guess this won't happen when > using a > tdbsam passdb backend (which is not an option for us for now). I can confirm that your results will be much improved in all respects when you move to a proper backend. In our situation, the PW file was always locked as a result of too many reads and we were entirely unable to change passwords for a period of time. In fact, I would encourage you to do something about this before you get bitten by it, because with the file being read so often, you may run into this problem too. - -- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |novosirj(a)umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIH/qDmb+gadEcsb4RAunyAJ4lasxw461nCH54dxOlW+/Tm+QjQgCeIwXE YQg/Zb8tE//I537bvacM6RY= =AvXg -----END PGP SIGNATURE-----
From: L.P.H. van Belle on 6 May 2008 03:50 Hi, try this, first set alle the properties from user Administrator ( root ) then disconnect the printers for all users. reconnect. try now how fast it is. This works for my if the printer properties are slow. Greetz, Louis >-----Oorspronkelijk bericht----- >Van: samba-bounces+belle=bazuin.nl(a)lists.samba.org >[mailto:samba-bounces+belle=bazuin.nl(a)lists.samba.org] Namens >Ryan Novosielski >Verzonden: dinsdag 6 mei 2008 8:28 >Aan: samba(a)lists.samba.org >Onderwerp: Re: [Samba] PDC migration: printing trouble. Summary. > >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Remy Zandwijk wrote: > >> Second: all printers had an 'invalid users' setting in the share >> definition. >> It turned out that this considerably stresses the CPU. It >took about 10 >> seconds for the properties to show up for a 'HP 4250PS >driver' printer. >> While >> truss-ing the smbd process, we saw that the smbpasswd file was opened >> for 85 >> times (from the click on 'properties' to when the properties >appeared). I >> think that's a lot. We have around 4700 entries in the >smbpasswd file, so I >> can imagine why it takes long for the properties to show up >when 6 invalid >> users are configured. Only one would expect that the >smbpasswd file is >> opened >> just 6 to 10 times, and not 85 times. I guess this won't happen when >> using a >> tdbsam passdb backend (which is not an option for us for now). > >I can confirm that your results will be much improved in all respects >when you move to a proper backend. In our situation, the PW file was >always locked as a result of too many reads and we were entirely unable >to change passwords for a period of time. In fact, I would >encourage you >to do something about this before you get bitten by it, >because with the >file being read so often, you may run into this problem too. > >- -- > ---- _ _ _ _ ___ _ _ _ > |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II > |$&| |__| | | |__/ | \| _| |novosirj(a)umdnj.edu - >973/972.0922 (2-0922) > \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science >Bldg - C630 >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.6 (GNU/Linux) >Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > >iD8DBQFIH/qDmb+gadEcsb4RAunyAJ4lasxw461nCH54dxOlW+/Tm+QjQgCeIwXE >YQg/Zb8tE//I537bvacM6RY= >=AvXg >-----END PGP SIGNATURE----- > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
From: Matt Boyle on 6 May 2008 11:10 UPDATE: I've realized that this seems to be an issue with the compiler flags used to build samba. I've realized that i need to define _LARGEFILE_SOURCE, _LARGEFILE64_SOURCE, and _FILE_OFFSET_BITS=64. I've done this, but still have no luck reading files larger than 4GB. Anyone have suggestions? Thanks, Matt > Hi guys, > > I'm attempting to move large files (>4GB) from a PowerPC-based embedded system running a 2.4 kernel architecture to an PC running a 2.6 kernel. I've got samba compiled, installed, and running on the embedded box. I also have the directories from the PPC system mounted and accessible from the PC. > > I have two problems: larger file sizes do not list correctly, and large files transferred from the embedded box to the PC are not complete; IE they're dropping data along the way. I'm familiar with the 2GB file size limit on samba, and have mounted the PC side using the lfs flag. > > Problem 1: Incorrect listing > > Here's a list of the directory from the embedded box: > -r--r--r-- 1 root root 52646396 Jan 5 06:46 file1.ch10 > -r--r--r-- 1 root root 60755936 Jan 5 06:46 file2.ch10 > -r--r--r-- 1 root root 47606684 Jan 5 06:46 file3.ch10 > -r--r--r-- 1 root root 4920604376 Jan 5 05:51 file4.ch10 > > Here's that same listing, but of the samba mount of that directory on the PC: > > -r-xr-xr-x 1 root root 52646396 Jan 5 2007 file1.ch10 -r-xr-xr-x 1 > root root 60755936 Jan 5 2007 file2.ch10 -r-xr-xr-x 1 root root > 47606684 Jan 5 2007 file3.ch10 -r-xr-xr-x 1 root root 625637080 Jan 5 > 2007 file4.ch10 > > As you can see, files 1-3 list fine, but file4 is showing way short. I'm guessing this might be some sort of overflow condition, any ideas? > > Problem 2: Loss of data during transfer of large files. > When I try to transfer file4, i only get 41xxxxxxxx or so of the total > file size. This is the more pressing issue. > > Also, I cannot mount the samba share using CIFS. I use the line > > mount -t smbfs //server/share/ path/to/local/ -o user=u,pass=p,lfs > > to mount with SMBFS, and it works correctly, just doesn't display the large files. > However, when using the following: > > mount -t smbfs //server/share/ path/to/local/ -o user=u,pass=p,lfs > > I get "Mount error 5= Input/output error" > > Any thoughts? > > Thanks, > Matt ***Teletronics Technology Corporation*** This e-mail is confidential and may also be privileged. If you are not the addressee or authorized by the addressee to receive this e-mail, you may not disclose, copy, distribute, or use this e-mail. If you have received this e-mail in error, please notify the sender immediately by reply e-mail or by telephone at 267-352-2020 and destroy this message and any copies. Thank you. ******************************************************************* -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
First
|
Prev
|
Pages: 1 2 Prev: write list vs read list Next: [Samba] Help: justification for Linux PDC vs Windows... |