From: "Antonis Lazaridis" <antonis_san@hotmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] traffic shaping
Date: Fri, 08 Feb 2002 05:17:14 +0000 [thread overview]
Message-ID: <marc-lartc-101314551313152@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416818@msgid-missing>
> > But it feels like i found a bug or something. The "bug" is:
> > "it's impossible to find on the internet how to start multiple smbs"
>Are you speaking seriously ? It might be samba's "bug" but
>definitely not related to LARTC.
Sure, not related directly to LARCT.
Anyway, "Debugging" finished! :)
Problem solved, with some help from samba list.
If this is not a NeverAskedQuestion and somebody else needs the info:
You have to start the smb deamons with different .conf files, setting
different parameters for these:
- Interfaces, using "interfaces ="
- IP addresses, using "socket address ="
- log files directories, using "log file ="
- lock directories using "lock directory ="
(*) that was what i was missing that...
(Martin, you were wrong about the pid files, there are smb.pid and nmb.pid
files for every deamon)
- and offcourse use "bind interfaces only = yes"
Then you can define different directories to share, in the different conf
files. They will be served from different smb deamons, which can also be
different hosts or (YES!) different IPs.
It works.
Now i try following:
Let's say i give max 10Mbps bandwidth to the folder where i keep video
files. Can i change this dynamically?
Like this: if another user tries to access another video file, increase the
bandwidth for this IP to 20Mbps.
Or if this is not possible, dynamically sharing the 10 Mbps bandwidth, %mbps
for each user.
Is something like this possible with Linux QoS?
antonis.
_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2002-02-08 5:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 12:22 [LARTC] traffic shaping Wouter
2001-01-04 18:17 ` Sander
2001-01-05 3:52 ` Sander
2001-01-05 11:42 ` Wouter
2001-01-05 13:56 ` Junus
2001-01-05 13:56 ` Junus
2001-01-06 9:25 ` [LARTC] Traffic shaping Bruno
2001-01-07 13:54 ` Junus
2001-12-25 12:15 ` [LARTC] Traffic Shaping Sahil Gupta - NET4U
2001-12-25 12:27 ` bert hubert
2001-12-25 12:33 ` Sahil Gupta - NET4U
2001-12-25 12:34 ` Sahil Gupta - NET4U
2001-12-25 12:42 ` bert hubert
2002-01-22 4:52 ` [LARTC] traffic shaping Antonis Lazaridis
2002-01-22 7:44 ` Martin Devera
2002-01-23 8:23 ` Martin Devera
2002-01-23 9:42 ` Antonis Lazaridis
2002-01-23 9:51 ` Martin Devera
2002-01-25 8:11 ` Antonis Lazaridis
2002-01-26 23:00 ` Martin Devera
2002-01-27 1:21 ` Re[2]: " Will Lotto
2002-01-27 8:47 ` Stef Coene
2002-02-08 5:17 ` Antonis Lazaridis [this message]
2002-02-08 17:22 ` Riaz Mahmood
2006-10-04 20:45 ` Roberto Scattini
2007-05-06 20:14 ` [LARTC] Traffic Shaping Rangi Biddle
2007-05-07 8:25 ` AW: " Simo
2007-05-07 18:06 ` Rangi Biddle
2007-05-08 3:16 ` Rangi Biddle
2007-10-24 18:37 ` [LARTC] Traffic shaping Mohammad Shakir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-101314551313152@msgid-missing \
--to=antonis_san@hotmail.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.