4:19 a.m.
Hi,
It seems that after yesterdays (5th July) mammoth rawhide update, that
the cups daemon has vanished from /etc/init.d - any idea if this is just
an oversight?
PFJ
--
Vertraue mir, ich weiss, was ich mache...
10 a.m.
On 07/06/2011 09:21 AM, Reindl Harald wrote:
Am 06.07.2011 11:19, schrieb Paul F. Johnson:
> Hi,
>
> It seems that after yesterdays (5th July) mammoth rawhide update, that
> the cups daemon has vanished from /etc/init.d - any idea if this is just
> an oversight?
sounds like the switch to systemd started
good!
The development cycle is exactly to catch any potential issues like this
and the sooner we have those native service files out there the better.
So I propose that instead of you complaining here on the list you help
out in the migration progress and start converting legacy sysv init
scripts to a native systemd service files.
If you are uncapable of doing that I suggest that you keep these
sarcastic remarks of yours to yourself and off list.
Thanks
JBG
2:33 p.m.
On Wed, 2011-07-06 at 15:00 +0000, "Jóhann B. Guðmundsson" wrote:
On 07/06/2011 09:21 AM, Reindl Harald wrote:
>
> Am 06.07.2011 11:19, schrieb Paul F. Johnson:
>> Hi,
>>
>> It seems that after yesterdays (5th July) mammoth rawhide update, that
>> the cups daemon has vanished from /etc/init.d - any idea if this is just
>> an oversight?
> sounds like the switch to systemd started
> good!
>
The development cycle is exactly to catch any potential issues like this
and the sooner we have those native service files out there the better.
So I propose that instead of you complaining here on the list you help
out in the migration progress and start converting legacy sysv init
scripts to a native systemd service files.
If you are uncapable of doing that I suggest that you keep these
sarcastic remarks of yours to yourself and off list.
erm, I didn't read the initial post as at all sarcastic. I think you're
over-interpreting. Reindl simply suggested why the SysV definition had
disappeared - "sounds like the switch to systemd started" - and gave an
opinion - "good!". I can't see any reason to interpret the opinion as
sarcasm.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
4:22 a.m.
On 06/07/11 10:19, Paul F. Johnson wrote:
It seems that after yesterdays (5th July) mammoth rawhide update,
that
the cups daemon has vanished from /etc/init.d - any idea if this is just
an oversight?
I would guess (given that Lennart used it as his example in his recent
article) that it has been converted to be a native systemd service.
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
4:25 a.m.
Hi,
> It seems that after yesterdays (5th July) mammoth rawhide
update, that
> the cups daemon has vanished from /etc/init.d - any idea if this is just
> an oversight?
I would guess (given that Lennart used it as his example in his recent
article) that it has been converted to be a native systemd service.
Ah.
Looks like I may need to bz it as unless I run /usr/sbin/cupsd -F from a
terminal, the service isn't starting. s-c-services and s-c-printer isn't
showing anything.
Should I put it under cups or systemd?
PFJ
--
Vertraue mir, ich weiss, was ich mache...
4:30 a.m.
On 06/07/11 10:25, Paul F. Johnson wrote:
> I would guess (given that Lennart used it as his example in his
recent
> article) that it has been converted to be a native systemd service.
Ah.
Looks like I may need to bz it as unless I run /usr/sbin/cupsd -F from a
terminal, the service isn't starting. s-c-services and s-c-printer isn't
showing anything.
Well first of all I'd check it's enabled as I believe policy is that the
enabled/disabled state of a service is not carried over when it migrates
from svsvinit to systemd.
So a "systemctl enable cups.service" might be the best thing to try
first - certainly my rawhide VM seems to have had it disabled.
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
6:18 a.m.
On Wed, 2011-07-06 at 10:30 +0100, Tom Hughes wrote:
Well first of all I'd check it's enabled as I believe policy
is that the
enabled/disabled state of a service is not carried over when it migrates
from svsvinit to systemd.
Correct, and I haven't pursued getting an exception for cups so that it
can automatically be enabled.
Did we decide in the end that default service enabling should happen as
part of a spin's kickstart, or does it need to be in the package?
Tim.
*/
6:32 a.m.
On 07/06/2011 11:18 AM, Tim Waugh wrote:
On Wed, 2011-07-06 at 10:30 +0100, Tom Hughes wrote:
> Well first of all I'd check it's enabled as I believe policy is that the
> enabled/disabled state of a service is not carried over when it migrates
> from svsvinit to systemd.
Correct, and I haven't pursued getting an exception for cups so that it
can automatically be enabled.
Did we decide in the end that default service enabling should happen as
part of a spin's kickstart, or does it need to be in the package?
Hum..
I thought with Lennart patch/setup on his blog the only case you need to
enable cups is if you are going to be running centralized printer server
which in that case the admin himself would enabled it hence we would not
have to have it enabled by default...
JBG
7:27 a.m.
On Wed, 2011-07-06 at 11:32 +0000, "Jóhann B. Guðmundsson" wrote:
I thought with Lennart patch/setup on his blog the only case you need
to
enable cups is if you are going to be running centralized printer server
which in that case the admin himself would enabled it hence we would not
have to have it enabled by default...
Yes, you're quite right, my mistake.
Tim.
*/
7:38 a.m.
On 06/07/11 13:27, Tim Waugh wrote:
On Wed, 2011-07-06 at 11:32 +0000, "Jóhann B. Guðmundsson"
wrote:
> I thought with Lennart patch/setup on his blog the only case you need to
> enable cups is if you are going to be running centralized printer server
> which in that case the admin himself would enabled it hence we would not
> have to have it enabled by default...
Yes, you're quite right, my mistake.
Except that the cups package only seems to have the service unit and not
the socket or path units so socket activation won't work at the moment.
I had assumed that was deliberate, but maybe not?
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
4:25 a.m.
On Wed, 06 Jul 2011 10:19:46 +0100 Paul F. Johnson wrote:
It seems that after yesterdays (5th July) mammoth rawhide update,
that
the cups daemon has vanished from /etc/init.d - any idea if this is
just an oversight?
* Wed Jun 29 2011 Tim Waugh <twaugh(a)redhat.com> 1:1.5-0.9.rc1
- Ship systemd service unit instead of SysV initscript (bug #690766).
4:48 a.m.
On Wed, 2011-07-06 at 10:19 +0100, Paul F. Johnson wrote:
Hi,
It seems that after yesterdays (5th July) mammoth rawhide update, that
the cups daemon has vanished from /etc/init.d - any idea if this is just
an oversight?
Looks like it migrated to native systemd configuration:
http://pkgs.fedoraproject.org/gitweb/?p=cups.git;a=commitdiff;h=b7d9a1124...
--
Mathieu
4689
days inactive
4689
days old
13 comments
8 participants
participants (8)
-
Adam Williamson -
Jóhann B. Guðmundsson -
Mathieu Bridon -
Michal Schmidt -
Paul F. Johnson -
Reindl Harald -
Tim Waugh -
Tom Hughes