Such a limited account would need write access to any sync folders: I'd say the simplest way to enable such behavior is to make the sync folders group-writable by a group to which the service account belongs. It is definitely possible to configure a service account with limited access (see here and here). If multi-user instances are desired, then it seems to be a matter of correctly restricting the permissions of the service account under which the service is run. If multi-user instances aren't desired, it seems like what we're really talking about is just autostart, which can easily be accomplished by other means.
In this case, running the service under a specific user account is poor practice: what happens to the service if said user gets deleted? As I understand it, the whole point of running syncthing as a service is to allow multiple users on the system to take advantage of the file synchronization services. I'm not sure I agree that the service must run as a user account, though. Rolling our own service wrapper would probably address the reported limitations of NSSM, and also avoid installing an additional dependency, which is generally win under Windows, where it's common for dependencies to get left behind when a program is uninstalled, leading to cruft.
#BITTORRENT SYNC XP INSTALL#
Iss0, I can write the NSIS installer (which will basically copy syncthing to the install location and install it as a service) if you want. » More Info » Download qBittorrent 32-Bit - qBittorrent is a BitTorrent client that aims to be an excellent alternative to other BitTorrent clients. It's a horrible language, but the installer will probably be fairly simple, and I have some experience in writing NSIS installers. uTorrent - uTorrent 2.2.1 is the once top-rated, popular file-sharing program before it was ruined by bundleware and bloat.
I suggest the installer be written in NSIS. Net is included with Windows XP, which means that if you want to support XP, you'll need to use something other than. NET come pre-installed on which versions of Windows: This presents a problem though, because Visual C++ programs needs the Visual C++ Redistributable to be installed first before they are run so we can't have the installer be written in Visual C++.NET programs of course require.
I propose that the Windows installer should be able to run on a brand new Windows machine with nothing new installed on it.
0 kommentar(er)
