-
Posts
56 -
Joined
-
Last visited
-
Days Won
1
Posts posted by hansel
-
-
Kinda solved it.
With following command
zeus> ps | grep "btacd" 7259 root 20096 S btacd 7260 root 20096 S btacd 7261 root 20096 S btacd 7287 root 3200 S grep btacd
I found the right process and killed the PID with
kill 7259
and my message log retired.
-
DSM 4.3 build 3810++
I have a lot of errors in my /var/log/messages of type:
Dec 15 22:45:06 zeus btacd: auto_connect.cpp:247 Failed to get manager. Try to restart bluetoothd... Dec 15 22:45:06 zeus btacd: auto_connect.cpp:252 Failed to get manager again. Dec 15 22:45:06 zeus btacd: btacd.cpp:75 Device list is NULL. Dec 15 22:45:06 zeus bluetoothd[2711]: opening L2CAP socket: Address family not supported by protocol Dec 15 22:45:06 zeus bluetoothd[2711]: Server initialization failed Dec 15 22:45:06 zeus bluetoothd[2711]: Unable to start SCO server socket Dec 15 22:45:06 zeus bluetoothd[2711]: Failed to init audio plugin Dec 15 22:45:06 zeus bluetoothd[2711]: Can't open HCI socket: Address family not supported by protocol (97) Dec 15 22:45:06 zeus bluetoothd[2711]: adapter_ops_setup failed
It occurs every 4-5 seconds. I haven't plugged in any bluetooth USB dongle. I do I disable this deamon?
-
Never mind. As often I was thinking too complicated (must be because I'm coming from a ClearOS fileserver).
Here is the fix:
Just make the home location standard on "Volume 1"
After the home folder service has been started
go to Control Panel > Shared Folder
and open the "homes" share.
Change location from "Volume 1" to "Volume X"
-
I have XPEnology installed on a HP N40L Microserver. The system is installed on /volume1 which is a SATA 2.5" drive. All data is on /volume2 (SHR) which are 2 3.5" discs. I have LDAP directory server enabled and I want every user's Home folder on /volume2 pool. There is only /volume1 to choose from in the DSM software. How to change this location via CLI?
I have edited the symbolic link /var/services/homes to point to /volume2 but this doesnt't change enything in DSM.
-
Not sure if N40L bios hack has similar advantages than N54L, but here is some information.
[SOLVED] HP Proliant N40L MicroServer native support
in DSM 5.2 and earlier (Legacy)
Posted
Trantor's build is based on Synology's DS3612xs. It's generic and runs ok on many systems including my N40L. But I have the feeling that it can do with a little less DS3612xs and more N40L.
When I look at the output of "dmesg" there is 4 NICs referenced, a few too many md's and more. Quite a few errors too.
Can we customize it some more and make it more HP N40L??