Switch to uptime-kuma directory using cd uptime-kuma command. Remote: Enumerating objects: 19267, done. Then clone the package uptime kuma from GitHub using below git clone command. Removed 13 packages, changed 74 packages, and audited 223 packages in 3s You need to first update your npm using sudo npm install npm -g command as shown below. You can use multiple ways to install Uptime Kuma Server monitoring tool on Linux depending on your requirements and tools availability. The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C Uptime Kuma: Self-Hosted Server Monitoring tool on LinuxĪlso Read: How to Install Issabel on CentOS 7 Using 6 Easy Steps Step 1: PrerequisitesĪ) You should have a running Linux Server.ī) You should have a sudo or root access to run privileged commands.Ĭ) You should have npm and docker installed in your Server.īefore proceeding further, it is important to update the system packages to the latest version using sudo apt update & sudo apt upgrade command as shown below. It allows you to monitor services internally in your private network.It provides much more configurable option than any other monitoring tool. We will see the steps to install in below section. It is easy to install in any of the Linux distributions. This also provides a lot more monitoring features than Uptime Robot. Uptime Robot is known to be one of the best monitoring service available today but it's not a self-hosted service so developers thought to replace it with a self-hosting service called Uptime Kuma. Uptime Kuma is a free and open source self-hosted server and website monitoring tool aimed to offer a self-hosting alternative to "Uptime Robot" project. This page is part of release 4.04 of the Linux man-pages project.In this tutorial, we are going to look into a self hosted Server Monitoring Tool on Linux called Uptime Kuma. SEE ALSO chattr(1), futimesat(2), stat(2), utimensat(2), futimens(3), futimes(3) Timestamps to something other than the current time on an append-only file. Linux does not allow changing the timestamps on an immutable file, or setting the (Linux: does not have either the CAP_DAC_OVERRIDE or the CAP_FOWNER capability).ĮPERM times is not NULL, the caller's effective UID does not match the owner of the file,Īnd the caller is not privileged (Linux: does not have the CAP_FOWNER capability).ĮROFS path resides on a read-only filesystem.ĬONFORMING TO utime(): SVr4, POSIX.1-2001. The caller does not have write access to the file, and the caller is not privileged On error, -1 is returned, and errno is set appropriately.ĮRRORS EACCES Search permission is denied for one of the directories in the path prefix of pathĮACCES times is NULL, the caller's effective user ID does not match the owner of the file, If times is NULL, then analogously to utime(), the access and modification times of the Times specifies the new access time, and times specifies the new modification time. Of 1 microsecond for specifying timestamps. The elements of this array are timeval structures, which allow a precision The utimes() system call is similar, but the times argument refers to an array rather thanĪ structure. The utime() system call allows specification of timestamps with a resolution of 1 second. The effective user ID equals the user ID of the file, or times is NULL and the process has If times is NULL, then the access and modification times of the file are set to theĬhanging timestamps is permitted when: either the process has appropriate privileges, or The utime() system call changes the access and modification times of the inode specifiedīy filename to the actime and modtime fields of times respectively. SYNOPSIS #include #include int utime(const char * filename, const struct utimbuf * times ) #include int utimes(const char * filename, const struct timeval times ) DESCRIPTION Note: modern applications may prefer to use the interfaces described in utimensat(2). Utime, utimes - change file last access and modification times
0 Comments
Leave a Reply. |