Why is the symlink provided? Where is the definition of the
ups-monitor virtual package written down? What is using this symlink?
I assume a good solution should take into account the answers to these
questions. :)
It's there to be called by various parts of "init", though right now I
think o
On Sun, Sep 21, 2008 at 05:31:37AM +1000, Kel Modderman wrote:
> I looked at a couple of the packages you identified and this was also the
> case.
> The nut package should reinstate the symlink then, and new insserv uploaded
> with modification to handle /etc/init.d/symlink -> script case.
Arnau
On Sunday 21 September 2008 01:12:34 Anton Martchukov wrote:
> On Thu, Sep 18, 2008 at 11:19:15PM +1000, Kel Modderman wrote:
> > Is the link just there to be a "virtual/persistent" link to whatever service
> > which is installed and provides the functionality?
> > Inspection of the nut package lea
On Thu, Sep 18, 2008 at 04:23:34PM +0200, Petter Reinholdtsen wrote:
> Why is the symlink provided? Where is the definition of the
> ups-monitor virtual package written down? What is using this symlink?
> I assume a good solution should take into account the answers to these
> questions. :)
I am
On Thu, Sep 18, 2008 at 11:19:15PM +1000, Kel Modderman wrote:
> Is the link just there to be a "virtual/persistent" link to whatever service
> which is installed and provides the functionality?
> Inspection of the nut package leads me to believe this may be the case, so
> I wrote a patch for insse
[Anton Martchukov]
> Can we work out a common solution for the problem? Now apcupsd,
> genpower, nut (in testing), powstatd create ups-monitor symlink in
> init.d since they provide ups-monitor virtual package. However,
> insserv cannot solve dependencies since it discovers several init
> scripts p
Hi all,
On Wednesday 17 September 2008 23:08:27 Anton Martchukov wrote:
> On 9/17/08, Petter Reinholdtsen <[EMAIL PROTECTED]> wrote:
> > > If we need virtual package scripts in init.d than I see now to options:
> > >
> > > 1) Use a script instead of symlink with different lsb headers (this
> >
On 9/17/08, Petter Reinholdtsen <[EMAIL PROTECTED]> wrote:
> > If we need virtual package scripts in init.d than I see now to options:
> >
> > 1) Use a script instead of symlink with different lsb headers (this
> > means rework of all packages using symlink)
> I suspect this involves very few p
"Anton Martchukov" <[EMAIL PROTECTED]> wrote:
> 2) Changhe insserv to not count symlinks at all (do not know about
> possible affects about it)
Rather make insserv ignore symlinks pointing to a file in the same
directory.
JB.
--
Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED
[Anton Martchukov]
> I have checked for other packages, e.g. exim is providing virtual
> package "mail-transport-agent", but I see no "mail-transport-agent"
> symlink in /etc/init.d. Same for my "apache2" providing "httpd"
> virtual package and again no symlink in /etc/init.d.
Yes, you have discov
On 9/17/08, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> There's an "ups-monitor" virtual package defined in Policy, and
> apparently all packages providing it ship /etc/init.d/ups-monitor, and
> searching on the net one can find various bits of documentation
> referring to that file.
> If nobo
[Adeodato Simó]
> Wow. I'm not very knowledgeable on the matter, but after looking a bit
> around, I would say it is not okay to just remove that symlink.
The issue at hand is that several scripts can not provide the same
facility (as in have the same string in the Provides header) without
causing
* Anton Martchukov [Tue, 16 Sep 2008 13:00:42 +0400]:
> Hello Debian Release Team,
> could you enable freeze exception for nut package?
> There is a small change - removed symlink to init.d script
> that fixes bug when nut package prevented insserv from
> enabling dependency based boot:
> http:
13 matches
Mail list logo
