Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #239741 > unrolled thread

Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation

Back to article view | Back to comp.os.linux.advocacy

Contents

  Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation DFS <nospam@dfs.com> - 2014-04-22 14:42 -0400
    Re: Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation Melzzzzz <mel@zzzzz.invalid> - 2014-04-22 20:51 +0200
      Re: Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation DFS <nospam@dfs.com> - 2014-04-22 16:19 -0400
        Re: Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation TomB <tommy.bongaerts@gmail.com> - 2014-04-23 05:31 +0000
          Long Term Shithead: Bug #10 - whining about documentation Chris Ahlstrom <OFeem1987@teleworm.us> - 2014-04-23 05:59 -0400
            Re: Long Term Shithead: Bug #10 - whining about documentation chrisv <chrisv@nospam.invalid> - 2014-04-23 06:50 -0500
              Re: Long Term Shithead: Bug #10 - whining about documentation 	flatfish+++ <phlatphish@yahoo.com> - 2014-04-23 08:42 -0400
              Re: Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation DFS <nospam@dfs.com> - 2014-04-23 10:21 -0400
              Re: Long Term Shithead: Bug #10 - whining about documentation GreyCloud <mist@cumulus.com> - 2014-04-23 08:54 -0600
              Re: Long Term Shithead: Bug #10 - whining about documentation Hadron<hadronquark@gmail.com> - 2014-04-24 13:07 +0200
            Re: Long Term Shithead: Bug #10 - whining about documentation 	flatfish+++ <phlatphish@yahoo.com> - 2014-04-23 08:38 -0400
            Re: Long Term Shithead: Bug #10 - whining about documentation GreyCloud <mist@cumulus.com> - 2014-04-23 08:53 -0600
            Re: Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation DFS <nospam@dfs.com> - 2014-04-23 18:05 -0400
              Re: Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation 	flatfish+++ <phlatphish@yahoo.com> - 2014-04-23 18:12 -0400
                Re: Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation DFS <nospam@dfs.com> - 2014-04-23 21:37 -0400
              Re: Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation Hadron<hadronquark@gmail.com> - 2014-04-24 13:17 +0200
            Re: Long Term Shithead: Bug #10 - whining about documentation Hadron<hadronquark@gmail.com> - 2014-04-24 13:06 +0200
          Re: Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation DFS <nospam@dfs.com> - 2014-04-23 10:19 -0400
            Re: Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation TomB <tommy.bongaerts@gmail.com> - 2014-04-23 23:26 +0000
    Re: Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation Snit <usenet@gallopinginsanity.com> - 2014-04-22 12:35 -0700

#239741 — Ubuntu 14.04 Long Term Shitware: Bug #10 - log viewer app missing menus shown in documentation

http://bayimg.com/EAniDAAFL


The Help documentation refers to File and Filter and View menu items, 
but the log viewer app only has one menu item: System Log, and it 
doesn't contain File, Filter or View.

Same if you open the log viewer (gnome-system-log) as root.



"Whatever their problems is not the fault of Ubuntu"

[toc] | [next] | [standalone]

#239742

On Tue, 22 Apr 2014 14:42:44 -0400
DFS <nospam@dfs.com> wrote:

> http://bayimg.com/EAniDAAFL
> 
> 
> The Help documentation refers to File and Filter and View menu items, 
> but the log viewer app only has one menu item: System Log, and it 
> doesn't contain File, Filter or View.
> 
> Same if you open the log viewer (gnome-system-log) as root.
> 
> 
> 
> "Whatever their problems is not the fault of Ubuntu"
> 
> 

There are search and filter functions , but not in the menu ;)
There is lens and wheel ... try them out...

-- 
Click OK to continue...

[toc] | [prev] | [next] | [standalone]

#239756

On 04/22/2014 02:51 PM, Melzzzzz wrote:
> On Tue, 22 Apr 2014 14:42:44 -0400
> DFS <nospam@dfs.com> wrote:
>
>> http://bayimg.com/EAniDAAFL
>>
>>
>> The Help documentation refers to File and Filter and View menu items,
>> but the log viewer app only has one menu item: System Log, and it
>> doesn't contain File, Filter or View.
>>
>> Same if you open the log viewer (gnome-system-log) as root.
>>
>>
>>
>> "Whatever their problems is not the fault of Ubuntu"
>>
>>
>
> There are search and filter functions , but not in the menu ;)

I found them, but they're not in the menus like the Help says.  They're 
accessed via a little cog button on the top right.

Once you open a log, it stays in the list at left.  Thankfully.




> There is lens and wheel ... try them out...

or command line


* all messages logged on a date
cat logfile | grep ^YYYY-MM-DD


* first and last 25 messages on a date
cat logfile | grep ^YYYY-MM-DD | head -n 25
cat logfile | grep ^YYYY-MM-DD | tail -n 25


* all messages related to gparted
cat logfile | grep gparted

[toc] | [prev] | [next] | [standalone]

#239801

On 2014-04-22, the following emerged from the brain of DFS:

8<

> * all messages logged on a date
> cat logfile | grep ^YYYY-MM-DD
>
>
> * first and last 25 messages on a date
> cat logfile | grep ^YYYY-MM-DD | head -n 25
> cat logfile | grep ^YYYY-MM-DD | tail -n 25
>
>
> * all messages related to gparted
> cat logfile | grep gparted

Yes, /that's/ how it's done ;-)

-- 
Q:	Why should you always serve a Southern Carolina football man
	soup in a plate?
A:	'Cause if you give him a bowl, he'll throw it away.

[toc] | [prev] | [next] | [standalone]

#239804 — Long Term Shithead: Bug #10 - whining about documentation

TomB wrote this copyrighted missive and expects royalties:

> On 2014-04-22, the following emerged from the brain of DFS:
>
> 8<
>
>> * all messages logged on a date
>> cat logfile | grep ^YYYY-MM-DD
>>
>> * first and last 25 messages on a date
>> cat logfile | grep ^YYYY-MM-DD | head -n 25
>> cat logfile | grep ^YYYY-MM-DD | tail -n 25
>>
>> * all messages related to gparted
>> cat logfile | grep gparted
>
> Yes, /that's/ how it's done ;-)

Log viewer app?  How quaint.  Sounds like something Windows would use.

And then, instead of using stock system tools (e.g. as noted above), you end
up with something like this:

   http://msdn.microsoft.com/en-us/library/windows/desktop/aa385785(v=vs.85).aspx

   The following are the programming elements that you use to create an
   instrumentation manifest, create resources from the manifest that your
   provider uses, get instrumentation metadata at run time, and query events
   from channels and log files:

   -  EventManifest Schema
   -  Event Schema
   -  Query Schema
   -  Windows Event Log Constants
   -  Windows Event Log Data Types
   -  Windows Event Log Enumerations
   -  Windows Event Log Functions
   -  Windows Event Log Structures
   -  Windows Event Log Tools

And here's just the function page:

   http://msdn.microsoft.com/en-us/library/windows/desktop/aa385784(v=vs.85).aspx

Windows... the Rube Goldberg OS.

-- 
If ignorance is bliss, why aren't there more happy people?

[toc] | [prev] | [next] | [standalone]

#239805 — Re: Long Term Shithead: Bug #10 - whining about documentation

Chris Ahlstrom wrote:

>Log viewer app?  How quaint.  Sounds like something Windows would use.
>
>And then, instead of using stock system tools (e.g. as noted above), you end
>up with something like this:
>
>   http://msdn.microsoft.com/en-us/library/windows/desktop/aa385785(v=vs.85).aspx
>
>   The following are the programming elements that you use to create an
>   instrumentation manifest, create resources from the manifest that your
>   provider uses, get instrumentation metadata at run time, and query events
>   from channels and log files:
>
>   -  EventManifest Schema
>   -  Event Schema
>   -  Query Schema
>   -  Windows Event Log Constants
>   -  Windows Event Log Data Types
>   -  Windows Event Log Enumerations
>   -  Windows Event Log Functions
>   -  Windows Event Log Structures
>   -  Windows Event Log Tools
>
>And here's just the function page:
>
>   http://msdn.microsoft.com/en-us/library/windows/desktop/aa385784(v=vs.85).aspx
>
>Windows... the Rube Goldberg OS.

Hey, man, they just want to get it to where users need only point and
drool.  

Think of the cost savings to companies, now able to hire pubeless
n00bs like "Hadron" (has he figured-out paths, yet?) for their IT
department.

-- 
'EVERYONE knows that having "." on your path is a HUGE security risk
since you might inadvertently pick up a rogue script called "ls" for
example in the dir you are browsing.'  -  "Linux expert" Hadron Quark

[toc] | [prev] | [next] | [standalone]

#239809 — Re: Long Term Shithead: Bug #10 - whining about documentation

On Wed, 23 Apr 2014 06:50:16 -0500, chrisv wrote:

> Chris Ahlstrom wrote:
> 
>>Log viewer app?  How quaint.  Sounds like something Windows would use.
>>
>>And then, instead of using stock system tools (e.g. as noted above), you end
>>up with something like this:
>>
>>   http://msdn.microsoft.com/en-us/library/windows/desktop/aa385785(v=vs.85).aspx
>>
>>   The following are the programming elements that you use to create an
>>   instrumentation manifest, create resources from the manifest that your
>>   provider uses, get instrumentation metadata at run time, and query events
>>   from channels and log files:
>>
>>   -  EventManifest Schema
>>   -  Event Schema
>>   -  Query Schema
>>   -  Windows Event Log Constants
>>   -  Windows Event Log Data Types
>>   -  Windows Event Log Enumerations
>>   -  Windows Event Log Functions
>>   -  Windows Event Log Structures
>>   -  Windows Event Log Tools
>>
>>And here's just the function page:
>>
>>   http://msdn.microsoft.com/en-us/library/windows/desktop/aa385784(v=vs.85).aspx
>>
>>Windows... the Rube Goldberg OS.
> 
> Hey, man, they just want to get it to where users need only point and
> drool.  

The idea is to get the data as easily as possible.
 
> Think of the cost savings to companies, now able to hire pubeless
> n00bs like "Hadron" (has he figured-out paths, yet?) for their IT
> department.

Are you one of them?
A point and drooler?

Is that why you use Windows chrisv?

Great self nuke.

[toc] | [prev] | [next] | [standalone]

#239812

On 04/23/2014 07:50 AM, chrisv wrote:
> Chris Ahlstrom wrote:
>
>> Log viewer app?  How quaint.  Sounds like something Windows would use.
>>
>> And then, instead of using stock system tools (e.g. as noted above), you end
>> up with something like this:
>>
>>    http://msdn.microsoft.com/en-us/library/windows/desktop/aa385785(v=vs.85).aspx
>>
>>    The following are the programming elements that you use to create an
>>    instrumentation manifest, create resources from the manifest that your
>>    provider uses, get instrumentation metadata at run time, and query events
>>    from channels and log files:
>>
>>    -  EventManifest Schema
>>    -  Event Schema
>>    -  Query Schema
>>    -  Windows Event Log Constants
>>    -  Windows Event Log Data Types
>>    -  Windows Event Log Enumerations
>>    -  Windows Event Log Functions
>>    -  Windows Event Log Structures
>>    -  Windows Event Log Tools
>>
>> And here's just the function page:
>>
>>    http://msdn.microsoft.com/en-us/library/windows/desktop/aa385784(v=vs.85).aspx
>>
>> Windows... the Rube Goldberg OS.
>
> Hey, man, they just want to get it to where users need only point and
> drool.


Do you and your company intentionally make your products harder to use?

Didn't think so, turd.




> Think of the cost savings to companies, now able to hire pubeless
> n00bs like "Hadron" (has he figured-out paths, yet?) for their IT
> department.

Hadron puts you to shame in ALL areas of Linux and IT.  Most everyone 
here does.

I'd be very surprised if a moron like you could sort a block of data in 
Excel.

[toc] | [prev] | [next] | [standalone]

#239820 — Re: Long Term Shithead: Bug #10 - whining about documentation

On 4/23/2014 5:50 AM, chrisv wrote:
> Chris Ahlstrom wrote:
> 
>> Log viewer app?  How quaint.  Sounds like something Windows would use.
>>
>> And then, instead of using stock system tools (e.g. as noted above), you end
>> up with something like this:
>>
>>   http://msdn.microsoft.com/en-us/library/windows/desktop/aa385785(v=vs.85).aspx
>>
>>   The following are the programming elements that you use to create an
>>   instrumentation manifest, create resources from the manifest that your
>>   provider uses, get instrumentation metadata at run time, and query events
>>   from channels and log files:
>>
>>   -  EventManifest Schema
>>   -  Event Schema
>>   -  Query Schema
>>   -  Windows Event Log Constants
>>   -  Windows Event Log Data Types
>>   -  Windows Event Log Enumerations
>>   -  Windows Event Log Functions
>>   -  Windows Event Log Structures
>>   -  Windows Event Log Tools
>>
>> And here's just the function page:
>>
>>   http://msdn.microsoft.com/en-us/library/windows/desktop/aa385784(v=vs.85).aspx
>>
>> Windows... the Rube Goldberg OS.
> 
> Hey, man, they just want to get it to where users need only point and
> drool.  
> 

Just as I thought... you're a retard.

> Think of the cost savings to companies, now able to hire pubeless
> n00bs like "Hadron" (has he figured-out paths, yet?) for their IT
> department.
> 

[toc] | [prev] | [next] | [standalone]

#239965 — Re: Long Term Shithead: Bug #10 - whining about documentation

chrisv <chrisv@nospam.invalid> writes:

> Chris Ahlstrom wrote:
>
>>Log viewer app?  How quaint.  Sounds like something Windows would use.
>>
>>And then, instead of using stock system tools (e.g. as noted above), you end
>>up with something like this:
>>
>>   http://msdn.microsoft.com/en-us/library/windows/desktop/aa385785(v=vs.85).aspx
>>
>>   The following are the programming elements that you use to create an
>>   instrumentation manifest, create resources from the manifest that your
>>   provider uses, get instrumentation metadata at run time, and query events
>>   from channels and log files:
>>
>>   -  EventManifest Schema
>>   -  Event Schema
>>   -  Query Schema
>>   -  Windows Event Log Constants
>>   -  Windows Event Log Data Types
>>   -  Windows Event Log Enumerations
>>   -  Windows Event Log Functions
>>   -  Windows Event Log Structures
>>   -  Windows Event Log Tools
>>
>>And here's just the function page:
>>
>>   http://msdn.microsoft.com/en-us/library/windows/desktop/aa385784(v=vs.85).aspx
>>
>>Windows... the Rube Goldberg OS.
>
> Hey, man, they just want to get it to where users need only point and
> drool.  
>
> Think of the cost savings to companies, now able to hire pubeless
> n00bs like "Hadron" (has he figured-out paths, yet?) for their IT
> department.

turd, I know "paths" inside out. Which is WHY I know I'm correct. You
need flushing.

./configure  NOT configure IS the standard in the configure, make,
release cycle you clueless wanker.



-- 
"I have a BSEE.... Negative feedback has many benefits, but "maintaining stability" is not one of them. Just the opposite, in fact." 
The turdv/chrisv idiot and his pretend BSEE degree.
PLEASE VISIT OUR HALL OF LINUX IDIOTS
http://linuxidiots.blogspot.com/

[toc] | [prev] | [next] | [standalone]

#239807 — Re: Long Term Shithead: Bug #10 - whining about documentation

On Wed, 23 Apr 2014 05:59:47 -0400, Chris Ahlstrom wrote:

> TomB wrote this copyrighted missive and expects royalties:
> 
>> On 2014-04-22, the following emerged from the brain of DFS:
>>
>> 8<
>>
>>> * all messages logged on a date
>>> cat logfile | grep ^YYYY-MM-DD
>>>
>>> * first and last 25 messages on a date
>>> cat logfile | grep ^YYYY-MM-DD | head -n 25
>>> cat logfile | grep ^YYYY-MM-DD | tail -n 25
>>>
>>> * all messages related to gparted
>>> cat logfile | grep gparted
>>
>> Yes, /that's/ how it's done ;-)
> 
> Log viewer app?  How quaint.  Sounds like something Windows would use.
> 
> And then, instead of using stock system tools (e.g. as noted above), you end
> up with something like this:

Yawwnnnnn.....

You sound like one of those types who can't see the forest for the
trees.

[toc] | [prev] | [next] | [standalone]

#239819 — Re: Long Term Shithead: Bug #10 - whining about documentation

On 4/23/2014 3:59 AM, Chris Ahlstrom wrote:
> TomB wrote this copyrighted missive and expects royalties:
> 
>> On 2014-04-22, the following emerged from the brain of DFS:
>>
>> 8<
>>
>>> * all messages logged on a date
>>> cat logfile | grep ^YYYY-MM-DD
>>>
>>> * first and last 25 messages on a date
>>> cat logfile | grep ^YYYY-MM-DD | head -n 25
>>> cat logfile | grep ^YYYY-MM-DD | tail -n 25
>>>
>>> * all messages related to gparted
>>> cat logfile | grep gparted
>>
>> Yes, /that's/ how it's done ;-)
> 
> Log viewer app?  How quaint.  Sounds like something Windows would use.
> 
> And then, instead of using stock system tools (e.g. as noted above), you end
> up with something like this:
> 
>    http://msdn.microsoft.com/en-us/library/windows/desktop/aa385785(v=vs.85).aspx
> 
>    The following are the programming elements that you use to create an
>    instrumentation manifest, create resources from the manifest that your
>    provider uses, get instrumentation metadata at run time, and query events
>    from channels and log files:
> 
>    -  EventManifest Schema
>    -  Event Schema
>    -  Query Schema
>    -  Windows Event Log Constants
>    -  Windows Event Log Data Types
>    -  Windows Event Log Enumerations
>    -  Windows Event Log Functions
>    -  Windows Event Log Structures
>    -  Windows Event Log Tools
> 
> And here's just the function page:
> 
>    http://msdn.microsoft.com/en-us/library/windows/desktop/aa385784(v=vs.85).aspx
> 
> Windows... the Rube Goldberg OS.
> 
You mean that Linux doesn't utilize dmesg like Solaris does from the
console?   LOL!!!

[toc] | [prev] | [next] | [standalone]

#239874

On 04/23/2014 05:59 AM, Chris Ahlstrom wrote:
> TomB wrote this copyrighted missive and expects royalties:
>
>> On 2014-04-22, the following emerged from the brain of DFS:
>>
>> 8<
>>
>>> * all messages logged on a date cat logfile | grep ^YYYY-MM-DD
>>>
>>> * first and last 25 messages on a date cat logfile | grep
>>> ^YYYY-MM-DD | head -n 25 cat logfile | grep ^YYYY-MM-DD | tail -n
>>> 25
>>>
>>> * all messages related to gparted cat logfile | grep gparted
>>
>> Yes, /that's/ how it's done ;-)
>
> Log viewer app?  How quaint.  Sounds like something Windows would
> use.


It's a Gnome app for Linux.  Been around forever.  The one in Ubuntu is 
copyrighted by the FSF... you know them, don't you?  The giggly twerps 
who sit around and bitch about Microsoft while begging for an allowance.

Sound familiar?



> And then, instead of using stock system tools (e.g. as noted above),
> you end up with something like this:
>
> http://msdn.microsoft.com/en-us/library/windows/desktop/aa385785(v=vs.85).aspx
>
>
> The following are the programming elements that you use to create an
> instrumentation manifest, create resources from the manifest that
> your provider uses, get instrumentation metadata at run time, and
> query events from channels and log files:
>
> -  EventManifest Schema -  Event Schema -  Query Schema -  Windows
> Event Log Constants -  Windows Event Log Data Types -  Windows Event
> Log Enumerations -  Windows Event Log Functions -  Windows Event Log
> Structures -  Windows Event Log Tools
>
> And here's just the function page:
>
> http://msdn.microsoft.com/en-us/library/windows/desktop/aa385784(v=vs.85).aspx
>
>
>
> Windows... the Rube Goldberg OS.


Poor Creepy++

"Boo hoo!!! Windows Event Logging is too complex!!  I likes me the 
simpleton Linux way: an unstructured text log file I can process wif 
cat, awk, grep, and pipes!"

Problem with your girlie-man 'analysis' is Windows Event logging is
complex (to you) because it's well-designed and professional and 
sophisticated, as opposed to Linux event logging which is unstructured 
and hobbyist and amateurish.

In Linux, you can't even count on an event date/time being in a
consistent format: kern.log uses 'Apr 23 08:32:36', dpkg.log uses
'2014-04-17 01:21:23', and pm-suspend.log uses 'Wed Apr 23 08:32:37 EDT
2014'.  Some logs put the date first, others put it later in the event
line.  Some logs don't even have date info in them.

It's typical Linux slopware chaos.

Windows Event logging is FAR superior.  From the GUI Event Viewer, to 
custom log views, to the XML infrastructure of the log data, to the 
Event logging API and SDK, to the granularity of the Events and their 
properties, to the command line mgmt utility wevtutil, to the 
documentation, it absolutely puts Linux to shame.


Here Creepy++, I'll get you started on some CLI stuff:

list of logs (there are nearly 500 available)
# wevtutil el

list of event publishers
(apps, services, drivers that write to the event logs)
# wevtutil ep

info about an event publisher
# wevtutil gp Workstation

get status info about a log
# wevtutil gli System

export the log to a file
# wevtutil epl System  D:\my_system.log

query logs for events
(eg errors or warnings logged the last 2 hours)
# wevtutil qe System /q:"*[System[(Level=2 or Level=3) and
TimeCreated[timediff(@SystemTime)<=7200000]]]" /f:text /rd:True

command reference
http://technet.microsoft.com/en-us/library/cc732848.aspx

to open the Event Viewer
# eventvwr

Plus, you can use the Event Viewer to construct a sophisticated custom 
query, then cut and paste it and edit it for use in wevtutil or scripting.



Note: the above is what's known as a beatdown: me on you, and Windows on 
Linux.

[toc] | [prev] | [next] | [standalone]

#239877

On Wed, 23 Apr 2014 18:05:00 -0400, DFS wrote:

> On 04/23/2014 05:59 AM, Chris Ahlstrom wrote:
>> TomB wrote this copyrighted missive and expects royalties:
>>
>>> On 2014-04-22, the following emerged from the brain of DFS:
>>>
>>> 8<
>>>
>>>> * all messages logged on a date cat logfile | grep ^YYYY-MM-DD
>>>>
>>>> * first and last 25 messages on a date cat logfile | grep
>>>> ^YYYY-MM-DD | head -n 25 cat logfile | grep ^YYYY-MM-DD | tail -n
>>>> 25
>>>>
>>>> * all messages related to gparted cat logfile | grep gparted
>>>
>>> Yes, /that's/ how it's done ;-)
>>
>> Log viewer app?  How quaint.  Sounds like something Windows would
>> use.
> 
> 
> It's a Gnome app for Linux.  Been around forever.  The one in Ubuntu is 
> copyrighted by the FSF... you know them, don't you?  The giggly twerps 
> who sit around and bitch about Microsoft while begging for an allowance.
> 
> Sound familiar?
> 
> 
> 
>> And then, instead of using stock system tools (e.g. as noted above),
>> you end up with something like this:
>>
>> http://msdn.microsoft.com/en-us/library/windows/desktop/aa385785(v=vs.85).aspx
>>
>>
>> The following are the programming elements that you use to create an
>> instrumentation manifest, create resources from the manifest that
>> your provider uses, get instrumentation metadata at run time, and
>> query events from channels and log files:
>>
>> -  EventManifest Schema -  Event Schema -  Query Schema -  Windows
>> Event Log Constants -  Windows Event Log Data Types -  Windows Event
>> Log Enumerations -  Windows Event Log Functions -  Windows Event Log
>> Structures -  Windows Event Log Tools
>>
>> And here's just the function page:
>>
>> http://msdn.microsoft.com/en-us/library/windows/desktop/aa385784(v=vs.85).aspx
>>
>>
>>
>> Windows... the Rube Goldberg OS.
> 
> 
> Poor Creepy++
> 
> "Boo hoo!!! Windows Event Logging is too complex!!  I likes me the 
> simpleton Linux way: an unstructured text log file I can process wif 
> cat, awk, grep, and pipes!"
> 
> Problem with your girlie-man 'analysis' is Windows Event logging is
> complex (to you) because it's well-designed and professional and 
> sophisticated, as opposed to Linux event logging which is unstructured 
> and hobbyist and amateurish.
> 
> In Linux, you can't even count on an event date/time being in a
> consistent format: kern.log uses 'Apr 23 08:32:36', dpkg.log uses
> '2014-04-17 01:21:23', and pm-suspend.log uses 'Wed Apr 23 08:32:37 EDT
> 2014'.  Some logs put the date first, others put it later in the event
> line.  Some logs don't even have date info in them.
> 
> It's typical Linux slopware chaos.
> 
> Windows Event logging is FAR superior.  From the GUI Event Viewer, to 
> custom log views, to the XML infrastructure of the log data, to the 
> Event logging API and SDK, to the granularity of the Events and their 
> properties, to the command line mgmt utility wevtutil, to the 
> documentation, it absolutely puts Linux to shame.
> 
> 
> Here Creepy++, I'll get you started on some CLI stuff:
> 
> list of logs (there are nearly 500 available)
> # wevtutil el
> 
> list of event publishers
> (apps, services, drivers that write to the event logs)
> # wevtutil ep
> 
> info about an event publisher
> # wevtutil gp Workstation
> 
> get status info about a log
> # wevtutil gli System
> 
> export the log to a file
> # wevtutil epl System  D:\my_system.log
> 
> query logs for events
> (eg errors or warnings logged the last 2 hours)
> # wevtutil qe System /q:"*[System[(Level=2 or Level=3) and
> TimeCreated[timediff(@SystemTime)<=7200000]]]" /f:text /rd:True
> 
> command reference
> http://technet.microsoft.com/en-us/library/cc732848.aspx
> 
> to open the Event Viewer
> # eventvwr
> 
> Plus, you can use the Event Viewer to construct a sophisticated custom 
> query, then cut and paste it and edit it for use in wevtutil or scripting.
> 
> 
> 
> Note: the above is what's known as a beatdown: me on you, and Windows on 
> Linux.

The problem with incompetents like Creepy is that they run away after
their beat down.
And this one is a beauty BTW.
Good job DFS.

[toc] | [prev] | [next] | [standalone]

#239935

On 4/23/2014 6:12 PM,  flatfish+++ wrote:

> The problem with incompetents like Creepy is that they run away after
> their beat down.
> And this one is a beauty BTW.
> Good job DFS.


Thanks.

Creepy++ is a serious pissant.  20+ years of making a living off Windows 
by day, and he still whines about it at night from a position of ignorance.

[toc] | [prev] | [next] | [standalone]

#239968

DFS <nospam@dfs.com> writes:

> On 04/23/2014 05:59 AM, Chris Ahlstrom wrote:
>> TomB wrote this copyrighted missive and expects royalties:
>>
>>> On 2014-04-22, the following emerged from the brain of DFS:
>>>
>>> 8<
>>>
>>>> * all messages logged on a date cat logfile | grep ^YYYY-MM-DD
>>>>
>>>> * first and last 25 messages on a date cat logfile | grep
>>>> ^YYYY-MM-DD | head -n 25 cat logfile | grep ^YYYY-MM-DD | tail -n
>>>> 25
>>>>
>>>> * all messages related to gparted cat logfile | grep gparted
>>>
>>> Yes, /that's/ how it's done ;-)
>>
>> Log viewer app?  How quaint.  Sounds like something Windows would
>> use.
>
> It's a Gnome app for Linux.  Been around forever.  The one in Ubuntu is
> copyrighted by the FSF... you know them, don't you?  The giggly twerps who sit
> around and bitch about Microsoft while begging for an allowance.
>
> Sound familiar?
>
>> And then, instead of using stock system tools (e.g. as noted above),
>> you end up with something like this:
>>
>> http://msdn.microsoft.com/en-us/library/windows/desktop/aa385785(v=vs.85).aspx
>>
>>
>> The following are the programming elements that you use to create an
>> instrumentation manifest, create resources from the manifest that
>> your provider uses, get instrumentation metadata at run time, and
>> query events from channels and log files:
>>
>> -  EventManifest Schema -  Event Schema -  Query Schema -  Windows
>> Event Log Constants -  Windows Event Log Data Types -  Windows Event
>> Log Enumerations -  Windows Event Log Functions -  Windows Event Log
>> Structures -  Windows Event Log Tools
>>
>> And here's just the function page:
>>
>> http://msdn.microsoft.com/en-us/library/windows/desktop/aa385784(v=vs.85).aspx
>>
>>
>>
>> Windows... the Rube Goldberg OS.
>
> Poor Creepy++
>
> "Boo hoo!!! Windows Event Logging is too complex!!  I likes me the simpleton
> Linux way: an unstructured text log file I can process wif cat, awk, grep, and
> pipes!"
>
> Problem with your girlie-man 'analysis' is Windows Event logging is
> complex (to you) because it's well-designed and professional and sophisticated,
> as opposed to Linux event logging which is unstructured and hobbyist and
> amateurish.
>

The problem with arseholes like Ahlstrom is that they seem to thing a
well designed "front end" somehow paralyses other tools. He's so 1337
with his command line "grep". What a weenie.

-- 
"I have a BSEE.... Negative feedback has many benefits, but "maintaining stability" is not one of them. Just the opposite, in fact." 
The turdv/chrisv idiot and his pretend BSEE degree.
PLEASE VISIT OUR HALL OF LINUX IDIOTS
http://linuxidiots.blogspot.com/

[toc] | [prev] | [next] | [standalone]

#239964 — Re: Long Term Shithead: Bug #10 - whining about documentation

Chris Ahlstrom <OFeem1987@teleworm.us> writes:

> TomB wrote this copyrighted missive and expects royalties:
>
>> On 2014-04-22, the following emerged from the brain of DFS:
>>
>> 8<
>>
>>> * all messages logged on a date
>>> cat logfile | grep ^YYYY-MM-DD
>>>
>>> * first and last 25 messages on a date
>>> cat logfile | grep ^YYYY-MM-DD | head -n 25
>>> cat logfile | grep ^YYYY-MM-DD | tail -n 25
>>>
>>> * all messages related to gparted
>>> cat logfile | grep gparted
>>
>> Yes, /that's/ how it's done ;-)
>
> Log viewer app?  How quaint.  Sounds like something Windows would use.
>

Yes Creepy. Admins use them and often use wizards to set alarms for certain
conditions . You really are a fucking weenie.

-- 
"I have a BSEE.... Negative feedback has many benefits, but "maintaining stability" is not one of them. Just the opposite, in fact." 
The turdv/chrisv idiot and his pretend BSEE degree.
PLEASE VISIT OUR HALL OF LINUX IDIOTS
http://linuxidiots.blogspot.com/

[toc] | [prev] | [next] | [standalone]

#239811

On 04/23/2014 01:31 AM, TomB wrote:
> On 2014-04-22, the following emerged from the brain of DFS:
>
> 8<
>
>> * all messages logged on a date
>> cat logfile | grep ^YYYY-MM-DD
>>
>>
>> * first and last 25 messages on a date
>> cat logfile | grep ^YYYY-MM-DD | head -n 25
>> cat logfile | grep ^YYYY-MM-DD | tail -n 25
>>
>>
>> * all messages related to gparted
>> cat logfile | grep gparted
>
> Yes, /that's/ how it's done ;-)


Are you being sarcastic?

If so, I'll write an 8-line script to replace you... and add a 'Tame the 
cunt!' .sig that makes people think you're still on the job.

Don't think I won't do it...

[toc] | [prev] | [next] | [standalone]

#239890

On 2014-04-23, the following emerged from the brain of DFS:
> On 04/23/2014 01:31 AM, TomB wrote:
>> On 2014-04-22, the following emerged from the brain of DFS:
>>
>> 8<
>>
>>> * all messages logged on a date
>>> cat logfile | grep ^YYYY-MM-DD
>>>
>>>
>>> * first and last 25 messages on a date
>>> cat logfile | grep ^YYYY-MM-DD | head -n 25
>>> cat logfile | grep ^YYYY-MM-DD | tail -n 25
>>>
>>>
>>> * all messages related to gparted
>>> cat logfile | grep gparted
>>
>> Yes, /that's/ how it's done ;-)
>
>
> Are you being sarcastic?
>
> If so, I'll write an 8-line script to replace you... and add a 'Tame the 
> cunt!' .sig that makes people think you're still on the job.

A great quote from a great movie!

And a 8-script to replace me? A one-liner should do. Ask Hadron!

> Don't think I won't do it...

-- 
Don't you wish you had more energy... or less ambition?

[toc] | [prev] | [next] | [standalone]

#239748

On 4/22/14, 11:42 AM, in article lj6d75$seb$1@dont-email.me, "DFS"
<nospam@dfs.com> wrote:

> http://bayimg.com/EAniDAAFL
> 
> 
> The Help documentation refers to File and Filter and View menu items,
> but the log viewer app only has one menu item: System Log, and it
> doesn't contain File, Filter or View.
> 
> Same if you open the log viewer (gnome-system-log) as root.
> 
> 
> 
> "Whatever their problems is not the fault of Ubuntu"

Excellent work on finding these.


-- 
* Mint MATE: Trash, Panel, Menu:    <http://youtu.be/C0y74FIf7uE>
* Mint KDE bugs or Easter eggs?     <http://youtu.be/CU-whJQvtfA>
* Mint KDE working with folders:    <http://youtu.be/7C9nvniOoE0>
* Mint KDE creating files:          <http://youtu.be/N7-fZJaJUv8>
* Mint KDE help:                    <http://youtu.be/3ikizUd3sa8>
* Mint KDE general navigation:      <http://youtu.be/t9y14yZtQuI>
* Mint / LibreOffice:               <http://youtu.be/USU9iqppfto>
* Win 8 / Word 2013:                <http://youtu.be/z8gUL2TCcV4>
* Mavericks / Pages 5.1:            <http://youtu.be/D3BPWANQoIk>

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.advocacy

csiph-web