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

cupsaddsmb infinite loop #2926

michaelrsweet opened this Issue Sep 4, 2008 · 1 comment


None yet
1 participant
Copy link

michaelrsweet commented Sep 4, 2008

Version: 1.3.7 User: Hawke

If any step in cupsaddsmb fails (e.g. wrong password for the user name, user without SePrintOperatorPrivilege), it will just keep retrying forever.

This can result in problems like locking yourself out very quickly.

It's especially bad since it produces no output if not in verbose mode, so you can't tell that it's just trying the same thing over and over and will never work.

It would be far better if cupsaddsmb would try only once, and report that an error happened, and what that error was.


This comment has been minimized.

Copy link
Collaborator Author

michaelrsweet commented Sep 4, 2008 User: mike

Unfortunately, there is no way to differentiate between authentication errors and other kinds of errors. File a bug with the Samba folks and we'll update cupsaddsmb at that time to use what they come up with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.