Dirk Eddelbuettel writes (supercite undone - iwj):
[Ian Jackson writes:]
Right. In order to avoid having to rename lots of packages or change
their version numbers I propose the following naming scheme for files
on the FTP site in the `binary' directory:
package-name--version[-revision
Bill Mitchell writes (Re: New ftp method for dselect):
dchanges(1) seems to parse distribution filenames OK, though the
parsing code is pretty ugly. If it's broken, please let me know.
Seems to do it OK isn't good enough - we need something unambiguous
and predictable.
Ian.
David Engel writes (Re: New ftp method for dselect):
OK, so package file names don't parse easily. Why couldn't the cross
reference be included in the Packages file? It's needed by dselect
anyway. Also, what about packages like ld.so where the file name
doesn't match the package name
Raul Miller writes (Re: Bug#1995: run-parts on laptops):
I think there's a good answer to this question, but I doubt the above
workaround to the current package implementation of cron will occur to
very many people.
How about taking cron out of rc*.d ?
Ian.
Dale Miller writes (Incoming file permissions):
I noticed that some but not all of the new packages
that get uploaded to the Incoming directory don't have
read permissions. Is there a reason for this? Are they
uploaded that way? I like to install the latest and
greatest as quick as possible.
Bill Mitchell writes (Bug#2048: Broken pipe from dpkg to head):
root:work# dpkg --info less*deb | head -1
old debian package, version 0.939000.
Broken pipe
Richard Kettlewell writes (Bug#2048: Broken pipe from dpkg to head):
[EMAIL PROTECTED]:richard$ ls -l | head -1
total 19792
Broken
brian white writes (Re: Package Verification ):
This is fine, but it doesn't help with verifying packages on
non-Debian systems as is required by people who must do an actual FTP
from another machine. As for the format, feel free to alter it. I
figured I would be parsing this line out of
Dale Scheetz writes (psutils ELF package release):
As I have not yet obtained the upstream source, I have been unable to
create a diff file for this package (I had to fake out dchanges with a
fraud .diff.gz file).
Do not upload the package without a diff. It's incomplete. Please
get the
Let's say I have a package named foo-n with a shared library in it
named libfoo.so.x.y that, at least for the time being, must always be
available by that name, even while dpkg is moving things around. Now,
at some point in the future, I know that libfoo.so.x.y whill no longer
be
Carl Streeter writes (Re: Unanswered problem reports by maintainer):
On Tue, 26 Dec 1995, Raul Miller wrote:
URL: http://www.cps.cmich.edu/~streeter/debian-bugs/
http://www.debian.org/Bugs.
Ian.. Could you update this?
Done. (I've been away - I'll catch up with my email in the
David Engel writes (Re: ncurses-1.9.8a ELF release):
Slowly. I've been trying to better understand how dpkg works and find
a way to do what I want with the current behaviour. The only way I've
come up with is rather ugly and probably error prone so I haven't even
bother to hash it all out.
These listings have been using out-of-date overrides file and Packages
file information, because the cron job to update my local copy wasn't
working.
I think I've fixed that now, and the next summary should be correct.
Please let me know of any further problems.
Thanks,
Ian.
(BTW: I've just
Robert Leslie writes (Re: New ftp method for dselect):
Exceptions: (the ones I saw, anyway)
stable/binary/net/bind-4.9.3-BETA24-1.deb
debian-1.0/binary/net/bind-4.9.3-BETA26-2.deb
If there are no objections I think I will rename the next version of the bind
package to something
Sven Rudolph writes (Re: Buglist):
Some suggestions for the bug reporting system:
- It is possible to mark a message quiet in order to get it not echoed
at debian-devel. Is there a way to make answers to it be not echoed
too ? (e.g. by introducing a debian-bugs-quiet alias)
That
Miquel van Smoorenburg writes (apache):
Well, my views on this are:
o a /var/httpd/htdocs for the documents
Remember apache can be a server for multiple domains. That's why
we need a 2-level directory structure; you might get
/var/httpd/htdocs-customer2
/var/httpd/htdocs-customer3
(Crosspost to -alpha and -sparc removed.)
Bill Mitchell writes (Re: binary-alpha and binary-sparc directories):
It seems that the Guidelines document needs updating to address
issues falling out of this.
One issue is whether binary packages are to be distinguished by
distribution-specific
Erick Branderhorst writes (Bug#2060: dpkg and depends on version again):
[...] The character is misleading and in practice it is
interpretated by dpkg as =. I would suggest to change the syntax
used in Depends/Conflict/Provides/Recommends/Suggest fields into a
more intuitive way (Table 2).
Erick Branderhorst writes (Bug#2059: dpkg and depend on versions):
Package: dpkg
Version: 1.0.8
I installed the man package (2.3.10-6) succesfully. After that I tried
to upgrade the libgdbm1 package (1.7.3-8). During installation of
libgdbm1 dpkg reports about libgdbm1 conflicting with man
Michael K. Johnson writes (Re: binary-alpha and binary-sparc directories ):
Ian Murdock writes:
[...] ther have to have separate Incoming directories for all
supported architectures, or we'll have to have a naming scheme for all
Incoming binary packages (prepending a dash and the architecture
Michael Alan Dorman writes (Bug#2081: named does not start):
In message [EMAIL PROTECTED], Jean-Marc Bourguet w
rites:
PS=`ps -p $PID 2/dev/null| tail -1 | grep named`
You might want to make this
PS=`ps -p $PID 2/dev/null| tail -1 | grep named | grep -v grep`
so that it doesn't pick up
Ian Murdock writes (Too much information! (And what to do about it.)):
With all of the new developers that are joining the Project and the
number of new packages that are resulting from their involvement, it's
becoming increasingly difficult, especially for newer users who aren't
exactly sure
Marek Michalkiewicz writes (Bug#2091: creating packages requires root
privileges):
To create a binary *.deb package, root privileges are required. This
is because you must create a complete directory structure with proper
ownerships and permissions first, and then use dpkg-deb to create
a
Matthew Bailey writes (Re: FTP site performance low):
[...]
Well netscape corp screwed me with politics and listed me in their mirror
listings. Well there used to be more mirrors but it seems that we are one
of three listed now. And until beta 5 or release version are out I can
not get out
(Gigantic crosspost trimmed.)
Raul Miller writes (Re: binary-alpha and binary-sparc directories):
It does look like dvips was superceeded by some other package, and
that it did originally have some executables in it. [All I have on my
system from dvips is a copyright statement and some .tex
David H. Silber writes (Bug#2080: cern-httpd or dpkg leaves log files after
purge.):
Package: cern-httpd -or- dpkg
Version: ??? 1.0.7
After purging cern-httpd from my system, the log files remained.
The logfiles will be created by the package, so dpkg doesn't know
anything about
Raul Miller writes (Re: Bug#1995: run-parts on laptops):
Ian Jackson:
Perhaps savelog should be moved into another package, then ?
This seems like a very good idea.
miscutils is probably the right one.
Ian.
While thinking about this problem over the Christmas break I have come
to the conclusion that we do not have to change the filenames so that
we can recover the package name and version information from them.
Programs can use the Packages file to avoid downloading files that
they know they don't
Manoj Srivastava writes (dist-3.60-3 uploaded to ftp.debian.org):
* Use /etc/news/organization instead of /etc/organization
Please note that people who installed mailagent-3.44-1
and/or dist-3.60-2 shall have to remove /etc/organization
manually after
I've updated mkpackages so that it puts the size in bytes and MD5
checksum of the files in the Packages files.
I didn't put them in the same field because it seemed silly for
programs and humans to have to parse the contents of a field into two
essentially unrelated pieces of information, and
Bill Mitchell writes (Re: binary-alpha and binary-sparc directories):
This seems shakey -- especially if we posit that the i386 maintainer
is in the U.S., the Mac maintainer in Germany, and the PowerPC maintainer
in Korea. Also, the upstream source maintainer might be in Romania,
and might
Andy Guy writes (ftp method v2):
eg, if:
Filename: development/binary/text/a2gs-1.0-4.deb
looks for a2gs-1.0-4.deb in the ls -lR listing (it will probably
find it in text/ !).
If it cannot find a Filename field it falls back on using
pkgname-ver[-rev].deb.
That's an improvement, but
Erick Branderhorst writes (Re: Bug#2059: dpkg and depend on versions):
Yes, I'm sure, the transcription was in chronological order. I didn't
understand
the `5' either.
Chronological order ?
I was thinking that perhaps the was causing it?
Is the conflicting version number calculated from
Raul Miller writes (Re: binary-alpha and binary-sparc directories):
How about the option of a better record of what has happened?
For example, currently, if multiple packages supply the same file only
the most recently installed package has the files listed in it's .list
file. If we have
Erick Branderhorst writes (Re: Bug#2060: dpkg and depends on version again):
How about
= = for less/greater than or equal to
Ok
for strictly less/greater thani
Ok
for less/greater than or equal to (backwards compatibility,
generates warning from dpkg-deb)
Ok but an
Dale Scheetz writes (Re: new syslogd):
...
Well, sysklogd conflicts with syslogd. I assume this means that it
conflicts with it's conffiles too?
No.
The thought was that this could be why
dselect has problems with syslogd and sysklogd.
Could you please elaborate on these problems ?
Ian.
Package: cern-httpd
Version: 3.0-6
The cern-httpd postinst tries to start the daemon, like this:
start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/cern-httpd
If the server is configured to run out of inetd, as I have it, this
(probably) runs cern-httpd and hangs. If you type an HTTP
Martin Schulze writes (Re: Porting and the bug reporting system):
...
But as Michael said, the bugtracking system has a long backlock. Your
bugs won't reach the maintainer until Ian has repaired it.
The bug tracking system is now working fine, and answering mail almost
immediately.
The only
I've been reading the discussion ...
Firstly, I'm glad to have disposed of the `byte-for-byte original
source archive' idea (and that some of the people I thought were
advocating this were merely advocating that we should be able to
extract the original source files somehow from our source
I'm absolutely convinced that we need a `buzz-fixed' directory, to
which Debian-1.1.patchlevel and stable are made to point.
I propose that we organise this as follows:
* Packages that need to go into buzz-fixed have in the dchanges
file `Distribution: unstable buzz-fixed' or perhaps just
Package: netpbm
Version: 1994.03.01p1-1
I tried to find a way to make the netpbm tools supplied in the package
produce a file that was in the ASCII-only format described in pnm(5),
rather than the binary format, but this didn't appear to be possible.
I think it should be, perhaps as a new program
Brian Mays writes (Re: kernel-source and kernel-headers packages):
Ian Jackson [EMAIL PROTECTED] writes:
Can't these be retired ?
...
Why not just ship the (debianised, obviously) source to the
kernels we ship as .tar.gz and .diff.gz, just like any other
binary package ?
Here is one
Package: netpbm
Version: 1994.03.01p1-1
I got a huge number of file conflicts between pbmplus (10dec91-2) and
netpbm, all for the manpages.
Either the manpages should have the suffix .1netpbm instead of .1
(though as the binaries are in /usr/bin this is probably unnecessary)
or netpbm should
Mark Eichin writes (Re: xterm_color with no colors):
Why does the colour xterm package not set TERM correctly by default ?
because I didn't know that xterm-color *existed* as a terminfo
entry. The entry is *not* part of the xterm-color package; I have no
idea where it comes from.
I'll put
Dale Scheetz writes (Re: Bug#3422: termcap entry too long error):
[...]
However, it seems to me that if
dpkg made some kind of running log entry of it's activities, or could
time-stamp it's installations, debugging of these two problems could
provide adequate answers to who did what to whom.
Package: procps
Version: 1.01a-1
-chiark:~ w
2:13pm up 17 days, 12:23, 12 users, load average: 0.31, 0.20, 0.14
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
richard ttyp0mojave.elmail.co 9:24am 26.00s 0.65s 0.65s -bash
pjb1008 ttyp2ash.eng:0.0
Increasingly, documentation is in a generic markup format that can be
processed into various output formats either by standard tools or ones
that come with the package.
For example:
* GNU Texinfo can be converted to Info, DVI (and hence rather large
PostScript) and HTML.
* The Linux FAQ
OK, so we've decided to have packages put their Emacs startup stuff in
a directory, with one file per package.
The directory obviously ought to go in /etc, and the files made
conffiles, so that the sysadmin can reconfigure things.
/etc/emacs/site-start.d ?
Ian.
I'm shortly going to release experimental versions of dpkg and hello.
They'll use the new source package format, which hasn't settled down
yet, so they ought to go in project/experimental.
Unless someone tells me otherwise I'm going to ship them with
`Distribution: experimental' in the .changes
MESSAGE-
Format: 1.5
Date: Tue, 6 Aug 1996 02:31:52 +0100
Source: dpkg
Binary: dpkg
Architecture: source i386
Version: 1.3.0
Distribution: experimental
Urgency: low
Maintainer: Ian Jackson [EMAIL PROTECTED]
Description:
dpkg - Package maintenance system for Debian Linux
Changes:
dpkg
a format that the latest dpkg supports (so that people
don't need to find your home-grown parser to build your package).
Ian.
;; dpkg-changelog.el --- change log maintenance for dpkg-style changelogs
;; Keywords: maint
;; Copyright (C) 1996 Ian Jackson
;; This file is part of dpkg
I have finished draft versions of the programmers' and policy manuals.
The PostScript conversion isn't working yet, but they are available
for your perusal in HTML or plain text (with or without overstrikes).
HTML via the Web:
http://chiark.chu.cam.ac.uk/~ian/programmer.html/
Package: news
Priority: extra
Section: admin
Description: System news tool. (System V)
In addition the fact that this description is inadequate (which will
have been reported automatically a few weeks ago), IMO the package
name is very misleading - it will make people think the package has
Dirk Eddelbuettel writes (Re: /usr/doc/copyright/package -
/usr/doc/package/copyright ?):
[Ian Jackson:]
Should we move the copyright file (and the examples directory) into
the per-package directory in /usr/doc ?
Good idea. Can we also recommend/impose to include the Changelog [1] file
The main new thing here is a manpage for dpkg-source and the related
scripts.
-BEGIN PGP SIGNED MESSAGE-
Format: 1.5
Date: Thu, 8 Aug 1996 02:36:04 +0100
Source: dpkg
Binary: dpkg
Architecture: source i386
Version: 1.3.1
Distribution: experimental
Urgency: low
Maintainer: Ian Jackson
Erick Branderhorst writes (Re: /usr/doc/copyright/package -
/usr/doc/package/copyright ?):
...
No, the /usr/doc/package dir is a dir which normally comes with all
stuff in it gzipped and I think we should keep it like that. We can not
gzip copyright files (this has been decided/mandated long
Guy Maor writes (Re: /usr/doc/copyright/package -
/usr/doc/package/copyright ?):
...
I don't think we should move the copyright file. Most people don't
ever need to look at them, so it's simpler if they're out of the way.
What about the changelog ?
In general I'm not convinced that keeping
I've made a few minor edits and rearrangements.
The PostScript (via Lout) formatting is now working.
Updated versions are at:
http://chiark.chu.cam.ac.uk/~ian/programmer.html/
http://chiark.chu.cam.ac.uk/~ian/policy.html/
ftp://chiark.chu.cam.ac.uk/users/ian/dpkg-doc/
So, what should I
Guy Maor writes in private email - I hope he won't mind me posting:
On Thu, 1 Aug 1996, Ian Jackson wrote:
[EMAIL PROTECTED] writes:
I'd like to see where we sit as far as catching up and was wondering if
anyone has a nice little script that will compare the source directory
Package: lrzsz
Version: 0.12a-5
I've not heard from the author wrt my query below. I'm filing this
bug to make sure that this issue gets checked rather than forgotten.
Thank you for your attention.
Ian.
Mike Neuffer writes (Re: lrzsz ? Re: forwarded message from CERT Bulletin):
...
I'm not
Package: make
Version: 3.74-11
Given the Makefile below in an empty directory:
chiark:d make clean
rm -f t.* u.*
chiark:d make
echo bar t.bar
echo foo t.foo
echo wombat u.wombat
echo spong u.spong
rm t.bar
chiark:d
We see that the intermediate file used for the pattern rules (%.bar)
is
Package: dpkg
Version: 1.3.1
Scott Barker writes (Re: problems with 1.1 release):
...
ok. Although, I beg to differ about the *.conffiles:
ls /var/lib/dpkg/info/*.conffiles
/var/lib/dpkg/info/adduser.conffiles
/var/lib/dpkg/info/at.conffiles
/var/lib/dpkg/info/base.conffiles
[etc]
Oops,
David Engel writes (Re: Bug#3838: GCC should depend on CPP, not conflict with
it):
Ian Jackson writes:
...
Hmm. Why is it necessary for gcc to know which version of cpp is
available, or for it to have exactly the right one ?
Would you want the front-end driver (gcc) to use different
Package: lyx, ftp.debian.org
Version: 0.9.28-1
This package depends on a non-free package (xforms).
It should be in contrib, not in the distribution proper.
Ian.
Package: compress-package, ftp.debian.org
Version: 1.0.1-1
This package is only an installer for a non-free piece of software.
It should be in contrib, not in the distribution proper.
Ian.
I've just added the subsection below to the draft policy manual.
Bruce, tell me if you want me to say something different.
I'd like to come up with some rather more formal way of distributing
our different documentation formats. Perhaps we should create a new
subdirectory of the FTP site for
(version, 1, nameprop);
+}
+if (nameprop.value XtIsRealized(toplevel)) {
+XSetWMName(XtDisplay(toplevel), XtWindow(toplevel), nameprop);
+}
if (app_res.show_date) {
if (doc doc-date) {
label = doc-date;
--
Ian Jackson, at home. [EMAIL PROTECTED
.
* -mmaintainer synopsis changed in dpkg-genchanges usage.
* debian/substvars may now contain blank lines.
-- Ian Jackson [EMAIL PROTECTED] Thu, 8 Aug 1996 02:36:04 +0100
I should think that you've all heard about this by now - if not go and
look at comp.os.linux.announce.
I'm just posting here on what's really an irrelevant topic to say that
I think it's a very good thing that someone is challenging Microsoft.
I mailed Lyle Ball at Caldera to tell him so, and he
Miquel van Smoorenburg writes (Re: Alphas and libc dependencies):
You (Ian Jackson) wrote:
...
2a. Give the package containing our version of glibc version 0 the
name libc5. 2b. Implement version numbers for virtual packages so
that we can use one here.
I think 2b should be done
Mark Eichin writes (Re: fileutils can now replace perforate...):
[Ian Jackson:]
But --sparse=auto is impossible to implement correctly on many
systems, and filesystem-dependent on others !
Depends on what you mean by sparse... the trick is that you can use
stat() to determine if the file
Miquel van Smoorenburg writes (Re: Alphas and libc dependencies):
...
In addition to my last message, here is an alternative I've just though
of. Why don't we just provide dummy (eg empty) libc5, libdb1 etc
packages, and let libc6 depend on them. Then libc5 etc _will_ be
installed..
I think
[EMAIL PROTECTED] writes (Re: Emacs per-package startup files):
Umm, /usr/lib/emacs/site-lisp/ is already there, and already the right
place for this sort of thing. Next question?
Err, I don't think so. Files in /usr/lib/emacs/site-lisp aren't
loaded automatically (and shouldn't be).
As for
Miquel van Smoorenburg writes (Bug#3984: NIS writes error message to STDERR):
...
This is a bug in the library; the library routines print this (they
shouldn't ofcourse). Heeemmm can anybody tell me how to redirect
a bug report to another package, libc5 in particular?
Yes. [EMAIL PROTECTED]'
Dale Scheetz writes (Re: New virtual package names. ):
...
On another note, is there an editor virtual package? Is there any interest
in adding one? It could be valuable to add Provides: editor to ae (and
others as well).
Sorry I'm coming into this so late (just over a week, in fact), but I
Lars Wirzenius writes (Re: Name clash in prospective package ):
...
For instance, there's no guarantee that /usr/local/lib exists, or that
the admin wants it to exist, or that it won't cause any trouble if it
does exist. I can't think of anything that would break, but admins
are allowed to do
Daniel Quinlan writes (Bug#3991: dselect has confusing and bizarre interface):
[ complaints about dselect's user interface ]
I am merging this with Bug#1037.
Offers of assistance are welcome.
Ian.
(Note: this message is crossposted between two mailing lists -
you should probably follow up on only one.)
What used to be the FSSTND group has changed composition somewhat, and
now includes a number of people from the BSD world. It set itself the
goal of producing a joint filesystem layout
Craig Sanders writes (epoch?? how to make squid-1.0.5 squid-1.0beta16):
...
Was epoch implemented? How do I use it?
Yes. See the draft programmers' manual.
Ian.
Yves Arrouye writes (Replaces: and virtual packages?):
I thought having a package with
Provides: compress
Replaces: compress
would be like
Provides: compress
Conflicts: compress
except that the conflict will not appear and I hoped that when the package
was
Yves Arrouye writes (Is it okay to download orig source once only?):
...
I propose that we upload once
somepackage_release.tar.gz
which unpacks to
somepackage-release.orig/
and then further uploads would be
somepackage_release-deb.diff.gz
Bernd Eckenfels writes (gcc and binutils):
ist it possile that on a fresh new install gcc is installed before binutils
is installed, and therefore fail to configure? If I run configure afterwards
everything is fine. Will dpkg install a package first if it sees that other
ones depend on it?
Raul Miller writes (Re: Draft manuals):
Some thought about qmail should occur [in the section on
mail processing].
qmail doesn't use a mail spool directory for security reasons, mail
boxes are in the user's home directory by default. And, of course,
there's the maildir format for people
Erick Branderhorst writes (Re: /usr/doc/copyright/package -
/usr/doc/package/copyright ?):
...
But a /usr/doc/copyright dir should remain. The only contents allowed in
there would be generic copyright messages like GPL LGPL BSD and so on.
Putting these generic files in
David Engel writes (Re: Bug#3838: GCC should depend on CPP, not conflict with
it):
...
Because they're designed to work together. That's why the FSF
includes cpp with gcc instead of packaging it separately.
This doesn't much sense to me, at least not without more detail.
Why do gcc and cpp
+0100
Source: sgmlspm
Binary: sgmlspm
Architecture: source all
Version: 1.03ii-1
Distribution: experimental
Urgency: low
Maintainer: Ian Jackson [EMAIL PROTECTED]
Description:
sgmlspm- Perl modules for processing SGML parser output
Changes:
sgmlspm (1.03ii-1) experimental; urgency=LOW
Mark Eichin writes (Re: Emacs per-package startup files):
...
[it would make it easier to fix the
/etc/passwd problem that mhpower mentioned], but in those cases we
can't really change the database because of existing use, whereas
with emacs we are free to do that.)
Right, that was my line
Miquel van Smoorenburg writes (Re: CC's on this mailing list):
...
I've noticed on some other lists that everything that is posted on the
list has From: set to the original sender, Reply-To: to the list address
and Cc: deleted.
This is actually very nice. Would it be hard (or just a bad
There are a couple of circumstances when a new version of a package
needs to be released by someone other than the usual maintainer:
* Architecture-specific patches which need to be integrated.
* Maintainer is away or can't do it for some other reason.
* Urgent security and other fixes.
I
the binary package(s) and test
extract the source package(s).
* Sign the release: either re-run dpkg-buildpackage (this will rebuild
the package entirely), or PGP-sign the .dsc, rebuild the .changes
using dpkg-genchanges, and then PGP-sign the .changes.
--
Ian Jackson, at home. [EMAIL PROTECTED
Miquel van Smoorenburg writes (Re: New package standards - LAST CALL):
...
I also think that when you make the new source package official, we
should warn all maintainers of the base packages and ask them to convert
their packages to the new standard. If they don't react in say 2 weeks,
Lars Wirzenius writes (Re: Name clash in prospective package ):
Ian Jackson:
The point of not putting things in /usr/local isn't, as I see it, so
Well, I'm not in full agreement, but it's not important enough.
Fair enough.
I propose the following resolution:
I can live with the what you
Yves Arrouye writes (Re: Qmail, smail and sendmail):
...
That's what I do. I even run sendmail -bi if newaliases is not found.
But I wanted to be sure that all mail packages do provide the same
user way of defining aliases, even if they manage them differently after
that.
I'll specify in the
Yves Arrouye writes (CC's on this mailing list):
Ian Jackson writes:
I'm considering adding a paragraph to the policy manual telling people
not to CC each other when replying to messages on debian-devel.
Is it the consensus of the list that this would be a good idea ?
It would
Yves Arrouye writes (Re: Pb: gdb cannot read core from 2.0.8 (is it a gdb or
kernel problem)?):
...
But the message is really misleading... It would ne nice if Gdb checked
wether the prog arg was a core first, and in this case tell that's the
case and remind usage. (Not that I ask that it does
Yves Arrouye writes (Bug#4093: start-stop-daemon fails to kill process):
Maybe should it kill the process whose pid is in the pidfile, even if
it does not think the executable is running?
Here is an example of the problem:
marin66# /etc/init.d/apache stop
no /usr/sbin/apache found; none
: Ian Jackson [EMAIL PROTECTED]
Description:
debiandoc-sgml - Documentation formatting for Debian manuals
Changes:
debiandoc-sgml (1.0) experimental; urgency=LOW
.
* Initial release.
Files:
734bc16c3554423a36972a2a3f2b5413 551 text optional debiandoc-sgml_1.0.dsc
-BEGIN PGP SIGNED MESSAGE-
Format: 1.5
Date: Sat, 10 Aug 1996 23:05:41 +0100
Source: dpkg
Binary: dpkg
Architecture: source i386
Version: 1.3.3
Distribution: experimental
Urgency: low
Maintainer: Ian Jackson [EMAIL PROTECTED]
Description:
dpkg - Package maintenance system
, 10 Aug 1996 23:35:51 +0100
Source: dpkg
Binary: dpkg
Architecture: source i386
Version: 1.3.3
Distribution: experimental
Urgency: low
Maintainer: Ian Jackson [EMAIL PROTECTED]
Description:
dpkg - Package maintenance system for Debian Linux
Changes:
dpkg (1.3.3) experimental; urgency=low
-BEGIN PGP SIGNED MESSAGE-
Format: 1.5
Date: Sat, 10 Aug 1996 22:23:39 +0100
Source: hello
Binary: hello
Architecture: source i386
Version: 1.3-9
Distribution: experimental
Urgency: low
Maintainer: Ian Jackson [EMAIL PROTECTED]
Description:
hello - The classic greeting, and a good
-BEGIN PGP SIGNED MESSAGE-
Format: 1.5
Date: Sun, 11 Aug 1996 13:26:27 +0100
Source: debiandoc-sgml
Binary: debiandoc-sgml
Architecture: source all
Version: 1.0.1
Distribution: experimental
Urgency: low
Maintainer: Ian Jackson [EMAIL PROTECTED]
Description:
debiandoc-sgml
301 - 400 of 2647 matches
Mail list logo
