By the the /Var I am assuming you mean the /var directory tree.
/var/log is where syslogd writes important logfiles. You can remove older files from there if you have a problem.
/var/tmp can also be cleaned up.
This sample cleans up only if the 2GB limit has been reached. Use GB in your limit if you want to use this code.
It removes old syslog files and cleans up /var/tmp (I guessed where /var/tmp might be, some systems do not even have one, and the directory can be /var/admin/tmp or some such).
Be careful with this script you could do damage to the system by wholesale removal of any old big file in /var. Also consider increasing the size of the /var/ filesystem, there usually is one.
This User Gave Thanks to jim mcnamara For This Post:
hi there,
i read man sh(1) and tried to understand the difference between $var and ${var}, but i'm still unsure. when do we use one and when do we use the other? i need an example :rolleyes:
thx (1 Reply)
Hi all,
I'm trying to assign values to multiple variables, is there a way i can just change the number of the variable? ie
read$num=YES
write$num=NO
ex$num=YES
where the $num can be changed ie. in this instance i have 3 read variables, 3 write variables and 3 ex variables and i'd prefer... (1 Reply)
hi sirs
can u tell the difference between /var/log/syslogs and /var/adm/messages
in my working place i am having two servers.
in one servers messages file is empty and syslog file is going on increasing..
and in another servers message file is going on increasing but syslog file is... (2 Replies)
The /var/adm/messages in Solaris seem to log more system messages/errors compared to /var/log/messages in Linux.
I checked the log level in Linux and they seem OK.
Is there any other log file that contains the messages or is it just that Linux doesn't log great many things? (2 Replies)
Hello, I recently found that my /var/sadm/install/contents, ~/admin/default, /var/spool/patch and /var/spool/pkg files were empty.
This broke the pkginfo, pkgchk and other package related tools.
The pkgmap no longer points to where the applications have been installed.
I have replaced the... (0 Replies)
Hi
I want to know what is the difference between $var and ${var}. :D
I saw in few of the scripts examples.Somewhere people use $var and somewhere ${var}.
Is there any difference between two ? :confused:
Thanks (4 Replies)
i try to find way to make string concatenation in csh ( sorry this is what i have )
so i found out i can't do :
set string_buff = ""
foreach line("`cat $source_dir/$f`")
$string_buff = string_buff $line
end
how can i do string concatenation? (1 Reply)
I have been searching and reading about syslog. I would like to know how to Transfer the logs being thrown into /var/log/messages into another file example /var/log/volumelog.
tail -f /var/log/messages
dblogger: msg_to_dbrow: no logtype using missing
dblogger: msg_to_dbrow_str: val ==... (2 Replies)
Discussion started by: kenshinhimura
2 Replies
LEARN ABOUT LINUX
inviso_as_lib
inviso_as_lib(3erl) Erlang Module Definition inviso_as_lib(3erl)NAME
inviso_as_lib - The Inviso Autostart Utility Library
DESCRIPTION
The purpose of the Inviso autostart utility library is to facilitate the creation and modification of autostart configuration files used by
the standard autostart.
EXPORTS
setup_autostart(Node, R, Opts, TracerData, CmdFiles, Bindings, Transl, RTtag) -> ok | {error, Reason}
Types Node = atom()
R = int()
Opts -- see inviso:add_nodes/2,3
TracerData -- see inviso:init_tracing/1,2
CmdFiles = [CmdFile]
CmdFile = string()
Bindings = [{Var,Val}]
Var = atom()
Val = term()
Transl = [{{M1,F1,Arity}, {M2,F2,{Mt,Ft}}}]
M1 = F1 = M2 = F2 = Mt = Ft = atom()
Arity = int()
RTtag = term()
Reason = term()
Creates an autostart configuration file on Node . The name of the file is automatically deducted from consulting the Runtime_Tools
configuration parameters at Node .
R is the number of allowed autostarts remaining.
Opts is the options which shall be given to the runtime component. See inviso:add_nodes/2,3 .
TracerData is used when initiating tracing on this node. See inviso:init_tracing/1,2 .
CmdFiles points out files containing instructions understood by the inviso_autostart_server implementation of an autostart initia-
tor.
Bindings is a list of {Var, Val} tuples, where Var is the name of a variable and Val the actual value of the variable.
Transl means that M1:F1/Arity shall be translated into M2:F2 .
RTtag is the incarnation tag of the runtime component. See See inviso:add_nodes/2,3 .
set_repeat(Node, R) -> ok | {error, Reason}
Types Node = atom()
R = int()
Reason = term()
Sets the repeat parameter in the autostart file at Node without changing any of its other contents. The autostart configuration file
must exist.
R is the number of allowed autostarts remaining.
inhibit_autostart(Node) -> ok | {error, Reason}
Types Node = atom()
Reason = term()
Sets the repeat parameter in the autostart file at Node to 0. Equivalent to set_repeat(Node, 0) .
Ericsson AB inviso 0.6.2 inviso_as_lib(3erl)