similar to: smbsh questions

On Fri, 21 May 1999, Sami Cokar wrote: > Hello, > how do you use smbsh? I have not found any dox on it other than how to > compile it. any help would be appreciated. Thanx. SMBSH is really neat. After you compile and install it (./configure --enable-smbwrapper ; make ; make install does it) you simply run it - it'll give you a login/pw and your usual shell prompt. You then can

Hi, currently I am running Solaris 8 and I am trying to install Samba so that I can run smbsh to access a Windows server. I do the following: ./configure --prefix=/usr/local/samba --with-smbwrapper make make install All the documentation I have seen says what I am doing is correct. Neither the configure nor any of the make commands fail. And once the installation is complete everything else

Someone asked today about smbfs on HPUX. The basic answer to that is that smbfs is _very_ operating system specific so it would take quite a lot of work to get it to run on another OS. There is hope though. Over the past few days I have been developing something called smbwrapper (and smbsh). This offers most of the capabilities of smbfs in a way that makes it somewhat portable. It also provides

I tried linking smbwrapper.so directly into bash, but that only works for bash and not any of the subprocesses it runs. That is bash can cd into the /smb directory and I can do an echo * to list files. But if I run a system command (ls, emacs) they can't see the /smb directory because they aren't linked with smbwrapper.so. -----Original Message----- From: Dirk De Wachter

Has anyone seen the following problems with smbsh under Solaris 8: 1. smbsh with no options does not prompt correctly for the Username: and Password:. You can enter them if you know that is what you need and it will continue on. If you use -U username it works. 2. Once smbsh is running, any command results in a "[1]+ Stopped" with bash. If you

I guess the uSSubject line says it all. Does smbwrapper/smbsh actually work? It took some editing to get smbwrapper to actually compile, but the changes seemed obvious (different versions of gcc?). However when I try to execute smbsh (RH7.0), I get to the message ERROR: can't get smbw shared lock which looks like it could be a difference between the way different OS handle things. So,

Hi I can't get 2.0.7 to compile under linux 6.4. My configure looks like: ./configure --with-smbwrapper --with-automount --with-smbmount but when I make, all goes well until: Compiling smbwrapper/shared.c Linking bin/smbsh Compiling smbwrapper/smbw.c with -fpic smbwrapper/smbw.c:1429: warning: `struct stat64' declared inside parameter list smbwrapper/smbw.c:1429: warning: its scope

samba@samba.org Serge Gavrilov <serge@pdmi.ras.ru> Ed Schernau <ed@schernau.com> Jeremy Allison <jeremy@valinux.com> Cristian POP <cpop@compas.dntcj.ro> Ed Schernau <ed@schernau.com> John Evans <samba@kilnar.com> David Bullock <davidb@loftuscomp.com.au> Gunnar Lindholm <gunnar.lindholm.320@student.lu.se> Junaid Iqbal

Version 2.0.5a (same prob w/2.0.4b, though). smbsh segfaults after I enter my password. As root, it just seg faults. As my login user, it dumps core. Attached is a script of an strace of it. Running RH 6.0, kernel 2.2.10, AMD K6-2/350, 64M RAM. Configure options were: CFLAGS="$RPM_OPT_FLAGS" ./configure --prefix=%{pref} --libdir=/etc \ --with-lockdir=/var/lock/samba

This smbsh rips! However, it unfortunately only rips on one of the machines here ;) On the others, which have basically the same config but a 2.2.5 kernel (vs 2.2.9) smbsh runs fine, and a cd to /smb works, but nothing else. 'ls' produces a listing of the directory where smbsh started in - it seems to me that no 'preloading' is being done of smbwrapper.so. Is there a way to test

Hi Oka, It worked! All works fine in the tcsh. Thanks! Kurt ----- Original Message ----- From: Stam, Kurt To: 'kurt@oneheartbreak.com' Sent: Friday, August 25, 2000 4:33 PM Subject: FW: smbsh - Samba 2.0.7 - Solaris 2.6 -----Original Message----- From: Oka Setiawan [mailto:oka@indigopool.com] Sent: Friday, August 25, 2000 4:37 PM To: Stam Kurt Subject: RE: smbsh - Samba 2.0.7 -

I have built, installed, and run 2.0.6 successfully without smbmount, but want to do it with this time. I know that it's not part of samba, but am hoping someone can tell me if I'm making a simple mistake. It's possible that it's not even samba related. I'm a novice at this and have not gotten very good at figuring out what's wrong when something doesn't build

I am having a problem with smbsh. I get the following error after I enter my username and password: ERROR: can't get smbw shared lock (Invalid argument) I am running linux 7.2 with samba 2.2.2. The error message is produced from the function lockit(void) in smbwrapper/shared.c. The error originates in file lib/util.c in function: fcntl_lock(shared_fd,SMB_F_SETLKW,0,1,F_WRLCK) fcntl_lock

I continue to have the same problems in Samba 2.0.6 with smbfs that I was seeing in 2.0.5: (1) After a mount (mount -t smbfs etc.), the volume is often not yet fully mounted. For instance, if I write a Perl script like: system('mount -t smbfs -o password=pwd //MACHINE/SHARE /mnt/machine_share'); system('find /mnt/machine_share > find.out'); the 'find' may not find

Samba 2.0.6 (as distributed w/ FreeBSD 3.4 Walnut Creek CDs in ports collection) I'm trying to setup a samba server on my network. My network is not quite as simple as examples in documentation, because it has an NT server running as a PDC. I'm following the troubleshooting steps in book "teach yourself samba in 24 hrs" chapter 11 trouble shooting. I get to "step 7:

Hi ! The O'Reilly "Using Samba" book, recommend not to include smbmount support as it is for Linux only: "This feature wasn't being maintained at the time the book was written, so the Samba team made it an optional feature and provided smbwrapper instead. The smbwrapper feature works on more Unix platforms than smbmount, so you'll usually want to use --with-smbwrapper

Greetings, I don't know how common an issue this is as I haven't found much in the list archives that was helpful to me, so I'm hoping for some pointers. FYI, we have samba 2.3.3a-6 running on the 2.4.18-10 kernel. There seems to be an issue with smbfs mounts at times where connectivity may be lost (e.g. Win share becomes unavailable) causing local processes such as lsof or ps,

After fighting with trying to rebuiled my src.rpm file. I decided to use a plain old fashion compile from the tar files. which worked ok, no settings changed. at about 11pm last night I finished and noticed a few things that made me a bit uneasy. 1) all the Samba bin files were installed in /usr/local/samba/.. 2) no smb.conf file was created. I used ./configure, make , make install when I

Hello! The top-level configure.in in the CVS version of Samba uses "echo" instead of the standard AC_MSG_* macros provided by Autoconf. I could not find any reasons for not using AC_MSG_*. "cvs log configure.in" doesn't list any reasons. "cvs annotate configure.in" doesn't work for read-only CVS because the CVS server for Samba is too old! The attached

This is the list of problems I had with samba-2.0.6 so far. Can anyone tell me if he can reproduce them and if he considers them as problems? 2.0.6 on linux 2.2.13 or 2.0.33 1) sighup/log reopening doesn't always work: connections that are already active keep logging to the old logs; logrotate rotates/zip the logs and samba stops logging completely till restart. 2) Localized chars. I have