bkm435

bumping...anyone at all have X running?

Hi all, First, my continuing thanks to all of you who make Xpenology happen...it's a greater service to more people than you may ever know. I'm running DSM5.2 and the past week or so I've been trying to get X to run on my server. After more hours not succeeding, and more self-help googling than I can remember, I'm finally raising the white flag and asking for help. I've installed ipkg and followed the steps at http://forum.synology.com/enu/viewtopic ... 90&t=76647. Installation seems to go without a hitch. I've added every X utility and font library I can find. I've modified my PATH to include /opt/bin:/opt/sbin. But when I try to launch startx, I get: -ash: startx: not found. Searching my server for the startx script suggests that it doesn't exist, although I have found this guy lurking out there: /volume1/@appstore/debian-chroot/var/chroottarget/usr/share/man/man1/startx.1.gz I know there must be a way to get this working but I'm at the end of my tether. In case it's not apparent, I'm a step past noob but still not versed well enough to sniff this thing out myself. Thanks for any help you can offer!

First, a general thanks again to all of the awesome people here who make and keep this project so fantastic! Last month I upgraded to 5.0-4493 after a very successful year on 4.3. The upgrade was absolutely painless and the system itself has been working perfectly, presuming that I didn't just jinx it by saying that. However, I've been very frustrated with Photo Station and after hours of searching online, I'm amazed that I can't find any clear direction on how to address these issues: Here's my configuration: - Personal Photo Station option selected for all users - Photo Station set to use DSM for user management - While I use the admin account for most global sysadmin needs, I have a separate user account named bkm set up with with full admin privileges. My organized image library is in this account in /homes/bkm/photo. After (re)organizing thousands of photos, I was all psyched to set up family and friends with access to Photo Station and/or to share links to specific photos. Here's where the confusion arises. A) Access permissions: It's apparent to me that I can make certain content public by 1) putting it in the central /photo directory and/or 2) flagging the albums as public. Or 3) I can make it password-protected and make sure people have the PW that I set for each album. I don't want to do #2 or #3 for probably obviously reasons of visibility, management and annoyance. I would prefer not to do #1 for account management and hygiene reasons, though I could get over that. I would think that any user - especially one with admin privs, should be able to mark any album as private and then select the users and groups that can see that album. But in the Photo Station UI, only the actual admin account displays anything in the user and group lists, and even those lists don’t seem to come up consistently from >Settings>Photos>Access Permissions. In DSM, I have only the very coarse options to set permissions to shared folders across groups, or to personal folders for everyone in the groups to which that user (e.g. bkm) belongs. As a further annoyance, if I log directly into Photo Station vs. doing so from DSM or specifying ~admin or ~bkm with the tilde in the URL, there is no content and I can’t even re-log in using the ~ without closing the browser first. 1) If I have perhaps 30-40 albums nested within 4-5 album groupings, how do I give specific users or groups access to specific albums when they log into Photo Station? 2) How do those users do the same for any of their own content that they may want to post? 3) Can any user and/or I log directly into Photo Station without changing the complete URL to have the ~username/photo structure? B) Sharing: I would think that if I use the Share option to send someone a link, that link should go directly to that photo and only that photo. Instead, the few times I’ve done that, the recipient seems to go to the top level of my Photo Station account and sees all publicly visible albums. I’ve pounded my head against the screen for countless days trying to figure these things out and have to believe that the answers are staring me in the face. Hopefully those answers are not “you can’t do that.” I’ve tried uninstalling and re-installing Photo Station just in case. That would have been too easy. Any and all help appreciated!

Running XPE 4.3 all year with no problems, box is working like a charm. Finally got around to consolidating thousands of photos from every machine in the house, spent the last several weekends sorting them beautifully and getting them indexed into Photo Station 6. I had set up the new folder structure under an "organized" folder which was one level below /photo in my user folder. As a final step, I went to move all of my organized folders up to that first level, out from under /photo/organized. I decided to do this using the Move option in Photo Station rather than in File Station, to avoid having to re-index everything. I did this a few folders at a time, then realized that one of the folders that I moved had DISAPPEARED. Of course it was the one with the most photos and the most sub-folders. Of course. There is no sign of this thing in File Station anywhere on the volume. Thankfully I have a backup of all the files, so I'm not standing on the ledge. But the backup is from before a week of sorting and organizing, and the idea of comparing and re-sorting everything is making me crazy. Plus, my sense of justice demands that I at least try to fix this. I've looked into photorec and extundelete, and while I'm comfortable with the basics of moving around in SSH, I haven't quite found a guide that makes it quite clear enough for me since the basics like apt-get don't seem to work in DSM SSH. Has anyone else run into this, and does anyone have a solution? Separately, I couldn't seem to get public albums in one account to be visible in a different account. But one thing at a time. Many thanks!

Re: SSH - I wish I had a more eloquent reply but "duh" followed by a head slap is the only thing appropriate. That worked, thanks! Now to try and conquer this volume issue...

Yes - I rebooted with the USB stick in its original port, and the volume was created by dsm on the drive fresh out of the box. And I opened ports 22 and 23. Any other thoughts?

Argh...just rebuilt machine with a new 2TB WD Red, restored data and config from backup, all was great. Then I went to move the USB key from front to one of the rear ports for the long term. Yes, I stupidly did this while the machine was running but I thought 'hey, it's USB, it will just be re-recognized." Well, now the box isn't seeing the volume I created which had been working just fine. It sees the drive but wants to create a new volume. I've tried restarting, hoping that would do it but to no avail. This seems like there should be an obvious fix, but I can't find a thing. Any ideas? FYI I'm running 4.2-3202. Also for whatever reason I can't seem to ssh into the box, although the ports are allowed in the DSM firewall.

Fantastic, thanks very much - I will try this!

First, a big thanks to all the people who have shared their knowledge on this board. You've made staging and launching DSM both in my home and office a real pleasure. Now, here's one for the storybooks: the machine I have running in my office is humming along nicely. I have all of the DS mobile apps running on my ipad and iphone. But several times a day, DS Finder reports alerts such as improper shutdowns and overheating from machines that are not mine. In fact, about 1/2 of the alerts are in other languages (French and Chinese). The slight kick from seeing other people's NAS reports quickly gave way to concern about possible security flaws in the software. Of course I'm less concerned about people seeing my errors (and fortunately I haven't yet had any) than possibly talking back at them. I'm running DSM 4.2 under Ubuntu 12.04 LTS. DS Finder is tunneling through a VPN so I have no idea how it's in touch with these other networks. I have found no other reports of this online and thus no suggested fixes. Any ideas?