"You just cannot rely on specific timeouts, or specific behaviour. In
fact, you can't even rely on your notification being visible at all. The
notification daemon could just as well not display anything, but write
the message to a log file (which obviously never times out)."
If the only guarantee
@Sebastien
The issue here isn't anyone trying to tell the devs how to develop their
software. The notify-osd package intentionally ignores part of the
desktop notification spec, yet still claims to be compliant. It breaks
packages around it (ie: notify-send) and forces developers to
'Ubuntu'ize'
+1 for Vladimir Dobriakov's comment #28 and wirespot's comment #20
I have a script that I run every 5 minutes. I want to get notified when
it exits successfully. I don't need 10 seconds to read 'Success: my-
script.sh".
>From #29: "Marco Chiappero, it is true that expire_timeout is not part
of
I know this is old, but personally I'd prefer to see a startup script in
/etc/init.d/glassfish
The first thing I did was create my own anyway. The domain directory
being split from the rest of the glassfish install was enough of a
change from a standard glassfish install that I had to go hunting
