04-08-2019
Yeah, at least one more year of warranty, that's cool and ASUS service is good. They send a tech to my condo, which is cool.
I could not develop software if I used the screen on my 13" MacBook Air(s) like I used to; and that is one of the reasons for years I stopped coding. It was too much of an eye strain to code on small screens.
However, I love this 34" curved monitor, and if I had the table space, I would have three of them surrounding me!
For anyone who loves to code or develop software and feels eye strain using a monitor, and you are currently using a monitor less than 21", I would highly recommend you get a monitor like this one. It's a total life changer!
Just do it!
Cheers.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, everyone. I tried to install red hat 8.0 on this computer ( CPU: Intel PIII 866, Memory 128 M, HD: 6.4G MATROX, Vedio card: RIVA TNT 16M), but the process always stuck. And the CD-ROM stopped and the light turned of, the HardDrive's light still on. I waited for almost one hour, but nothing... (5 Replies)
Discussion started by: HOUSCOUS
5 Replies
2. UNIX for Advanced & Expert Users
Hi,
I have a problem on CDE 1.4 Solaris 8.
It looks like each time I lock the screen, the dtexec that invoke
the dtscreen (that is o.k.) do not died after it done his job and it stay in the system and cause many zombie.
Any suggestions?
Thanks,
Itay. (3 Replies)
Discussion started by: itayst
3 Replies
3. UNIX and Linux Applications
Greetings all,
I'm on a solaris 9 system with vnc-4.1.2 installed. I had a connection to a vnc server that suddenly started sapping up cpu cycles - getting up around 13%. I killed the server instance, and now when I try to start a new server, i get the following message:
"vncserver: socket... (0 Replies)
Discussion started by: mike_q
0 Replies
4. HP-UX
Hello.
system fails on reboot this AM.
received message about not possible for kernel to find process that caused crash.
system does memory dump succesfully, then tries to boot again.
looking further at messages during this time, i'm getting 'init died with return value 256'...system panic... (12 Replies)
Discussion started by: mrviking
12 Replies
5. What is on Your Mind?
so my windows xp box has died. trust me, if i didnt game so much id be using solaris or linux but they dont make games for them :( anyway, i've got a really beat up old linux laptop that i'm using now. it runs well it just can't handle most of todays web pages. gmail is awful on this thing!! i wish... (4 Replies)
Discussion started by: pupp
4 Replies
6. HP-UX
Hi,
I am trying to setup subversion on hpux 11.11, the svnserve process can be started and the repos have been created, but every we connect to the svn via port 3699 the svnserver will died.
how can i troubleshoot this issue? there is not error from the syslog file. (0 Replies)
Discussion started by: robertngo
0 Replies
7. HP-UX
Hi,
I have searched the forum and found that there are many scripts that need the path i.e. /tmp, /opt, /var etc to be provided or hard coded for it to calculate the disk space free percentage.
What i need is a script that shows the free disk space for all partitions on my HPUX itanium... (5 Replies)
Discussion started by: mohtashims
5 Replies
LEARN ABOUT DEBIAN
dbus-monitor
dbus-monitor(1) General Commands Manual dbus-monitor(1)
NAME
dbus-monitor - debug probe to print message bus messages
SYNOPSIS
dbus-monitor [--system | --session | --address ADDRESS] [--profile | --monitor] [watch expressions]
DESCRIPTION
The dbus-monitor command is used to monitor messages going through a D-Bus message bus. See http://www.freedesktop.org/software/dbus/ for
more information about the big picture.
There are two well-known message buses: the systemwide message bus (installed on many systems as the "messagebus" service) and the
per-user-login-session message bus (started each time a user logs in). The --system and --session options direct dbus-monitor to monitor
the system or session buses respectively. If neither is specified, dbus-monitor monitors the session bus.
dbus-monitor has two different output modes, the 'classic'-style monitoring mode and profiling mode. The profiling format is a compact for-
mat with a single line per message and microsecond-resolution timing information. The --profile and --monitor options select the profiling
and monitoring output format respectively. If neither is specified, dbus-monitor uses the monitoring output format.
In order to get dbus-monitor to see the messages you are interested in, you should specify a set of watch expressions as you would expect
to be passed to the dbus_bus_add_match function.
The message bus configuration may keep dbus-monitor from seeing all messages, especially if you run the monitor as a non-root user.
OPTIONS
--system
Monitor the system message bus.
--session
Monitor the session message bus. (This is the default.)
--address ADDRESS
Monitor an arbitrary message bus given at ADDRESS.
--profile
Use the profiling output format.
--monitor
Use the monitoring output format. (This is the default.)
EXAMPLE
Here is an example of using dbus-monitor to watch for the gnome typing monitor to say things
dbus-monitor "type='signal',sender='org.gnome.TypingMonitor',interface='org.gnome.TypingMonitor'"
AUTHOR
dbus-monitor was written by Philip Blundell. The profiling output mode was added by Olli Salli.
BUGS
Please send bug reports to the D-Bus mailing list or bug tracker, see http://www.freedesktop.org/software/dbus/
dbus-monitor(1)