stan(st...@panix.com) on 2016.05.03 07:17:38 -0400:
> Building 5.9 machines to replace 5.5 ones. Looking in /usr/src on the 5.9
> machines, I do not see the code for rwhod. Has this been removed, and if
> so, why? We use this on all of our mahcines.
Because we remove code that nobody
Building 5.9 machines to replace 5.5 ones. Looking in /usr/src on the 5.9
machines, I do not see the code for rwhod. Has this been removed, and if
so, why? We use this on all of our mahcines.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a
Hi Stan,
On Mon, May 02, 2016 at 02:34:19PM -0400, stan wrote:
> Preparing to upgrade some 5.5 machines to 5.9
>
> I seem to be missing /usr/sbin/rwhod on a freshly installed 5.9 machine.
> Is there soemthing special I have to do to get this isnalled?
rwhod and friends (rsh,
stan writes:
> Preparing to upgrade some 5.5 machines to 5.9
>
> I seem to be missing /usr/sbin/rwhod on a freshly installed 5.9 machine.
> Is there soemthing special I have to do to get this isnalled?
Ahem... create a port for it, maybe? rwhod has been removed since
2014/04/24.
-
Preparing to upgrade some 5.5 machines to 5.9
I seem to be missing /usr/sbin/rwhod on a freshly installed 5.9 machine.
Is there soemthing special I have to do to get this isnalled?
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing
I'm having a perplexing problem with rwhod and ruptime.
On two hosts (4.6-patched), rwhod is not apparently contacting
localhost properly; ruptime omits mention of the localhost.
On a third host (4.6-patched), function is normal.
A fourth host, (4.2-patched) is also working).
On the tw
gt; are instead building replacement machines, and moving over the config
> > files. So it's not an _upgrade_ as such issue, but a diffrenece in observed
> > behavior between 4.2, and 4.5.
>
> The 4.5 rwhod doesn't even send anything on the network, that makes
> it ve
uch issue, but a diffrenece in observed
> behavior between 4.2, and 4.5.
The 4.5 rwhod doesn't even send anything on the network, that makes
it very hard for other daemon to gather your info. Claudio seem to
have made a fix for 4.6. I don't run a rwhod on a regular basis but
the o
On Thu, Aug 13, 2009 at 05:54:37PM +0530, Siju George wrote:
> On Wed, Aug 12, 2009 at 11:33 PM, stan wrote:
> > We are in the process of upgrading a number of machines from 4.2 to 4.5.
> >
>
> upgrades are supported fromrelease to release so
> 4.2 > 4.3 > 4.4 > 4.5
OK, so I am sloppy with my wor
On Wed, Aug 12, 2009 at 11:33 PM, stan wrote:
> We are in the process of upgrading a number of machines from 4.2 to 4.5.
>
upgrades are supported fromrelease to release so
4.2 > 4.3 > 4.4 > 4.5
--Sij
We are in the process of upgrading a number of machines from 4.2 to 4.5.
The development machine we have running 4.5 seems to be exhibiting a
different behavior vis a vi rwhod. rwhod runs, and when I run it in debug
mode, I see it recognizing other machines on the same subnet. But it fails
to
Dear list members,
i am trying as root to get the output of rwhod daemon, but nothing is
show when stdout is redirected.
# rwhod -d
sendto 10.0.0.191.513
hostname etosha up 0:07
load 0.37, 0.36, 0.19
host etosha
But,
# rwhod -d | cat
As you can see nothing is show. Any ideia about
i am trying to get standard messages for rwhod redirected bu i am not
able to do it, does anybody know where the error is?
# rwhod -d
sendto 10.0.0.255.513
hostname etosha up 0:09
load 0.26, 0.28, 0.15
griosetosha:ttyp0 Jul 16 17:09
griosetosha:ttyp1 Jul 16 17:09 :05
grios
13 matches
Mail list logo
