FreeBSD Port: verlihub-0.9.8.e.r1,1

2009-12-15 Thread Daniel Dvořák
Hi all, after upgrading my verlihub to the latest version, the hub does not work anymore. Segmentation Fault. What´s happen to it ? And how may I help to solve the problem ? At the begging I snip gdb output, if it helps. # gdb /usr/local/bin/verlihub /usr/home/verlihub/verlihub.core GNU gdb

FreeBSD Port: mc-4.6.2 lynx-like motion forgot

2009-09-01 Thread Daniel Dvořák
Hi all, at the beginning I apologize for cross-mailling becuase I really don´t know which mailling list or mail address is the best one for sending my problem. I needed to set up lynx-like motion in configuration of mc. I did it and saved configuration. The application told me that it saved m

FW: FreeBSD Port: portupgrade-2.4.6,2

2008-12-25 Thread Daniel Dvořák
ebsd.org/pipermail/freebsd-ports/2008-December/author.html#51908> author ] _ On Thu, 25 Dec 2008 14:37:03 +0100 Daniel Dvořák http://lists.freebsd.org/mailman/listinfo/freebsd-ports> > wrote: >Hi, > >my portugrade does not upgrade my ports at all. I wanted to upgrad

FreeBSD Port: portupgrade-2.4.6,2

2008-12-25 Thread Daniel Dvořák
Hi, my portugrade does not upgrade my ports at all. I wanted to upgrade some ports with security risks. I upgraded my ports successfuly 2 months ago without any problem. server# portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap1.Fre

FreeBSD Port: monitord-0.4.1_2

2008-07-10 Thread Daniel Dvořák
Hi all, I needed to resolve the problem with verlihub, which refuses to properly run at the start of router. I tried using rcorder various tricks with orderring to run verlihub in the background of other processes. Nothing helped me. I have decided to use monitord, which monitors wheth

FreeBSD Port: quagga-0.99.10_3

2008-07-10 Thread Daniel Dvořák
mportant! After that, I stopped watchquagga daemon and I restarted quagga daemons, no wunder that error messages haven´t been appearing anymore. Voila! IMHO, the problem is connected with watchquagga daemon deffinitely. Daniel -Original Message- From: Daniel Dvořák [mailto:[EMAIL PROTECT

RE: FreeBSD Port: quagga-0.99.9_7

2008-07-07 Thread Daniel Dvořák
And do you use watchquagga in rc.conf ? I do. Daniel -Original Message- From: Sergey Matveychuk [mailto:[EMAIL PROTECTED] Sent: Monday, July 07, 2008 4:21 PM To: [EMAIL PROTECTED] Cc: 'Boris Kovalenko'; [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Daniel Dv

RE: FreeBSD Port: quagga-0.99.9_7

2008-07-07 Thread Daniel Dvořák
th solving the problems, which I have described them last week ? -Original Message- From: Sergey Matveychuk [mailto:[EMAIL PROTECTED] Sent: Sunday, July 06, 2008 1:22 AM To: [EMAIL PROTECTED] Cc: 'Boris Kovalenko'; [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7

RE: FreeBSD Port: quagga-0.99.9_7

2008-07-03 Thread Daniel Dvořák
Hi Boris, :) My last current problem with quagga is associated with the new multicast API for FreeBSD 7.0-RELEASE. OSPF does not work at all, and I am very surprised that no one has pointed out since February, which is officially FreeBSD 7 in the world. OSPF indefinitely crashes on the signal

RE: FreeBSD Port: quagga-0.99.9_7

2008-07-03 Thread Daniel Dvořák
Hi Boris, SMUX does not work as is. I know that worked for me, I know it safely, I was setting up to and it worked well for me, but something has changed. What's wrong? SMUXisKO# egrep smux /etc2/snmp/snmpd.conf smuxpeer .1.3.6.1.4.1.3317.1.2.1 smuxpeer .1.3.6.1.4.1.3317.1.2.2 smuxpeer .1.3.6.1.

RE: FreeBSD Port: quagga-0.99.9_7

2008-07-03 Thread Daniel Dvořák
Hi Boris, new version of quagga 0.99.10 behaves strange when running daemons. It logs events, which in version 0.99.9 is not appeared. The contents of the records of concern to me when they wrote "exiting", although quagga continues to work, and PID numbers coincided with a statement ps aux is

RE: FreeBSD Port: quagga-0.99.9_7

2008-07-03 Thread Daniel Dvořák
, IS-IS route software system3# /etc2/rc.d/quagga status Sleeping 10 seconds to obtain dynamic routing information... system3# It is new broken style. :D Respect, Daniel -----Original Message- From: Daniel Dvořák [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 11:43 AM To: 'Bor

RE: FreeBSD Port: quagga-0.99.9_7

2008-07-03 Thread Daniel Dvořák
>Very strange, but looks like this is a problem in system's rc, as my rc does >not have 34978 lines of code :) Hi Boris, The problem I haven´t solved since February, when I met with him again by chance in July when dealing with another problem, a new multicast api in FreeBSD 7. I will write an

RE: FreeBSD Port: quagga-0.99.9_7

2008-07-03 Thread Daniel Dvořák
Hi Boris, I am sorry for my late answer. I was on holidays. >I remember Makefile has ENABLE_VTY_GROUP knob, so You may use it. Is it what >You need? egrep "ENABLE_VTY_GROUP" /usr/ports/net/quagga/Makefile .if defined(ENABLE_VTY_GROUP) CONFIGURE_ARGS+=--enable-vty-group=${ENABLE_VTY_GROUP}

FreeBSD Port: quagga-0.99.9_7

2008-06-14 Thread Daniel Dvořák
Hi Boris, I would like to turn your attention on one little bug in quagga on FreeBSD. Why don´t we user groupname quaggavty from the beginning when the quagga had been ported to FreeBSD ? What do I mena ? I will show you the diffrence between quagga on Debian and on our FreeBSD. They use

RE: FreeBSD Port: denyhosts-2.6_1 (fwd)

2008-03-19 Thread Daniel Dvořák
Thank you. We will look forward for 2.7. Bye Dan -Original Message- From: Phil Schwartz [mailto:[EMAIL PROTECTED] Sent: Monday, March 17, 2008 2:41 PM To: Mohacsi Janos Cc: Daniel Dvořák Subject: Re: FreeBSD Port: denyhosts-2.6_1 (fwd) Hello, This will be fixed in 2.7. For now

FreeBSD Port: denyhosts-2.6_1

2008-03-16 Thread Daniel Dvořák
Hi Janos, I have 2 servers with denyhosts and everytime I receive the security mail with many attempts to login to my systems and everytime I am surprised why that, if I have denyhosts. I have found out from this link (https://bugs.launchpad.net/ubuntu/feisty/+source/denyhosts/+bug/133569)

RE: FreeBSD Port: quagga-0.99.9_7

2008-02-26 Thread Daniel Dvořák
Yes, it is strange, but it is there, how could I help you to understand more this problem ? Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, F

RE: FreeBSD Port: quagga-0.99.9_7

2008-02-26 Thread Daniel Dvořák
Yes, it is strange, but it is there, how could I help you to understand more this problem ? Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, F

RE: FreeBSD Port: quagga-0.99.9_7

2008-02-26 Thread Daniel Dvořák
Yes, it is strange, but it is there, how could I help you to understand more this problem ? Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, F

RE: FreeBSD Port: cacti-0.8.7b

2008-02-26 Thread Daniel Dvořák
: cacti-0.8.7b Daniel Dvořák wrote: > On the 16th of December 2007, you wrote these sentences in UPDATING > file about Plugin Architecture: > Plugin support is dropped again and will not revive anymore in the port. > A reason for that is the patch is unofficial and there are lo

RE: FreeBSD Port: cacti-0.8.7b

2008-02-26 Thread Daniel Dvořák
: cacti-0.8.7b Daniel Dvořák wrote: > On the 16th of December 2007, you wrote these sentences in UPDATING > file about Plugin Architecture: > Plugin support is dropped again and will not revive anymore in the port. > A reason for that is the patch is unofficial and there are lo

RE: FreeBSD Port: cacti-0.8.7b

2008-02-26 Thread Daniel Dvořák
: cacti-0.8.7b Daniel Dvořák wrote: > On the 16th of December 2007, you wrote these sentences in UPDATING > file about Plugin Architecture: > Plugin support is dropped again and will not revive anymore in the port. > A reason for that is the patch is unofficial and there are lo

RE: FreeBSD Port: quagga-0.99.9_7

2008-02-26 Thread Daniel Dvořák
Yes, it is strange, but it is there, how could I help you to understand more this problem ? Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, F

RE: FreeBSD Port: quagga-0.99.9_7

2008-02-26 Thread Daniel Dvořák
Yes, it is strange, but it is there, how could I help you to understand more this problem ? Yes, I meant these: zebra is running as pid ospfd is running as pid bgpd is running as pid etc. Bye Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, F

FreeBSD Port: cacti-0.8.7b

2008-02-25 Thread Daniel Dvořák
Hi sem, I value your long work for cacti port in FreeBSD and your opinion is well-founded unlike mine. On the 16th of December 2007, you wrote these sentences in UPDATING file about Plugin Architecture: Plugin support is dropped again and will not revive anymore in the port. A reason for

FreeBSD Port: quagga-0.99.9_7

2008-02-25 Thread Daniel Dvořák
Hi Boris, I have 2 question to you. Sometimes when I use quagga script for start, restart or status commands, there turns up strange message about unexpected operator on the different routers with quagga. I have some routers based on Linux and these errors are not there. # /etc2/rc.d/quagg

FreeBSD Port: quagga-0.99.9

2007-10-06 Thread Daniel Dvořák
Hi all, today I wanted to upgrade my quagga ports in 4 diffrent systems and the upgrading process has failed with these messages below for all 4 systems the same: quagga-0.99.9 < needs updating (port has 0.99.9_2) ... gmake[2]: Leaving directory `/usr/ports/net/quagga/work/qua

FW: FreeBSD Port: uptimed-0.3.7

2007-08-05 Thread Daniel Dvořák
I have no response, so I try to send to public. _ From: Daniel Dvořák [mailto:[EMAIL PROTECTED] Sent: Friday, August 03, 2007 11:09 PM To: '[EMAIL PROTECTED]' Subject: FreeBSD Port: uptimed-0.3.7 Hi Andy, I ask you about updating uptimed to the last release 0.3.11.

FreeBSD Port: bash-3.2.17_2

2007-07-24 Thread Daniel Dvořák
Hi Obrien, portupgrading bash from 3.1.17 to 3.2.17_2 is finished with error about missing autoconf. It is interesting why bash needs autoconf while compiling and for the second I have autoconf package, but it is useless for that as you can see below. What can I do to fix it? Tha

FreeBSD Port: quagga-0.99.7_2 - quagga restartting is broken ?

2007-06-27 Thread Daniel Dvořák
Hi Boris, I have a problem with restarting quagga by our script for a long time, I guess since that time when the script was moved from /etc/rc.d/ to /usr/local/etc/rc.d/. And before this major change each restarting of quagga was successful. I can swear on it. :) When I restart quagga, the ro

RE: FreeBSD Port: ipfw2dshield-0.5

2007-06-15 Thread Daniel Dvořák
-Original Message- From: Jeremy Chadwick [mailto:[EMAIL PROTECTED] Sent: Saturday, June 16, 2007 1:04 AM To: Daniel Dvo??ák Cc: 'John Merryweather Cooper'; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: FreeBSD Port: ipfw2dshield-0.5 > FreeBSD by default sets PATH to what you see in th

RE: FreeBSD Port: ipfw2dshield-0.5

2007-06-15 Thread Daniel Dvořák
- From: John Merryweather Cooper [mailto:[EMAIL PROTECTED] Sent: Friday, June 15, 2007 11:41 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: FreeBSD Port: ipfw2dshield-0.5 Daniel Dvořák wrote: > Hi Frank, > > I have some strange messages from cron daemo

FreeBSD Port: ipfw2dshield-0.5

2007-06-15 Thread Daniel Dvořák
Hi Frank, I have some strange messages from cron daemon about ipfw2dshild. And what is more interesting it appears only on WRAP platform (PC ENGINE), not on other hardwares. This mail for root from Cron Daemon: Message 1: >From [EMAIL PROTECTED] Sat Jan 1 00:03:07 2000 Date: Sat, 1 Jan 2000 00

FreeBSD Port: lsof-4.79A

2007-06-03 Thread Daniel Dvořák
Hi ler, today I have decided to upgrade my ports and have checked /usr/ports/UPDATING. There were nothing about lsof concretely in recently. When the process has begun, these messages appeared shortly: => Attempting to fetch from ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/NEW/. lsof_4.79A.

RE: FreeBSD Port: phpMyAdmin-2.10.0.2

2007-03-18 Thread Daniel Dvořák
>Can you try this small test to see if your php setup really does have >broken support for ctype_digit() ? >% php -r 'print ctype_digit(1234);' Yes, it returned 1. Should print '1'. If that doesn't work, then examine /usr/local/etc/php/extensions.ini -- does it contain the line extension=ctype

FreeBSD Port: phpMyAdmin-2.10.0.2

2007-03-16 Thread Daniel Dvořák
In March there were reports about bad dependences for phpMyAdmin, specially missing php-ctype like this http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2007-March/114357.html It seems that the latest phpmyadmin-2.10.0.1 release now requires functions from the PHP ctype module. undefi

FreeBSD Port: dnstop-20070105

2007-02-10 Thread Daniel Dvořák
Hi, The port has sources which did not work. # portupgrade -Rr dnstop ---> Upgrading 'dnstop-20061122' to 'dnstop-20070105' (dns/dnstop) ---> Building '/usr/ports/dns/dnstop' ===> Cleaning for dnstop-20070105 => dnstop-20070105.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempti

FW: mc not execute after portupgrading pkg-config\*

2007-02-02 Thread Daniel Dvořák
september 06 – october 06, IMHO something with subshell.c is not good. Daniel _ From: Daniel Dvořák [mailto:[EMAIL PROTECTED] Sent: Thursday, October 26, 2006 9:01 PM To: 'freebsd-ports@freebsd.org' Subject: mc not execute after portupgrading pkg-config\* Hi all, plea

mc not execute after portupgrading pkg-config\*

2006-10-26 Thread Daniel Dvořák
Hi all, please help me with mc. It does not work in 2 and more ssh sessions. After reading UPDATING file, there are last instruction about upgrading pkg-config. Portupgrade users: pkgdb -Ff portupgrade -rf pkg-config\* I did it as it is recommended. Later I opened 2 ssh s

FW: kismet scanning deos not work for me

2006-09-05 Thread Daniel Dvořák
uot; P.S.: mail me directly please. _ From: Daniel Dvořák [mailto:[EMAIL PROTECTED] Sent: Sunday, September 03, 2006 1:44 AM To: 'freebsd-ports@freebsd.org' Subject: kismet scanning deos not work for me Hi all, my config of kismet.conf is attached. I read the kismet manual

kismet scanning deos not work for me

2006-09-02 Thread Daniel Dvořák
Hi all, my config of kismet.conf is attached. I read the kismet manual from the begining to the end and Kismet does not work for me. Even when I manually reconfigure my card from ahdemo mode to monitor mode, after execute kismet -n command, these lines turn up at once: Waiting for channel con

RE: FreeBSD Port: samba-3.0.23,1

2006-07-12 Thread Daniel Dvořák
age- > From: Timur I. Bakeyev [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 12, 2006 11:03 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: FreeBSD Port: samba-3.0.23,1 > > Hi, Daniel! > > On Wed, 12 Jul 2006 04:28:19 +0200 > Daniel Dvořák <[EM

FreeBSD Port: arpwatch-2.1.a14

2006-07-11 Thread Daniel Dvořák
Hi all, let me ask you about arpwatch. The port under FreeBSD does not support the important switch -p, which we can find for example in Debian Linux. This switch is about "don´t put to promisccuous mode", which is really needed for example wireless cards, where promisc kills usually the traffic

FreeBSD Port: samba-3.0.23,1

2006-07-11 Thread Daniel Dvořák
Hello all, I wait for samba 3.0.23 for a long time in hope that this ... ===> samba-3.0.23,1 broken IPC and code. *** Error code 1 Stop in /usr/ports/net/samba3. *** Error code 1 Stop in /usr/ports/net/samba3. ... will not show with new version, I am wrong about this evidently. :( Last tim

FreeBSD Port: portupgrade-2.1.3.2, 2 - help me please, the port in short time is broken again, what does it all mean ?

2006-07-02 Thread Daniel Dvořák
Hi all, I upgraded my portupgrade to version 2.1.3 12 days ago, it was broken, okay after reading Makeconf changes a go back by portupgrading to 2.1.4, actualy 2.1.1,2. I was glad to see the portupgrade is working again. Today cron/portsnap update told me, there is new version of portupgrade,