-HUP 1 command

[fbsd_user]

After making changes to syslog.conf and newsyslog.conf
what is the command to enable the changes.

Is it Kill -HUP 1

[Jonathan Chen]

Post by fbsd_user
After making changes to syslog.conf and newsyslog.conf
what is the command to enable the changes.
Is it Kill -HUP 1

No. You don't need to HUP anything for newsyslog.conf, it's a cron-job.
For changes to syslog.conf you need to HUP the syslogd process, ie:

# kill -HUP <pid-of-syslogd>

[Quintin Riis]

I believe the common command for this is -SIGHUP. This depends on the
software though.
Quintin

Post by fbsd_user
After making changes to syslog.conf and newsyslog.conf
what is the command to enable the changes.
Is it Kill -HUP 1
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-questions

[Chad Leigh -- Shire.Net LLC]

Post by Quintin Riis
I believe the common command for this is -SIGHUP. This depends on the
software though.
Quintin

It is called SIGHUP but to send it you use -HUP to the kill command.

Chad

Post by Quintin Riis

After making changes to syslog.conf and newsyslog.conf what is the
command to enable the changes.
Is it Kill -HUP 1
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to

_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to

[Jez Hancock]

Post by fbsd_user
After making changes to syslog.conf and newsyslog.conf
what is the command to enable the changes.
Is it Kill -HUP 1

Note that process with PID 1 is usually the init process - sending a HUP
signal to it will produce undesirable effects similar to restarting the
whole server. Have a go and see what happens if it's not a production
server :P

[Christian Laursen]

Post by Jez Hancock

Post by fbsd_user
After making changes to syslog.conf and newsyslog.conf
what is the command to enable the changes.
Is it Kill -HUP 1

Note that process with PID 1 is usually the init process - sending a HUP
signal to it will produce undesirable effects similar to restarting the
whole server. Have a go and see what happens if it's not a production
server :P

I usually kill init with a SIGHUP after editing /etc/ttys and it has so
far never caused me any trouble.

Actually this is also explained in the init(8) manpage:

Line status (on, off, secure, getty, or window information) may be
changed in the ttys(5) file without a reboot by sending the signal SIGHUP
to init with the command ``kill -HUP 1''. On receipt of this signal,
init re-reads the ttys(5) file.

[meimi]

Hello everyone,
Today, I found out that my server has unusual high incoming bandwidth
usage (4Mbit/s) in some hours. Usually, my server will not have more than
200Kbit/s.
How can I check what the cause is?
Thanks
Meimi

[Jason Stewart]

Post by meimi
Hello everyone,
Today, I found out that my server has unusual high incoming bandwidth
usage (4Mbit/s) in some hours. Usually, my server will not have more than
200Kbit/s.
How can I check what the cause is?

ntop is one solution to your problem.

Good Luck,
Jason

[Darryl Grant]

You can also use tcpdump to try and figure it out.

If you log tcpdump to the console it will fly by giving your traffic, so perform a little capture and dump it into a file.

HTH,

Darryl

Post by Jason Stewart

Post by meimi
Hello everyone,
Today, I found out that my server has unusual high incoming bandwidth
usage (4Mbit/s) in some hours. Usually, my server will not have more than
200Kbit/s.
How can I check what the cause is?

ntop is one solution to your problem.
Good Luck,
Jason
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-questions