Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ipp-usb only for systemd? #25

Open
Golddouble opened this issue Mar 7, 2021 · 3 comments
Open

ipp-usb only for systemd? #25

Golddouble opened this issue Mar 7, 2021 · 3 comments

Comments

@Golddouble
Copy link

Hello,

I was successful to use ipp-usb when I boot Linux with systemd, but not when I boot with sysVinit.
Does ipp-usb not support sysVinit?

Thank you.

@alexpevzner
Copy link
Member

Hi!

It should work with sysVinit, but somebody needs to write appropriate scripts.

ipp-usb has two modes of operations:

  1. udev mode
ipp-usb udev

In this mode ipp-usb assumes that it will be started every time when compatible device is plugged into the system, and automatically exits when all compatible devices are unplugged.

  1. standalone mode
ipp-usb standalone

In this mode, ipp-usb runs forever, and automatically handles PnP events by itself, serving all connected compatible devices.

Both of these modes can be used with -bg flag, which tells ipp-usb to deamonize itself.

@Golddouble
Copy link
Author

Golddouble commented Mar 8, 2021

Thank you.

Please note: I am just a user and do not really understand what I am doing.

But I have made the following experiments in a terminal (This is with "ipp-usb_0.9.17-1+48.2_amd64.deb" and "sysVinit":

  1. sudo ipp-usb udev

Result: The printer is recognised. But only if it was already pluged in before I ran this command in the terminal.
When I then plug the printer out and plug it in again, then it is not recognised.

  1. sudo ipp-usb udev -bg

Result: Same behaviour like 1)

  1. sudo ipp-usb standalone

Result: The printer is recognized. No matter if it was already pluged in before I have run this command in the terminal. But the terminal can not be closed. It is somehow in process in a loop. So I had to breake off the process with Ctrl+Alt+Esc.

  1. sudo ipp-usb standalone -bg

Result: The printer is recognized. No matter if it was already pluged in before I have run this command in the terminal. Also it is no problem to close the terminal without the need of Ctrl+Alt+Esc.

So I guess either 3. or 4. is what I need.

Question 1:
Which of these two variants (3 or 4) do need less resources in the background?

Question 2:
What's the right way now to implement variant 3. or 4. ?
Should I make an entry in "auto-start" with the command
-sudo ipp-usb standalone
-sudo ipp-usb standalone -bg

Question 3:
What does the blue "!" on the print symbol mean (in "print settings") ?
Print symbol
It was not there, before I have printed. After the print this "!" has remained.

Thank you.

@Golddouble
Copy link
Author

Golddouble commented Mar 29, 2021

Other question:
When I have run the following command:
sudo ipp-usb standalone -bg

Then driverless printing is active and it works.

Problem: When I then start my VM (VirtualBox) I have no access to this printer. So I can not print in my VM.
Question: How can I then deactivate my printer in the host? I am looking for something like the opposite of the command "sudo ipp-usb standalone -bg".

I have not found anything for this in
man ipp-usb

There I have only found options to activate it, but not how to inactivate it.

Thank you.

Edit: If there is another way to free up the printer for the VM, then I am also open for that solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants