On Tue, 14 May 2002, Gerald Carter wrote:
> > > $ smbclient //server/share -c "ls" -Tc
> > > added interface ip=172.16.1.3 bcast=172.16.1.255 nmask=255.255.255.0
> > > Segmentation fault
Fixed in SAMBA_2_2 & HEAD.
cheers, jerry
-
On Tue, 14 May 2002, Richard Sharpe wrote:
> On Mon, 13 May 2002, Jay Ts wrote:
>
> > Hi,
> >
> > Just in case I'm the first to have noticed this:
> >
> > $ smbclient //server/share -c "ls" -Tc
> > added interface ip=172.16.1.3 bcast=172.16.1.255 nmask=255.255.255.0
> > Segmentation fault
>
On Mon, 13 May 2002, Jay Ts wrote:
> Hi,
>
> Just in case I'm the first to have noticed this:
>
> $ smbclient //server/share -c "ls" -Tc
> added interface ip=172.16.1.3 bcast=172.16.1.255 nmask=255.255.255.0
> Segmentation fault
Well, it happens to me as well. Did you manage to get a tracebac
Jay Ts wrote:
>
> $ smbclient //server/share -c "ls" -Tc
> added interface ip=172.16.1.3 bcast=172.16.1.255 nmask=255.255.255.0
> Segmentation fault
BTW, I should have mentioned that I'm running Samba 2.2.4
on Red Hat 7.1 here.
Jay Ts
[EMAIL PROTECTED]
Jay Ts wrote:
> Just in case I'm the first to have noticed this:
>
> $ smbclient //server/share -c "ls" -Tc
> added interface ip=172.16.1.3 bcast=172.16.1.255 nmask=255.255.255.0
> Segmentation fault
>
> This happened when out of curiosity, I wondered if
> it was possible to execute some smbcli
Hi,
Just in case I'm the first to have noticed this:
$ smbclient //server/share -c "ls" -Tc
added interface ip=172.16.1.3 bcast=172.16.1.255 nmask=255.255.255.0
Segmentation fault
This happened when out of curiosity, I wondered if
it was possible to execute some smbclient commands,
such as a c