From: The Natural Philosopher on
John Hasler wrote:
> geir writes:
>> It seems to be a certain htmlgend. I have found the file,
>
> Where? No Debian package installs anything by that name.

I think that's the point. Its a custom program doing stuff he wants to stop.
From: John Hasler on
geir writes:
> It seems to be a certain htmlgend. I have found the file,

I wrote:
> Where? No Debian package installs anything by that name.

The Natural Philosopher writes:
> I think that's the point. Its a custom program doing stuff he wants to
> stop.

He said he found the file, but hasn't said where (or exactly what he
means by "the file").
--
John Hasler
jhasler(a)newsguy.com
Dancing Horse Hill
Elmwood, WI USA
From: despen on
The Natural Philosopher <tnp(a)invalid.invalid> writes:

> Jeremy Nicoll - news posts wrote:
>> Geir <geir02(a)gmail.com> wrote:
>>
>>> However we are unable to find the annoying script. /etc/crontab
>>> does not contain any user-added stuff.
>>
>> I can't answer that, but would like to ask a question of my own that is
>> maybe related.
>>
>> Is there not (or can there not be) some central syslog on a linux system
>> that shows every system command that's being issued, along with things like
>> its process id and the process id of the issuer if that's different?
>>
>> I'm thinking in terms of - say - an MVS or S/390's system log?
>>
> ps?

No, ps shows whats running.

The MVS system log has an entry for each batch job run, tape mounts,
abends. It started out as the master console, then added support for
multiple consoles of different types, then became a means of automation
and control because programs can read it and reply to it.

Linux /var/log isn't much different in concept but does differ in content.

Overall, I'd say that Linux logging is light years ahead in many ways.

man rsyslogd
From: André Gillibert on
John Hasler wrote:
> geir writes:
> > It seems to be a certain htmlgend. I have found the file,
>
> Where? No Debian package installs anything by that name.

As Allen Kistler pointed, it's part of wview, a third-party program, that has been compiled from the source tarball, most probably.
<http://www.wviewweather.com/>
It looks like some software to get data from a Weather Station hardware device.

It has several daemons:
wviewd
htmlgend
wvpmond
wvalarmd
wvcwopd
wvhttpd
wviewftpd
wviewsshd

A quick look to the source tarball shows that these daemons may be launched from a script examples/Debian/wview.sh
#
# wview Start/Stop the wview daemon processes
#
# processnames: wviewd htmlgend wviewftpd wvalarmd wvcwopd wviewsshd wvhttpd
# config: /etc/wview
# pidfiles: /var/wview/*.pid

Then, it looks like a sys-v style init script supporting the start, stop, and restart parameters.

In order to stop this program, I would search for a /etc/init.d/wview or /etc/init.d/wview.sh file, stop all daemons with it, remove it from runlevels with update-rc.d, and then, remove it from init.d.
If I don't find this script, I would search for the installation source directory.
$ locate wview.sh
or
$ locate sqlite2wlk.c
or
$ locate vproInterface.c

May give a clue.
Once the source directory is found, I would run.
$ examples/Debian/wview.sh stop
and
$ make uninstall

If the source directory is not found, the source code may be downloaded at
<http://downloads.sourceforge.net/wview/>
Ideally, the same version should be downloaded. I don't know where it can be found. Maybe:
$ ls /usr/local/share/doc/wview*
or
$ ls /usr/share/doc/wview*
May show the version number.


And "examples/Debian/wview.sh stop" should be run.
If it doesn't properly terminates all daemons, kill should be run manually on all of them.

Then, the program may be compiled again, with the right ./configure options.. i.e. --prefix=/usr if htmlgend is in /usr/bin or --prefix=/usr/local if htmlgend is in /usr/local/bin.
Then, "make uninstall" may work properly.

A few files may be left if the source tarball is not the same as the original one.

--
André Gillibert