#1337 closed defect (fixed)
Sequence Starting Samba and Cups
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Bootscripts | Version: | b-6.1-pre1 |
| Severity: | critical | Keywords: | |
| Cc: |
Description
Sharing CUPS-printers via samba printers are not recognized by samba, when samba is started earlier than CUPS. This could be easily fixed by starting cups earlier.
Change History (14)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
If you share Windows printers to Linux, Samba should come up first.
This way works here even if CUPS came up first.
comment:3 by , 19 years ago
| Milestone: | future → 6.1 |
|---|---|
| Priority: | lowest → high |
| Severity: | trivial → normal |
I've confirmed Matthias' comments. Indeed, starting cups before samba still allows printing to Windows printers. There is really no good reason why we can't shuffle the order of the cups daemon startup so that samba is started first.
comment:4 by , 19 years ago
| bug_file_loc: | → http://www.linuxfromscratch.org/blfs/view/stable/server/samba3.html |
|---|
Used samba 3.0.14a instead of 3.0.11
Error: chmod: cannot access `/usr/lib/samba/libsmbclient.a': No such file or directory
Because file does not exist so add this command: cp /sources/samba-3.0.14a/source/bin/libsmbclient.a /usr/lib/samba/libsmbclient.a
Here:
Now, as the root user:
make install && mv /usr/lib/samba/libsmbclient.so /usr/lib && ln -sf ../libsmbclient.so /usr/lib/samba &&
cp /sources/samba-3.0.14a/source/bin/libsmbclient.a /usr/lib/samba/libsmbclient.a &&
comment:6 by , 19 years ago
| Owner: | changed from to |
|---|
comment:7 by , 19 years ago
| Status: | new → assigned |
|---|
comment:8 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Reordered scripts to S25cups, S45samba, S50winbind, and S55stunnel.
comment:9 by , 19 years ago
| Resolution: | fixed |
|---|---|
| Severity: | normal → critical |
| Status: | closed → reopened |
| Version: | a-SVN → b-6.1-pre1 |
Aack!
The "fix" that was put in didn't fix anything!
The existing bootscript symlinks in rc.? are not cleaned up, so they still exist after installing CUPS.
Problem is that the CUPS installation installs one set of bootscripts links and now there is a new set with different numbers. Both of them now exist!
The old ordering overwrote the existing ones, this is no longer the case.
This must be fixed before BLFS-6.1 is released.
comment:10 by , 19 years ago
| Owner: | changed from to |
|---|---|
| Status: | reopened → new |
comment:11 by , 19 years ago
| Status: | new → assigned |
|---|
comment:12 by , 19 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
I believe this is now fixed and the bug can be closed. DJ, please confirm and close it out if so. Thanks.
comment:13 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Yes it can be. Sorry for the awful timing. I had forgotten about it.
I'm not sure anything should be done about this other than perhaps placing some text in the Samba and Cups sections about the possible need to re-order the bootscripts.
What works for some, starting Samba first, doesn't work for others who need CUPS started first.
If you share Linux printers to Windows, CUPS should come up first.
If you share Windows printers to Linux, Samba should come up first.