Search results

syncthing-discosrv-0.12.1-1.lbn19.x86_64

The discovery server supports ql and postgres backends. Specify the backend via -db-backend and the database DSN via -db-dsn. By default it will use in-memory ql backend. If you wish to persist the information on disk between restarts in ql, specify a file DSN: $ discosrv -db-dsn="file://var/run/discosrv.db" For postgres, you will need to create a database and a user with permissions to create tables in it, then start the discosrv as follows: $ export DISCOSRV_DB_DSN="postgres://user:password@localhost/databasename" $ discosrv -db-backend="postgres" You can pass the DSN as command line option, but the value what you pass in will be visible in most process managers, potentially exposing the database password to other users. In all cases, the appropriate tables and indexes will be created at first startup. If it doesn't exit with an error, you're fine. See discosrv -help for other options.

syncthing-gtk-0.8-1.lbn19.noarch

GTK3 & Python based GUI and notification area icon for Syncthing Supported Syncthing features: Everything what WebUI can display Adding / editing / deleting nodes Adding / editing / deleting repositories Restart / shutdown server Editing daemon settings Additional features: First run wizard for initial configuration Running Syncthing daemon in background Half-automatic setup for new nodes and repositories Filesystem watching and instant synchronization using inotify Nautilus (a.k.a. Files), Nemo and Caja integration Desktop notifications

syncthing-inotify-0.6.7-1.lbn19.x86_64

Syncthing (core) uses a rescan interval to detect changes in folders. This application (syncthing-inotify) uses OS primitives to detect changes as soon as they happen. Therefore, if you save a file, syncthing-inotify will know about it and pass this information to Syncthing such that near real-time synchronisation can be achieved.

syncthing-relaysrv-0.12.1-1.lbn19.x86_64

This is the relay server for the syncthing project. By default, all relay servers will join the default public relay pool, which means that the relay server will be availble for public use, and will consume your bandwidth helping others to connect. If you wish to disable this behaviour, please specify -pools="" argument. Please note that relaysrv is only usable by syncthing version v0.12 and onwards. To run relaysrv you need to have port 22067 available to the internet, which means you might need to allow it through your firewall if you have a public IP, or setup a port-forwarding (22067 to 22067) if you are behind a router. Running for public use Make sure you have a public IP with port 22067 open, or make sure you have port-forwarding (22067 to 22067) if you are behind a router. Run the relaysrv with no arguments (or -debug if you want more output), and that should be enough for the server to join the public relay pool. You should see a message saying: 2015/09/21 22:45:46 pool.go:60: Joined https://relays.syncthing.net rejoining in 48m0s See relaysrv -help for other options, such as rate limits, timeout intervals, etc. Running for private use Once you've started the relaysrv, it will generate a key pair and print an URI: relay://:22067/?id=EZQOIDM-6DDD4ZI-DJ65NSM-4OQWRAT-EIKSMJO-OZ552BO-WQZEGYY-STS5RQM&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070 This URI contains partial address of the relay server, as well as it's options which in the future may be taken into account when choosing the best suitable relay out of multiple available. Because -listen option was not used, the relaysrv does not know it's external IP, therefore you should replace the host part of the URI with your public IP address on which the relaysrv will be available: relay://123.123.123.123:22067/?id=EZQOIDM-6DDD4ZI-DJ65NSM-4OQWRAT-EIKSMJO-OZ552BO-WQZEGYY-STS5RQM&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070 If you do not care about certificate pinning (improved security) or do not care about passing verbose settings to the clients, you can shorten the URL to just the host part: relay://123.123.123.123:22067 This URI can then be used in syncthing as one of the relay servers. See relaysrv -help for other options, such as rate limits, timeout intervals, etc.

sysfsutils-2.1.0-14.fc19.x86_64

This package's purpose is to provide a set of utilities for interfacing with sysfs.

syslinux-6.02-5.lbn19.x86_64

SYSLINUX is a suite of bootloaders, currently supporting DOS FAT filesystems, Linux ext2/ext3 filesystems (EXTLINUX), PXE network boots (PXELINUX), or ISO 9660 CD-ROMs (ISOLINUX). It also includes a tool, MEMDISK, which loads legacy operating systems from these media.

syslinux-extlinux-6.02-5.lbn19.x86_64

The EXTLINUX bootloader, for booting the local system, as well as all the SYSLINUX/PXELINUX modules in /boot.

syslinux-extlinux-nonlinux-6.02-5.lbn19.noarch

All the EXTLINUX binaries that run from the firmware rather than from a linux host.

syslinux-nonlinux-6.02-5.lbn19.noarch

All the SYSLINUX binaries that run from the firmware rather than from a linux host. It also includes a tool, MEMDISK, which loads legacy operating systems from media.

syslog-ng-3.4.6-1.fc19.armv6hl

syslog-ng, as the name shows, is a syslogd replacement, but with new functionality for the new generation. The original syslogd allows messages only to be sorted based on priority/facility pairs; syslog-ng adds the possibility to filter based on message contents using regular expressions. The new configuration scheme is intuitive and powerful. Forwarding logs over TCP and remembering all forwarding hops makes it ideal for firewalled environments.