Date: Tue, 16 May 2006 16:27:30 +0800 From: "Oliver A. Rojo" <oliverrojo@anticogroup.com> To: idzuwan@gmail.com Cc: freebsd-questions@freebsd.org Subject: Re: pptpd with mpd Message-ID: <44698CF2.2010107@anticogroup.com> In-Reply-To: <4469662E.50001@gmail.com> References: <4468470C.800@anticogroup.com> <200605151330.10966.nvass@teledomenet.gr> <44685FCD.9040207@gmail.com> <446944E1.6010009@anticogroup.com> <44694E58.9060507@gmail.com> <44695AF0.1060207@anticogroup.com> <44695C84.40500@gmail.com> <4469626B.5010500@anticogroup.com> <4469662E.50001@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
idzuwan@gmail.com wrote: > I think it would be better to monitor mpd via syslog it can be done by > doing: > > open /etc/syslog.conf and add: > > !mpd > *.* /var/log/mpd.log > > Then, restart syslogd: > > # touch /var/log/mpd.log > # killall -HUP syslogd > > open /etc/newsyslog.conf and add: > > # logfilename [owner:group] mode count size when flags > /var/log/mpd.log 644 4 100 * J > > run "mpd -b" all the mpd error/status should be in /var/log/mpd.log > now, do tail -f /var/log/mpd.log and try connection if there and error > it should be displayed in the log > >>>>> >>>> Ok here's the result: >>>> >>>> # ngctl shut ng0 >>>> ngctl: shutdown: No such file or directory >>>> >>>> >>> "ngctl shut ng0:" please take note the semicolon dont leave it :) >>> _______________________________________________ >>> >> ok i just resolve the error but my windows client still could not >> connect. It says that the Remote Computer did not Respond. >> > hooraaah! it's working now.... thanks a lot genius =)! -- Oliver A. Rojo ______________________________________________________________ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44698CF2.2010107>