rinetd | You should use Sam Hocevar | TCP library

by boutell C Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | rinetd Summary

rinetd is a C library typically used in Networking, TCP applications. rinetd has no bugs and it has low support. However rinetd has 1 vulnerabilities. You can download it from GitHub.

Redirects TCP connections from one IP address and port to another. rinetd is a single-process server which handles any number of connections to the address/port pairs specified in the file /etc/rinetd.conf. Since rinetd runs as a single process using nonblocking I/O, it is able to redirect a large number of connections without a severe impact on the machine. This makes it practical to run TCP services on machines inside an IP masquerading firewall. rinetd does not redirect FTP, because FTP requires more than one socket.

Support

Quality

Security

License

Reuse

Support

rinetd has a low active ecosystem.

It has 150 star(s) with 33 fork(s). There are 6 watchers for this library.

It had no major release in the last 6 months.

There are 7 open issues and 1 have been closed. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of rinetd is current.

Quality

rinetd has 0 bugs and 0 code smells.

Security

rinetd has 1 vulnerability issues reported (0 critical, 1 high, 0 medium, 0 low).

rinetd code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

rinetd does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

rinetd releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

It has 217 lines of code, 0 functions and 1 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of rinetd

Get all kandi verified functions for this library.

rinetd Key Features

No Key Features are available at this moment for rinetd.

rinetd Examples and Code Snippets

No Code Snippets are available at this moment for rinetd.

Community Discussions

Trending Discussions on rinetd

Why 'reboot' operation does not work with crontab?

QUESTION

Why 'reboot' operation does not work with crontab?

Asked 2021-Dec-20 at 18:17

I am using ubuntu 18.04.

I want to reboot my server every day.

Here is my crontab file for root, which is I can see with 'sudo crontab -e' operation

...

ANSWER

Answered 2021-Dec-20 at 18:17

So I started having this issue as well, recently too.

I've been doing a little digging, and so far what I have found is the following:

Placing 'reboot' in a SU crontab does nothing, but placing '/sbin/reboot' does successfully reboot the system
This is untrue for a User crontab, neither 'reboot' nor '/sbin/reboot' functions.

So this is a temporary fix that can get your system working for now, but I'm going to keep digging.

EDIT: There's something more going on here, it doesn't seem to just be a su related problem. I passed my password plaintext to 'sudo systemctl reboot' and it didn't fire.

Source https://stackoverflow.com/questions/70358428

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install rinetd

You can download it from GitHub.

Support

The server redirected to is not able to identify the host the client really came from. This cannot be corrected; however, the log produced by rinetd provides a way to obtain this information. Under Unix, sockets would theoretically lose data when closed with SO_LINGER turned off, but in Linux this is not the case (kernel source comments support this belief on my part). On non-Linux Unix platforms, alternate code which uses a different trick to work around blocking close() is provided, but this code is untested. The logging is inadequate. The duration of the connection should be logged.

Find more information at: