similar to: [2.6 patch] smbfs: make some functions static

Am 27.06.2000 19:58:44 schrieb urban: > On Tue, 27 Jun 2000 klaus-georg.adams@rwg.de wrote: > > > > > Hi Andrew, > > your patch from 2.2.15 to 2.2.16, backing out the older protocol levels breaks > > reading from an OS/2 LAN Server. > > The appended patch fixes things for me (against 2.2.16). > > This backs out a lot of desired changes. For example I think

Hi, I'm sure that you are all aware that the mount utilities that ship with samba are designed to compile and run only with Linux 2.1 series development kernels. I'll _try_ keep this short and sweet while doing my best to explain what I have done, since I have a tendancy to ramble on. I have two boxes, one Linux with libc5, and another with Linux and Glibc2 (aka libc6). The Samba

The Coverity checker found that if req was NULL because find_request returned NULL, this resulted in a break from the switch, but req was later dereferenced (look at the last line of this patch). Signed-off-by: Adrian Bunk <bunk@stusta.de> --- linux-2.6.12-rc1-mm2-full/fs/smbfs/request.c.old 2005-03-25 00:45:08.000000000 +0100 +++ linux-2.6.12-rc1-mm2-full/fs/smbfs/request.c 2005-03-25

Hi GNU command 'cp' normally looks for the block size of the destination and then uses such buffer to copy the file. Unfortunately you are settings block size for smbfs filesystems as 512 and using 'cp' then wastefully generates a lot of small (for ethernet) packets. I was surprised that using 'cat a >/net/b' is almost TWICE as fast than the traditional 'cp a

Jan Niehusmann <jan@gondor.com> wrote: > > Yesterday, I got the following error with 2.6.16.13 during a file copy > from a smb filesystem over a wireless link. I guess there was some error > on the wireless link, which in turn caused an error condition for the > smb filesystem. > > In the log, smb_file_read reports error=4294966784 (0xfffffe00), which > also shows up

A friend of mine is running Samba (samba-2.0.3-8) on a couple RedHat Linux 6.0 machines. He is sharing files bilaterally at work with a WinNT machine and at home with a Win9x machine. In both places, he is getting a large number of SMB error messages. I'm not sure whether these are from the smbfs (smbmount) or from the Windoze machines accessing the Linux drives, though I suspect the

Forgot to provide errors from my samba.log [2004/10/30 19:37:00, 0] tdb/tdbutil.c:tdb_log(725) tdb(/usr/local/samba/var/locks/gencache.tdb): tdb_lock failed on list 4 ltype=1 (Bad file descriptor) [2004/10/30 19:37:00, 0] tdb/tdbutil.c:tdb_log(725) tdb(/usr/local/samba/var/locks/gencache.tdb): tdb_lock failed on list 4 ltype=1 (Bad file descriptor) <shrug>, oplocks is turned off, so

All, Has anyone seen this before? This appears to be a Swift or app_swift bug. I'm having a difficult time finding any information or support on this. Asterisk version: Asterisk 11.6-cert4 built by asterisk @ ivrd02 on a x86_64 running Linux on 2014-08-11 13:55:25 UTC OS: Linux livrp03 2.6.32-431.11.2.el6.x86_64 #1 SMP Mon Mar 3 13:32:45 EST 2014 x86_64 x86_64 x86_64 GNU/Linux When

While using smbmounted shares I get the following errors in my syslog: ---<snip>-- Nov 27 18:27:45 cayman kernel: smb_request: result -104, setting invalid Nov 27 18:27:46 cayman kernel: smb_retry: successful, new pid=529, generation=2 --</snip>-- Is this something I should worry about? I am using RH 6.2, linux 2.4.16 and samba-2.0.10-0.62 installed from RPM. Regards, Peter

I'm getting a SIGSEGV at ast_slinear_saturated_multiply at the line: 351 res = (int) *input * *value; It's called from ast_frame_adjust_volume. The frame looks like: (gdb) print *f $6 = {frametype = AST_FRAME_VOICE, subclass = {integer = 100021, format = { id = AST_FORMAT_SLINEAR16, fattr = {format_attr = { 0 <repeats 64 times>}, rtp_marker_bit = 0

smb_request: result -104, setting invalid this repeatedly occurs in the messages log and the kernel log. does anyone know how i can look this up and find out what it means? samba appears to be working fine but i'd like to get to the bottom of it. cheers, kev

Hi, I am running samba 3.0.4 on my fedora box and I have been noticing a message like this showing up in /var/log/messages every hour, on the hour. May 16 10:01:00 box kernel: smb_request: result -104, setting invalid May 16 10:01:00 box kernel: smb_retry: successful, new pid=21347, generation=9 I assume that this message is being caused somehow by a cron job (diskcheck) that is going through

Hi All: When I use samfs, sometimes I got the following messages, Mr. Google says this is because the windows client use the share, and the connection is "reconnected"! Does it right? How to ward off the error? Is there any potential problem if I ignore it? My actions are smbmount and smbumount some shares. Sometimes some shares are smbumount before they mounted (thus cause a

I earlier this week upgraded from Debian woody to sarge on a machine that does a nightly backup to another machine via a samba share. Since then I have had some issues with accessing that share with I believe are a result of the upgrade. I upgraded the kernel at the same time to 2.4.27-1-686 #1 via apt-get, which might be the related to the problem. Smbfs is version 3.0.6-3

Dear Samba Support, Currently I'm using redhat 6.2 with kernel version 2.2.14-5.0 and samba server version : samba-2.0.6-9 I have configured our samba server as member of NT domain. Everything works well, ie: I can join to PDC server and also mount our file server into our samba server But everyday in our samba server on file /var/log/messages, I got messages: Aug 30 14:49:49 ultest

Greetings, About 2 months ago, we decided to backup our Oracle test servers via samba rather than nfs -- the backups were just taking too long using nfs. No problem mounting the remote file share to the server and the backup took about one-third of the time. Yep, worked good...and still continues to out perform nfs hands down. Problem is - I'm receiving errors on both of the test servers.

Al writes: > On Thu, 22 Mar 2001, Andreas Dilger wrote: > > If this is the case, then all of the other zero initializations can be > > removed as well. I figured that if most of the fields were being > > zeroed, then ones _not_ being zeroed would lead to this problem. > > Other zero initializations in inode->u certainly can be > removed, but whether it's

[Since samba-bugs has been shutdown, I'm posting this here...] I'm running RH 7.0 with both 2.2.16 and 2.4.2 kernels I've got the following samba packages installed: samba-client-2.0.7-21ssl samba-common-2.0.7-21ssl I have a Windows NT 4 server (SP6a) which stores many of my files since I use both Linux and Windows to access them (Linux on my desktop, Windows on my laptop) I

I've got a fully updated Fedora Core 4 server crashing hard every week or two. I use Samba via smbmount and autofs to read & delete log files on 17 XP boxs and 6 NT4SP6 boxes as well as a couple other Windows files servers every 5 minutes. The first indication of a problem I get is smbmount stops working, then the server becomes unresponsive to the point where only a power slam will fix

Hello, I have a problem, I'm mounting a ntfs directory shared with w2k. I made "cd" to the mounted directory, I excute tar ... and the limit is 2Gb, and I receive the error: Jul 20 10:04:30 mail kernel: smb_get_length: recv error = 512 Jul 20 10:04:30 mail kernel: smb_request: result -512, setting invalid Jul 20 10:04:30 mail kernel: smb_retry: caught signal Jul 20 10:04:30 mail