Linux - System logging

now in this video we are going to talk

about new system logs now what are logs

logs are nothing but it creates a report

of whatever the process are happening

into a Linux operating system into our

previous video we have checked for the

performance of different devices but

what if I'm not continuing checking the

particular devices or if there is an

error occurring into the back end how we

are going to come to know those

particular areas so for that logs are

very important to be created into the

Linux operating system but luckily your

system your Linux operating system

creates the logs itself by default so we

do not have to create it by default your

system create the logs which are a

flexible and empowered for logs we

create by using these units or system

tools now into this Linux operating

system it create the logs in their file

called as a syslog so this log is called

as your system log files which are by

default located centralized in a lock in

profiles called as slack VTC slash log D

or you can also get in control system

log itself so this is about the logs now

if I want to check what the locks we

have created and what are the actions we

can perform or file after the slow now

for example the logs already created and

I am NOT going to check the logs what

will happen I won't come to know what is

the error happening in to the backend

now for that we can also set an actions

for the slocks so we can set the

auctions that whatever the files we have

what are they whatever the log files we

have it should be printed so we can give

what log lpr dot log so it will be

printed into this particular file as

well as we can also directly move into

the particular console now if I want to

log to be checked or directly on the

console I can quietly put it on the

console or any of the terminals same way

we can also assign an action so that

whenever log are created after a day

after end of the day the log file should

be sent to a particular user or a root

we can any ins assign any users where

this particular log message should be

sent then we can also pipe a message to

a particular program now if suppose I

want to get this logs into a particular

file which is turned into a particular

folder so it should create a day wise

logs into that directory itself I can

also create into that or I can put it

with the certain program it will just

for the failure logs it will filter the

failure logs and will provide me the

error messages itself then also we can

send this particular messages on the

other host as well so not only in your

actual system or the system which you

have logged on we can also put this logs

into the other system now for an example

I'm a system administrator sitting at my

80 or the server I should get this

particular logs very clear on my console

whenever I have logged in so those

particular message can also be sent on

the other host so let us see how we can

check for this logs how we can get this

logs or how we can redirect it to the

particular user or a particular host

into our terminal so we can check for

the system logs into cache EGC slow

which we generally have

okay so we should be a route that

so we have multiple files here right now

we do not have any system blocks created

into it but yes we can also check for

the logs into the CDs slash four slash

logs so you can see if we have a log

directory here and we can also check the

logs over here so they are different

commands I have used for different

services I do have the logs so what are

the services generally I use mostly

generally the logs are created over here

and c-cup service GTM I know what it

looks good logs so I can also check the

boot locks what they would locks

containing like if it's fine or

it has similar so I can check it over

here so whenever your system gets

started

it creates and manages both locks same

way we have multiple locks which we are

generally used so once you go and create

the services once you go and manage your

services you will be able to see the

slots so it can check there is okay in

the error B I have received while using

my yum so it has created yum dot log a

separate services so it is nothing into

it right now because I think it's

completely flushed out when I restart my

machine so also we have different clocks

like we have used the Samba process we

have used GGG in process but it so all

the logs we can check by opening one or

one of one locks and if you have any

particular service it will create a

separate log for it

or if you do not remember this

particular you know and the path that is

war slash at the log if you do not

remember it you can also use the command

called as ta message so I can use the

mesg so it will again show you the

complete log still no which we have here

so you can check for the process the

complete log by using more it will show

you thee logs for yours complete system

logs

so this is how we generally check for

the logs which by default get created

into your systems so if you want to

create your manual logs as well so you

can also create your manual logs by

using some cropping tools the trapping

tools are like we have the Wireshark

which is the fruit free tool we

generally we have available into the

Linux operating systems so we can use

those those to you don't spoof here or

you can say crap your complete

activities which is going on into the

over the Internet same way you can also

trap the processes over here by using

the dump or a creation entity Wireshark

itself so for wire shock you need to

download those tool and you can work on

it so right now to set the system lock

switch your system creates by your own

so if you want to manually create your

locks you can do it but it will be the

same as generally the locks you

generally find into thee who are locks

so you will find systematic locks

created only by the system itself and

you can also set up messages for this

lock snake if anybody clear logs get

feel or if any particular services field

so you can also send a message over the

slogs to your email addresses so by

default your route gets this locks in

emails even you can't direct it into

their emails as well so this is what

exactly the logs we have seen like how

we can check the logs into the Linux

operating systems into next we are going

to check for the you know the process

management part that is signals and

traps so how we can create the traps if

how we don't really get trapped into the

machine and how we can get do release to

it so that's we are going to discuss so

keep watching the next video