| Summary: | service winbind does not start | ||
|---|---|---|---|
| Product: | [ROSA-based products] ROSA Fresh | Reporter: | Denis Koryavov <denis.koryavov> |
| Component: | Packages from Main | Assignee: | ROSA Linux Bugs <bugs> |
| Status: | RESOLVED FIXED | QA Contact: | ROSA Linux Bugs <bugs> |
| Severity: | normal | ||
| Priority: | Normal | CC: | alex.burmashev, alexander.kazantsev, denis.silakov |
| Version: | Fresh | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Platform: | --- | ROSA Vulnerability identifier: | |
| RPM Package: | ISO-related: | ||
| Bad POT generating: | Upstream: | ||
|
Description
Denis Koryavov
2013-03-25 14:19:08 MSK
See log: "Winbind is not configured in /etc/samba/smb.conf, not starting This is not error - we may disable winbind service, but users need it will be confused... Actually i think winbind can be setup as disabled by default and only enabling samba service will enable winbind, what do you think about it ? winbind is sysvinit service, not systemd (my mistake). Maybe that is what should be fixed, moved to systemd. Maybe we can provide some basic configuration for winbind by default? In Fresh R4, we have migrated to samba 4 and systemd scripts. Winbind starts and works fine with the default configuration. |