Re: start-stop-daemon with chroot ?

2008-07-11 Thread supermega
On 11 Lip, 09:30, Sven Joachim <[EMAIL PROTECTED]> wrote: > Hello supermega, > > do you also have a real name? > > On 2008-07-11 03:59 +0200, supermega wrote: > > > I'd like to use start-stop-daemon with chroot option, but I get a > > strange error. A test:

start-stop-daemon with chroot ?

2008-07-10 Thread supermega
Hi, I'd like to use start-stop-daemon with chroot option, but I get a strange error. A test: # start-stop-daemon --start --chroot /bin --exec ls start-stop-daemon: Unable to start ls: No such file or directory (No such file or directory) I should work, shouldn't it? When I run this: # start-stop-

Re: php5 and UTF BOM header

2007-08-11 Thread supermega
On 11 Sie, 09:50, Mathias Brodala <[EMAIL PROTECTED]> wrote: > Use an editor which allows you to omit the BOM, it's optional for UTF-8 > anyways. > As long as you send the correct Content-Type header, the output won't be any > different. > I know this solition and I use it for now, but it's again

php5 and UTF BOM header

2007-08-10 Thread supermega
Hi, my system is Debian stable Etch with: - apache22.2.3-4 - libapache2-mod-php55.2.0-8+etch7 PHP interpreter does not parse UTF BOM header bytes in UTF- encoded .php files and so I get a well known warning "Cannot modify header information - headers already sent" when trying to use heade

Re: CONFIG_IP_ROUTE_FWMARK not working in Debian !

2005-10-29 Thread supermega
It's a mistake, I modified it manualy... should be: 32764: from all fwmark 0x5 lookup isp2 32765: from lookup isp2 32766: from all lookup main 32767: from all lookup default But if there were no mark why would it affect the routing? I've logged the packets on FORWARD: iptables -A FORWARD -s $

Re: CONFIG_IP_ROUTE_FWMARK not working in Debian !

2005-10-18 Thread supermega
of course: # ip rule 0: from all lookup local 32765: from all fwmark 0x5 lookup isp2 32766: from all lookup main 32767: from all lookup default Packets from are dropped. If the ip rule looked like that: 0: from all lookup local 32765: from all fwmark 0x5 lookup isp2 32765: from lo

Re: CONFIG_IP_ROUTE_FWMARK not working in Debian !

2005-10-14 Thread supermega
well... it doesn't. I tested it once more with sarge/stable and 2.4 kernel. Funny thing: when the "ip rule fwmark" is added then the next rule - with lower preference - is checked, too (it can be main or "ip rule from" or anything). If the routes set by these 2 rules are the same then packet is a

Re: CONFIG_IP_ROUTE_FWMARK not working in Debian !

2005-10-10 Thread supermega
I don't think I need more complicated script.. I understand iproute2 and routing in linux quite well.. and this should work. My question was rather if I need to make any more OS tweaking (maybe in /proc/sys/net/ipv4 or whatever). Or if there is something blocking fwmark installed by default. --

Re: CONFIG_IP_ROUTE_FWMARK not working in Debian !

2005-10-10 Thread supermega
Thank you both. Nelson Castillo, can you tell me what kernel you're using? So.. - I download sarge/stable, install minimal system - apt-get iproute - do the following commands: #adding new routing table echo "200 isp2" >> /etc/iproute2/rt_tables # setting up routing

Re: CONFIG_IP_ROUTE_FWMARK not working in Debian !

2005-10-10 Thread supermega
Thanks for your answer. But way the first packet only? All packets from are marked and all should go to table isp2. Even with per-port load balancing in most services dest. port is always the same and I don't have to use conntrack/connmark (in Slackware). -- Tomek -- To UNSUBSCRIBE, email t

CONFIG_IP_ROUTE_FWMARK not working in Debian !

2005-10-09 Thread supermega
hello, I tried to post the topic on many groups.. with no answer. I would like to use "ip rule add fwmark" and I think it's just not working in debian. system debian testing from 2005-10-07 kernel 2.6.12-1-386 iproute2 from apt-get, ss041019 iptables from apt-get, 1.3.3 problem I have