Fbsd8 wrote;
>
> You have never said if you restarted syslog after making your changes to
> syslog.conf, you have to reboot your box or restart syslog for the
> changes to take effect.
Need I point out that the FM says that 'kill -HUP' of syslogd will cause
it to reread it's configuration file
On 29/11/2011 01:28, Kaya Saman wrote:
> As you know rsyslog works over udp and telnet is a tcp protocol so I
> enabled tcp on port 514 within rsyslog and telnet'ed from my router to
> the syslog server.
Use netcat to test UDP connectivity -- it's in the base system as nc(1):
% nc -v -u 192.0.
On 11/29/2011 12:29 PM, Matthew Seaman wrote:
On 29/11/2011 01:28, Kaya Saman wrote:
As you know rsyslog works over udp and telnet is a tcp protocol so I
enabled tcp on port 514 within rsyslog and telnet'ed from my router to
the syslog server.
Use netcat to test UDP connectivity -- it's in the
Hi:
I have a system running FBSD81 preparing migrate to 90 on a different
disk, so the new disk and partitions are mounted in /mnt. To build
FBSD90 on the new disk I mount devfs on /mnt/dev and chroot to /mnt.
Today I finished make build/install world/kernel in /mnt, and now I no
longer have
On 29/11/2011 13:50, Erik Nørgaard wrote:
Today I finished make build/install world/kernel in /mnt, and now I no
longer have network access, interfaces are visible with ifconfig but
no ip is set and can't be set from within the chroot environment.
Is this to be expected? How do I get my networ
On 11/29/11 1:44 PM, Kaya Saman wrote:
> On 11/29/2011 12:29 PM, Matthew Seaman wrote:
>> On 29/11/2011 01:28, Kaya Saman wrote:
>>> As you know rsyslog works over udp and telnet is a tcp protocol so I
>>> enabled tcp on port 514 within rsyslog and telnet'ed from my router to
>>> the syslog server.
On 11/29/11 1:58 PM, Erik Nørgaard wrote:
> On 29/11/2011 13:50, Erik Nørgaard wrote:
>> Today I finished make build/install world/kernel in /mnt, and now I no
>> longer have network access, interfaces are visible with ifconfig but
>> no ip is set and can't be set from within the chroot environme
I think status must check service in any case and I must not to setup
_enable="YES" in rc.conf.
Because of people want to check something:
-- Are that service running or not? (He do not know that service was
runned by /usr/local/etc/rc.d/service start or onestart. He just want
to check)
# /usr/
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
On 11/28/2011 1:19 AM, Gary Gatten wrote:
Unsubscribe
"This email is intended to be reviewed by only the intended recipient
and may contain information that is privileged and/or confidential.
If you are not
On 11/29/11 7:02 PM, FreeLine wrote:
> I think status must check service in any case and I must not to setup
> _enable="YES" in rc.conf.
>
> Because of people want to check something:
> -- Are that service running or not? (He do not know that service was
> runned by /usr/local/etc/rc.d/service s
Hi all,
is it safe to change kern.timecounter.hardware on a busy production system on the fly? Or I better
schedule a downtime to do that?
It seems I got a bad current selection, somehow, probably as an effect of leaving /etc/sysctl.conf
contents of early experimental setup stage of this mach
On Tue, Nov 29, 2011 at 12:34 PM, Ireneusz Pluta wrote:
> is it safe to change kern.timecounter.hardware on a busy production system
> on the fly? Or I better schedule a downtime to do that?
>
> It seems I got a bad current selection, somehow, probably as an effect of
> leaving /etc/sysctl.conf c
>> On Tue, 29 Nov 2011 14:05:30 +1000,
>> Da Rock said:
D> I installed twiki on a test server to get a handle on how it operates,
D> and it all worked fine so I installed it on the production server. The
D> only difference between the 2 is that the production server uses vhosts.
D> When I try t
On Tue, Nov 29, 2011 at 3:45 PM, wrote:
> There were more typos and bad grammar than good information in my previous
> response. What I ment to say:
>
> Go into the BIOS and make sure the CD is first in the boot list. Then
> make sure another system can read and boot the FreeBSD CD. After tha
On 29/11/2011 15:58, Damien Fleuriot wrote:
On 11/29/11 1:58 PM, Erik Nørgaard wrote:
Today I finished make build/install world/kernel in /mnt, and now I no
longer have network access, interfaces are visible with ifconfig but
no ip is set and can't be set from within the chroot environment.
Is
On 29 Nov 2011, at 23:27, Erik Nørgaard wrote:
> On 29/11/2011 15:58, Damien Fleuriot wrote:
>
>> On 11/29/11 1:58 PM, Erik Nørgaard wrote:
Today I finished make build/install world/kernel in /mnt, and now I no
longer have network access, interfaces are visible with ifconfig but
Hello freebsd-questions.
I am having problems with the Huawei E367 3G modem (USB) on FreeBSD (tried
both 8.2 and 9.0-RC2). It's using the u3g driver.
I have made a thread in the FreeBSD forums about this without much luck.
http://forums.freebsd.org/showthread.php?p=156029
As you can see (if you
On 11/30/11 05:24, Karl Vogel wrote:
On Tue, 29 Nov 2011 14:05:30 +1000,
Da Rock said:
D> I installed twiki on a test server to get a handle on how it operates,
D> and it all worked fine so I installed it on the production server. The
D> only difference between the 2 is that the production s
I'm having difficulty gaining serial console access to an 8.2-RELEASE
box running ZFS on its root partition. I would appreciate pointers to
help determine if this is a FreeBSD issue, or something external like
BIOS or cabling.
The server is a vanilla 1U Supermicro motherboard with AMI BIOS. The
BI
19 matches
Mail list logo
