Sponsored Content
Full Discussion: wtmpx file is too big
Operating Systems Solaris wtmpx file is too big Post 302154524 by Vijayakumarpc on Monday 31st of December 2007 02:07:02 AM
Old 12-31-2007
Thanks

Thanks for the help.

Reg,
Vijay
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to view a big file(143M big)

1 . Thanks everyone who read the post first. 2 . I have a log file which size is 143M , I can not use vi open it .I can not use xedit open it too. How to view it ? If I want to view 200-300 ,how can I implement it 3 . Thanks (3 Replies)
Discussion started by: chenhao_no1
3 Replies

2. UNIX for Advanced & Expert Users

how to delete entry in file "wtmpx"(/var/adm/wtmpx)

Do someone know how to delete entry(some lines) in file "wtmpx" that command "last" use it. this file is binary so I cannot edit directy. ========================= #last root pts/1 noc Fri Mar 3 22:04 still logged in root pts/1 noc Fri Mar 3 22:01 - 22:02 ... (4 Replies)
Discussion started by: arm_naja
4 Replies

3. UNIX for Dummies Questions & Answers

wtmpx file

Hello everybody: the wtmpx file on my Sol8 machine, got so big (2GB), that my root partition is almost full now, can I empty that file, I read about it that it contains database of user access and auditing, so in case I emptied it will it affect my system?? Thanks alot (3 Replies)
Discussion started by: aladdin
3 Replies

4. UNIX for Advanced & Expert Users

wtmpx file is not updating

Hi in my solaris 9 system wmptx file is not updating so it is not recording any login or logout or any other entry. can any one tell me how to solve this problem (0 Replies)
Discussion started by: aaysa123
0 Replies

5. Solaris

wtmpx file

What could possibly happen if wtmpx file got deleted by mistake? Thanks, (8 Replies)
Discussion started by: Pouchie1
8 Replies

6. UNIX for Dummies Questions & Answers

How big is too big a config.log file?

I have a 5000 line config.log file with several "maybe" errors. Any reccomendations on finding solvable problems? (2 Replies)
Discussion started by: NeedLotsofHelp
2 Replies

7. Solaris

WTMPX File corrupted

Hi All I work on solaris 8, 9 and 10 platforms and have encountered an error which is my wtmpx files appear to be corrupted as all entries contain the date 1970 (the birth of unix). Now this is obviously not the case, so my query is: 1 - Can the existing wtmpx files be manipulated to... (6 Replies)
Discussion started by: drestarr96
6 Replies

8. Solaris

Something is removing/deleting my wtmpx file?

hi, we have a solaris 10 box that was handled by a different sysadmin before & now it is turned over to us for system administration. our concern is that if we issue the "last" command, it usually says "wtmp begins current day current month date 02:30". just like this "wtmp begins Thu Mar 7... (6 Replies)
Discussion started by: booghaw
6 Replies

9. Solaris

Wtmpx File Permissions Question

Hi all, I have been tasked to change permissions on the wtmpx file to 640. Currently the permissions are at 644. My question is will anything be affected if I change the permissions as shown? Thanks in advance. Derek (2 Replies)
Discussion started by: Derk Berk
2 Replies

10. UNIX for Advanced & Expert Users

Getting information from the wtmpx file

Hi, I tried running the command "last" in the server to check the users that were last logged into the system. However, I get this error : root@csidblog:# last /var/adm/wtmpx: Value too large for defined data type How do I proceed to get this info? I read some forums suggesting to use... (2 Replies)
Discussion started by: anaigini45
2 Replies
VBE(5)                                                VHDL subset of ASIM/LIP6/CAO-VLSI lab.                                                VBE(5)

NAME
vbe VHDL behavioural subset. ORIGIN
This software belongs to the ALLIANCE CAD SYSTEM developed by the ASIM team at LIP6 laboratory of Universite Pierre et Marie CURIE, in Paris, France. Web : http://asim.lip6.fr/recherche/alliance/ E-mail : alliance-users@asim.lip6.fr DESCRIPTION
This document describes the ALLIANCE VHDL subset for behavioural data flow descriptions. CONCURRENT STATEMENTS In a data flow architecture only concurrent statements (except process) are supported. All sequential statements including loops, signal assignment, etc .. are to be banished. Allowed concurrent statements are: simple signal assignment conditional signal assignment selected signal assignment concurrent assert statement block statement BUSES When using concurrent statements, an ordinary signal can be assigned only once. The value of the signal must be explicitly defined by the signal assignment (for example, in a selected signal assignment the value of the target signal is to be defined for every value that the select expression can take). The above constraint may be felt as a hard restriction when designing distributed controled hardware (precharged line, distributed multi- plexer, etc ...). To hurdle this, VHDL uses a special feature: guarded-resolved signals. A resolved signal is a signal declared with a resolved subtype (see vhdl(5)). A resolved subtype is a type combined with a resolution function. A resolved signal can be assigned by multiple signal assignments. Depending on the value of each driver, the resolution function determines the effective value of the signal. A guarded signal is a resolved signal with drivers that can be disconected. A guarded signal must be assigned inside a block statement through a guarded signal assignment. A distributed multiplexer may be described as : signal Distributed_Mux : mux_bit bus; begin first_driver_of_mux : block (Sel1 = '1') begin Distributed_Mux <= guarded Data1; end block; second_driver_of_mux : block (Sel2 = '1') begin Distributed_Mux <= guarded Data2; end block; LATCHES and REGISTERS Sequential elements must be explicitly declared using the type reg_bit or reg_vector (and must be of kind register). A sequential element must be assigned inside a block statement by a guarded signal assignment. Rising edge triggered D flip flop : signal Reg : reg_bit register; begin flip_flop : block (ck = '1' and not ck'STABLE) begin Reg <= guarded Din; end block; Level sensitive latch: signal Reg : reg_bit register; begin latch : block (ck = '1') begin Lat <= guarded Din; end block; In both cases, the guard expression must depend only on one signal if the description is to be processed by the logic synthetizer (boom + boog). The following operators are only supported: not, and, or, xor, nor, nand, &, =, /= They can be applied on all types supported by the subset. Other standard VHDL operators (+, -, >, <, ...) have not been implemented in the present release. TIMING Timing information can be specified in behavioural descriptions using after clauses. However, those delays are currently only used for sim- ulation. After clauses are supported but not used for synthesis and formal proof. After clauses in block statements (for guarded signal assignments) are not supported for sequential elements (signals of kind register), but supported for bus elements (signals of kind bus). This is because the VHDL default disconnection time is null and this can generate unexpected behavior for sequential elements. In selected signal assignment, only uniform delays are supported (the same After clause in all assignments). Transport option is not supported. All delays are inertial delays. ASSERT STATEMENT Only two severity levels are supported in concurrent assert statements: warning print a warning message if the assert condition is not satisfied. error print an error message if the assert condition is not satisfied. Then, stop the simulation. Assert statements are ignored by the logic synthesis tool. DON'T CARE A special feature has been introduced in order to allow "don't care" specification when the logic synthtizer is targeted ( Beware : this feature is incompatible with the IEEE VHDL standard !!). An output can be assigned to the value 'D' (don't care). This is taken into account by the logic synthesis tool in the optimization process. When the value of an output is 'D' the logic synthesis tool may turn it into a '1' or a '0'. A 'D' value is understood as a '0' by the logic simulator (asimut). ARRAIES Arraies other than bit_vector, reg_vector, mux_vector and wor_vector are not supported. EXAMPLES
Here is the description of an adder with an accumulator register. entity add_accu is port ( clk : in bit; command : in bit; data_in : in bit_vector (31 downto 0); data_out : out bit_vector (31 downto 0); cry_out : out bit; vdd : in bit; vss : in bit ); end add_accu; architecture data_flow of add_accu is signal eff_data : bit_vector (31 downto 0); -- effective operande signal adder_out : bit_vector (31 downto 0); -- adder's result signal adder_cry : bit_vector (32 downto 0); -- adder's carry signal accum_reg : reg_vector (31 downto 0) register; -- accumulator constant initialize : bit := '0'; constant accumulate : bit := '1'; begin -- select the effective operand with command select eff_data <= X"0000_0000" when initialize, accum_reg when accumulate; -- compute the result out of the adder adder_out <= eff_data xor data_in xor adder_cry; adder_cry (0) <= '0'; adder_cry (32 downto 1) <= (eff_data and adder_cry (31 downto 0)) or (data_in and adder_cry (31 downto 0)) or (aff_data and data_in ) ; -- write the result into the register on the rising edge of clk write : block (clk = '1' and not clk'STABLE) begin accum_reg <= guarded adder_out; end block; -- assign outputs cry_out <= adder_cry (32); data_out <= accum_reg ; -- check power supply assert (vdd = '1' and vss = '0') report "power sypply is missing" severity ERROR; end; SEE ALSO
vhdl(5), vst(5), boom(1), loon(1), boog(1), asimut(1), proof(1) BUG REPORT
This tool is under development at the ASIM department of the LIP6 laboratory. We need your feedback to improve documentation and tools. ASIM
/LIP6 October 1, 1997 VBE(5)
All times are GMT -4. The time now is 05:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy