Presented in the traditional illustrated form:

# chkconfig ntpd || echo not runningnot running# chkconfig --add ntpd# chkconfig ntpd || echo not runningnot running

I like Red Hat's chkconfig , but its --add option is so badlymisnamed it winds up irritating me half the time I use it. Oneindication of how bad it is is that the chkconfig manpage needs touse a paragraph to half explain it, and the explanation is exceedinglytechnical.

Part of the problem is that chkconfig is

This week, we:

• got 13,205 messages from 267 different IP addresses.
• handled 19,508 sessions from 1,153 different IP addresses.
• received 163,293 connections from at least 49,706 different IPaddresses.
• hit a highwater of 11 connections being checked at once.

This is about the same volume as last week .The per day table fluctuates a fair bit, with a mid-week peak as usual

I ran into this over this about a year ago, but I got reminded of ittoday:

Regardless of what interface a service is bound to, its outgoingpackets are going out through the interface that the default routesits on.

(Or the route to the specific destination.)

The only packets that are guaranteed to go out the same interface theycame in on are those from sources on that interface's local networks.

This would have bit me hard a year ago if we'd had more load on