From: Gary Johnson <lambdatronic@disroot.org>
To: Les <lesdelc@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Cups Web Interface is Disabled
Date: Wed, 04 May 2022 09:28:20 -0400 [thread overview]
Message-ID: <87bkwdqv89.fsf@disroot.org> (raw)
In-Reply-To: <fef8194d-cfad-81bd-2a08-23984379f4ba@gmail.com>
Les <lesdelc@gmail.com> writes:
> Gary, added the following:
>
> ```
> (service cups-service-type
> (cups-configuration
> (web-interface? #t)))
> ```
>
> This did not change the access to cups. The Web Interface still
> remains Disabled.
>
1. Make sure to import `cups-service-type` and `cups-configuration` in your `use-modules` declaration at the top of the file.
2. Make sure that your `operating-system` declaration compiles without errors.
3. Remember to run `sudo guix system reconfigure /path/to/your/config.scm` to add this service.
4. Make sure the CUPS service is running with `sudo herd status cups`.
If not, you may need to start it manually or simply reboot your
computer to bring it up automatically at init time.
Good luck!
--
GPG Key ID: 7BC158ED
Use `gpg --search-keys lambdatronic' to find me
Protect yourself from surveillance: https://emailselfdefense.fsf.org
=======================================================================
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Why is HTML email a security nightmare? See https://useplaintext.email/
Please avoid sending me MS-Office attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
next prev parent reply other threads:[~2022-05-04 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 21:38 Cups Web Interface is Disabled Les Campbell
2022-04-27 0:18 ` Gary Johnson
[not found] ` <fef8194d-cfad-81bd-2a08-23984379f4ba@gmail.com>
2022-05-04 13:28 ` Gary Johnson [this message]
2022-05-06 15:57 ` Les Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkwdqv89.fsf@disroot.org \
--to=lambdatronic@disroot.org \
--cc=help-guix@gnu.org \
--cc=lesdelc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).