RE: FreeBSD Port: quagga-0.99.9_7
Hi Sergey, I see your patch already in ports, so I needn´t use it for now. Am I right ? I did portupgrading of quagga yesterday and a functionality is back again. SYSTEM3# pkg_info | grep quagga quagga-0.99.10_3Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software SYSTEM3# /etc2/rc.d/quagga status zebra is running as pid 62557. ospfd is not running. ospf6d is running as pid 62571. Sleeping 10 seconds to obtain dynamic routing information... Thanks. Daniel P.S.: Boris, have you received my other mail about quagga or my reports is not new for you ? How can I help you with 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 Daniel Dvořák wrote: It is new style. SYSTEM3: system3# pkg_info | grep quagga quagga-0.99.10_2Free RIPv1, RIPv2, OSPFv2, BGP4, 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 Try the patch please. I'll commit it if it's OK. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: quagga-0.99.9_7
Daniel Dvořák wrote: VERSION 0.99.10# egrep lock /var/log/quagga/zebra.log ^^^ 2008/06/30 01:38:59 errors: ZEBRA: Could not lock pid_file /var/run/quagga/zebra.pid, exiting 2008/07/01 13:57:21 errors: ZEBRA: Could not lock pid_file /var/run/quagga/zebra.pid, exiting VERSION 0.99.10# egrep lock /var/log/quagga/ospfd.log 2008/06/30 01:38:59 errors: OSPF: Could not lock pid_file /var/run/quagga/ospfd.pid, exiting 2008/07/01 13:57:21 errors: OSPF: Could not lock pid_file /var/run/quagga/ospfd.pid, exiting VERSION 0.99.10# egrep lock /var/log/quagga/ospf6d.log 2008/07/01 13:57:21 errors: OSPF6: Could not lock pid_file /var/run/quagga/ospf6d.pid, exiting Looks like the daemons tried to run twice and fault. But I can see the problem on my boxes. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
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 Dvořák wrote: VERSION 0.99.10# egrep lock /var/log/quagga/zebra.log ^^^ 2008/06/30 01:38:59 errors: ZEBRA: Could not lock pid_file /var/run/quagga/zebra.pid, exiting 2008/07/01 13:57:21 errors: ZEBRA: Could not lock pid_file /var/run/quagga/zebra.pid, exiting VERSION 0.99.10# egrep lock /var/log/quagga/ospfd.log 2008/06/30 01:38:59 errors: OSPF: Could not lock pid_file /var/run/quagga/ospfd.pid, exiting 2008/07/01 13:57:21 errors: OSPF: Could not lock pid_file /var/run/quagga/ospfd.pid, exiting VERSION 0.99.10# egrep lock /var/log/quagga/ospf6d.log 2008/07/01 13:57:21 errors: OSPF6: Could not lock pid_file /var/run/quagga/ospf6d.pid, exiting Looks like the daemons tried to run twice and fault. But I can see the problem on my boxes. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: quagga-0.99.9_7
Daniel Dvořák wrote:
It is new style.
SYSTEM3:
system3# pkg_info | grep quagga
quagga-0.99.10_2Free RIPv1, RIPv2, OSPFv2, BGP4, 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
Try the patch please. I'll commit it if it's OK.
--
Dixi.
Sem.
Index: files/quagga.sh.in
===
RCS file: /home/pcvs/ports/net/quagga/files/quagga.sh.in,v
retrieving revision 1.12
diff -u -r1.12 quagga.sh.in
--- files/quagga.sh.in 28 Jun 2008 03:23:36 - 1.12
+++ files/quagga.sh.in 1 Jul 2008 17:24:05 -
@@ -37,6 +37,25 @@
rm -f $pidfile
}
+do_cmd()
+{
+ for daemon in ${quagga_daemons}; do
+ command=%%PREFIX%%/sbin/${daemon}
+ required_files=%%SYSCONF_DIR%%/${daemon}.conf
+ pidfile=%%LOCALSTATE_DIR%%/${daemon}.pid
+ if [ ${quagga_cmd} = start -a ! -f ${required_files} ]; then
+ continue
+ fi
+ if [ ${quagga_cmd} = stop -a -z $(check_process ${command}) ];
then
+ continue
+ fi
+ eval flags=\$\{${daemon}_flags:-\${quagga_flags}\\}
+ name=${daemon}
+ run_rc_command $1
+ _rc_restart_done=false
+ done
+}
+
# set defaults
load_rc_config $name
@@ -63,28 +82,19 @@
if [ ! -z ${quagga_extralibs_path} ]; then
/sbin/ldconfig -m ${quagga_extralibs_path}
fi
+ do_cmd start
;;
-stop|restart)
+stop)
quagga_daemons=$(reverse_list ${quagga_daemons})
+ do_cmd stop
;;
+restart)
+ quagga_daemons=$(reverse_list ${quagga_daemons})
+ do_cmd stop
+ quagga_daemons=$(reverse_list ${quagga_daemons})
+ do_cmd start
esac
-for daemon in ${quagga_daemons}; do
-command=%%PREFIX%%/sbin/${daemon}
-required_files=%%SYSCONF_DIR%%/${daemon}.conf
-pidfile=%%LOCALSTATE_DIR%%/${daemon}.pid
-if [ ${quagga_cmd} = start -a ! -f ${required_files} ]; then
- continue
-fi
-if [ ${quagga_cmd} = stop -a -z $(check_process ${command}) ]; then
- continue
-fi
-eval flags=\$\{${daemon}_flags:-\${quagga_flags}\\}
-name=${daemon}
-run_rc_command $1
-_rc_restart_done=false
-done
-
if [ ${quagga_delay} != 0 ]; then
echo Sleeping ${quagga_delay} seconds to obtain dynamic routing
information...
sleep ${quagga_delay}
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
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}
@${ECHO} ENABLE_VTY_GROUP Specify group for vty socket ownership
But it seems it is not enabled, isn´t it ?
I'm not sure if this is it, but I would like to behave the quagga in Debian
(Linux) and FreeBSD consistently.
In contrast, FreeBSD, Linux also has a file named quagga in the directory
/etc/pam.d/.
This file is not in FreeBSD in directory /usr/local/etc/pam.d or /etc/pam.d,
which I would in the case of second option even understand.
Perhaps to FreeBSD is not needed, but then what exactly in the table the
options of quagga when compiling means the possibility of PAM PAM
authentication for vtysh ?
However, the aim is this:
I have an user XXX and I want him to give sufficient privileges to manipulate
the quagga. I do not want to give him permission through sudo or through su
commands. In addition, I want in order to when in the vtysh.conf file, the user
XXX is set with the possibility of nopassword, vtysh not ask me for a password
to the quagga.
Sh interpreter is preset to FreeBSD systems, so that the goal is for these
above-mentioned conditions, to run vtysh straight and asks for nothing.
So far, only what the user see the error message:
Vtysh
Exiting: failed to connect to any daemons.
I do not know how to do, to ask me, but the goal is identical behavior quagga
on FreeBSD to Linux systems and that´s all, not more and not less.
Thank you.
Regards,
Daniel
-Original Message-
From: Boris Kovalenko [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 5:45 AM
To: [EMAIL PROTECTED]
Subject: Re: FreeBSD Port: quagga-0.99.9_7
Hello, Daniel!
I remember Makefile has ENABLE_VTY_GROUP knob, so You may use it. Is it what
You need?
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 group quaggavty for command vtysh and they help themself with
pam.d/quagga file.
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ls -l /etc/pam.d/quagga
-rw-r--r-- 1 root root 162 2007-09-26 08:20 /etc/pam.d/quagga user$
cat /etc/pam.d/quagga # Any user may call vtysh but only those
belonging to the group quaggavty can # actually connect to the socket
and use the program.
auth sufficient pam_permit.so
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] whoami user [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] ls -l /etc/quagga/vtysh.conf
-rw-rw 1 quagga quaggavty 63 2008-01-10 01:28
/etc/quagga/vtysh.conf [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] cat
/etc/quagga/vtysh.conf username user nopassword username root
nopassword log syslog [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] egrep
quaggavty /etc/group quaggavty:x:106:user [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] vtysh Hello, this is Quagga (version 0.99.5).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
server# exit
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
So here it works, now FreeBSD:
whoami
resu
ls -l /etc/pam.d/quagga
ls: /etc/pam.d/quagga: No such file or directory
ls -l /usr/local/etc/pam.d/quagga
ls: /usr/local/etc/pam.d/quagga: No such file or directory
ls -l /usr/local/etc/quagga/vtysh.conf
-rw-rw-r-- 1 quagga quagga 129 10 led 01:52
/usr/local/etc/quagga/vtysh.conf
cat /usr/local/etc/quagga/vtysh.conf
username resu nopassword
username root nopassword
log syslog
pw group show quagga
quagga:*:101:resu
vtysh
Exiting: failed to connect to any daemons.
Is possible to repair it ? How can I assit you ?
It would be good if new version 0.99.10 will count with vtysh like on
Debian.
Thank you.
Bye.
Daniel
Regards,
Boris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
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 another report the following e-mail on multicast. I found out that this strange number [: 34978: unexpected operator is not at all a number of lines of code, but it is PID! It is a PID of daemon, which was running, but for some reason has been terminated, for example by signal 11 and an integral condition is that in /var/run/ quagga is the rest of the daemon, the pid file is opened. So when a user runs /usr/local/etc/rc.d/quagga start|stop|restart so it just appears these nonsenses on some unexpected operators. I can not repeat it because I do not know how to simulate freezing process expediently. But I am sure that this is PID number, because in the list of running processes ps aux were two processes ospfd and one of them had the same number like the number in error message. When I was killed the process with the number from error message and restarted quagga, the error message suddenly disappeared, it would lead to think that, between February to July the error unexpected end of the process become, and that I am, of course, it could not even see, and finally that it is rare phenomenon. Respect, Daniel -Original Message- From: Boris Kovalenko [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! Hi Boris, 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/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
Hi Boris again, :) I would like to thank you retrospectively to that my proposal is realised, and if this view has ceased to function, so I have to respond. I am afraid that in the last two committed changes in quagga, the error occurred. I have three systems, where I have installed three different versions to the latest display completely ceased to function. SYSTEM1: system1# pkg_info | grep quagga quagga-0.99.9_7 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software system1# /etc2/rc.d/quagga status quagga is running as pid 1116. quagga is running as pid 1122. quagga is running as pid 1128. Sleeping 10 seconds to obtain dynamic routing information... system1# It is old style. SYSTEM2: system2# pkg_info | grep quagga quagga-0.99.10 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software system2# /etc2/rc.d/quagga status zebra is running as pid 1517. ospfd is running as pid 1523. ospf6d is running as pid 1529. bgpd is running as pid 1535. Sleeping 10 seconds to obtain dynamic routing information... system2# It is new style. SYSTEM3: system3# pkg_info | grep quagga quagga-0.99.10_2Free RIPv1, RIPv2, OSPFv2, BGP4, 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: 'Boris Kovalenko' Cc: '[EMAIL PROTECTED]' Subject: RE: FreeBSD Port: quagga-0.99.9_7 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, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! Hi Boris, Question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: quagga-0.99.9_7
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 group quaggavty for command vtysh and they help themself with pam.d/quagga file. [EMAIL PROTECTED] ls -l /etc/pam.d/quagga -rw-r--r-- 1 root root 162 2007-09-26 08:20 /etc/pam.d/quagga user$ cat /etc/pam.d/quagga # Any user may call vtysh but only those belonging to the group quaggavty can # actually connect to the socket and use the program. authsufficient pam_permit.so [EMAIL PROTECTED] whoami user [EMAIL PROTECTED] ls -l /etc/quagga/vtysh.conf -rw-rw 1 quagga quaggavty 63 2008-01-10 01:28 /etc/quagga/vtysh.conf [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] cat /etc/quagga/vtysh.conf username user nopassword username root nopassword log syslog [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] egrep quaggavty /etc/group quaggavty:x:106:user [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] vtysh Hello, this is Quagga (version 0.99.5). Copyright 1996-2005 Kunihiro Ishiguro, et al. server# exit [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] So here it works, now FreeBSD: whoami resu ls -l /etc/pam.d/quagga ls: /etc/pam.d/quagga: No such file or directory ls -l /usr/local/etc/pam.d/quagga ls: /usr/local/etc/pam.d/quagga: No such file or directory ls -l /usr/local/etc/quagga/vtysh.conf -rw-rw-r-- 1 quagga quagga 129 10 led 01:52 /usr/local/etc/quagga/vtysh.conf cat /usr/local/etc/quagga/vtysh.conf username resu nopassword username root nopassword log syslog pw group show quagga quagga:*:101:resu vtysh Exiting: failed to connect to any daemons. Is possible to repair it ? How can I assit you ? It would be good if new version 0.99.10 will count with vtysh like on Debian. Thank you. Bye. Daniel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
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, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! 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/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
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, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! 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/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
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, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! 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/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
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, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! 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/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: quagga-0.99.9_7
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, February 26, 2008 6:50 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: quagga-0.99.9_7 Hello! 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/quagga status [: 34978: unexpected operator strange Very strange, but looks like this is a problem in system's rc, as my rc does not have 34978 lines of code :) quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? You mean You want to see zebra is running as pid ospfd is running as pid etc? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel Respect, Boris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: quagga-0.99.9_7
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/quagga status [: 34978: unexpected operator strange quagga is running as pid 35227. quagga is running as pid 35233. quagga is running as pid 35239. Sleeping 10 seconds to obtain dynamic routing information... And second question about PID´s, would it be possilbe instead drab quagga daemon place the real name of daemons, to see which daemon is not or is running ? For the first question I could send you more information, but my configuration is clean, I am pretty sure. Thanks. Bye. Daniel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
