Tag Info

Hot answers tagged


GCC on Solaris has some defaults that are different, for example, than GCC on Linux. For compiling 64 binaries you have to add -m64 to your compile and link lines. This makes GCC compatible to the Solaris Studio C compiler, in that respect. On SPARC, compiling programs as 32 bit does not have as much disadvantages as on e.g. x86, where 64 Bit also ...


Pure bash, one-liner: unset x y sum; while IFS=, read x y; do ((sum[$x]+=y)); done < input.csv; for i in ${!sum[@]}; do echo $i,${sum[$i]}; done Or in more readable form: unset x y sum while IFS=, read x y; do ((sum[$x]+=y)); done < input.csv for i in ${!sum[@]}; do echo $i,${sum[$i]} done The result: 100,400 201,400 300,600


There looks to be a single thread writing a little bit more than 4KB about 111 times per second. This is sufficient to keep your disk 100% busy (111 iops * 9 ms service time = 1 second of service per second = 100%). As there are no other processes writing on that disk (that partition actually), the wait queue is empty, all requests are processed immediately. ...


zpool status does not support a -l option, you must be confusing with something else. # cat /etc/release Oracle Solaris 10 1/13 s10x_u11wos_24a X86 Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved. Assembled 17 January 2013 # zpool help status usage: status [-vx] [-T d|u] [pool] ... ...


http://en.wikipedia.org/wiki/Asynchronous_I/O, a program is firing up requests for I/O, but does not wait on them. However it can still accept and process the I/O responses once they come.


With python this can be done more effectively. This program by default expects the file to be named as 'file.txt', which you can change if needed. #!/usr/bin/env python3 col1, col2 = [ list(y) for y in zip(*[ x.strip().split(',') for x in open('file.txt').readlines() if x != '\n' ]) ] for (offset,x) in enumerate(list(col1)): value = 0 while ...


I think this'll do: awk 'BEGIN{FS=OFS=","}{a[$1]+=$2}END{ for (i in a) print i,a[i]}'


While iostat and kstat are useful, since you've got Solaris with ZFS (so 10 or later), then you can take advantage of the Fault Management Architecture (FMA), which is tied in with zfs and many other parts of the OS. Look at the output from 'fmdump' to see if there have been any faults. As an example (with repeated output elided): $ fmdump -u ...

Only top voted, non community-wiki answers of a minimum length are eligible