Re: [lopsa-tech] C coding
- "Tom Limoncelli" wrote: > I see this in code now and then: > 1<<16-1 Being just a system geek and not a professional programmer, I don't understand why one would use that notation instead of the more obvious variations of "0x8000"? I understand that the compiler, at compile time (not run time) will figure out that the programmer "meant" 0x8000 from that piece of code so the end result is the same but it seems that for documentation purposes it'd be more obvious to do it the other way. Am I missing something? Thanks for letting me ask. -- << MCT >> Michael C Tiernan http://www.linkedin.com/in/mtiernan Non Impediti Ratione Cogatationis ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
Re: [lopsa-tech] OpenSource Video Conferencing?
Does the openmeetings project have any value? http://code.google.com/p/openmeetings/ -- << MCT >> Michael C Tiernan http://www.linkedin.com/in/mtiernan Non Impediti Ratione Cogatationis ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
Re: [lopsa-tech] Kerberos principle question.
Thanks for your time Ben. - "Ben Poliakoff" wrote: > If you're dealing with an MIT KDC then you can simply "expire" the > kerberos principal (not the password), which keeps it from being > used. Very nice solution! Thank you! -- << MCT >> Michael C Tiernan http://www.linkedin.com/in/mtiernan signature.asc Description: Digital signature ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
[lopsa-tech] Kerberos principle question.
Hello all. Thanks in advance for your time. I've got a working Kerberos & LDAP configuration and I have users who've left the systems. Ignoring the good/bad aspects of the policy of deleting vs locking out users for a moment, I am wondering about the internal behavior of Kerberos. If Kerberos provides the authentication information for users (but is only coupled to LDAP via the user's name) then I *believe* that I can delete a user's principle to prohibit use of the account and then, when the appropriate authority tells me the user is allowed back in, I can just create a new principle for this user and all will be right with the world. The assumption is of course that the lock/unlock period is beyond the life-time of any tickets. The reason I'm pinging this list is I know I don't know enough about Kerberos to be 100% right and I also know that if I make a mistake doo-doo hits the oscillating air circulator. So I figured I'd take hat-in-hand and ask some more seasoned folks. Am I missing an elephant in the room? Thanks for your time and opinins. :) -- << MCT >> Michael C Tiernan http://www.linkedin.com/in/mtiernan ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
Re: [lopsa-tech] Ticketing system
- "Martin Markovski" wrote: > Looking for a ticketing system that is preferably open source. I used to use zentrack, I loved it, it was very easy to use and deploy. -- << MCT >> Michael C Tiernan http://www.linkedin.com/in/mtiernan ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
Re: [lopsa-tech] sar data - how to slice and dice?
- "Matt Lawrence" wrote: > I have a bunch of systems collecting sar data and I really would like > to > aggregate it up and present it graphically. Any recommendations for > existing open source tools I should use? I'm capable of writing my > own, > but that would probably be a waste of my time. > Look up 'sargraph', I've been using it for a while, it's quite handy. ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
Re: [lopsa-tech] Solaris vs other *NIX's (Was: Help with Kickstart policy)
On Wed, May 19, 2010 at 3:00 PM:
[...]
> Logging in to a Solaris system
> feels archaic when compared to Linux or other
[...]
One of the things that I really think our business could learn from is
how sparse a basic installation of Solaris is. Yes, there's lots of
arguments about different flavors of Linux, etc. but the thing that I
run into the most is the horrible cross connection of things in places
that make no real sense. The installation of a simple library can
result in a dozen or so other things being added to the pile. Things
that really make little sense.
I don't have a specific example at the moment and I have to qualifiy
it with statements like "Using {RedHat|CentOS|SciLinux} & Yum". The
thing that bit me the most recently was that to install a simple thing
(non-gui based tool) resulted in a half dozen X11 packages being
incorporated into the pile.
I know that sometimes this is needed, no argument but I think that the
Solaris crowd had a better no, wrong word a more innate and
fundamental understanding of the need for minimizing the places for
security mistakes.
If you create a system to be a stand-alone webserver on the fringe of
your company network, you don't want to install lots of things such as
compiler tools and/or GUI pieces and libraries. Solaris always seemed
to do this better.
Yea, they had a lot to learn too..
--
<< MCT >> Michael C Tiernan.
http://www.linkedin.com/in/mtiernan
___
Tech mailing list
Tech@lopsa.org
http://lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
Re: [lopsa-tech] Help with Kickstart policy
On Wed, May 19, 2010 at 3:00 PM: [...] > He has been running a one man show for quite a while. [...] He also > has a pattern of refusing to communicate, it makes it tough to figure out > what his point of view is. [...] This may be your "in". The boss I used to have always invoked the "HBAT" question. What would happen to things if "you" (the keeper of the knowledge) got Hit By A Truck? Some "glass half full" types might say it as "If you won the lottery" but the odds and end effects are the same. The mantra I tried to use (and did not do a glorious job at) was "There's always a next guy" and that for any given moment in time I *am* the next guy. So, if I want to be fair to the people I work with and the next person in my seat, I make it obvious by documenting everything, commenting code, and taking the easiest route for everything so that it's obvious what's being done. We all blame the "last guy" so let's give them as little to blame as possible. My job isn't to do what $BOSS decides needs to be done next but to make sure that the concept of "Business Continuance" is enforced and facilitated. It is this area of the business side of the process that may give you the opening you need to wedge yourself into. If you were to begin to make noises such as asking about radical concepts such as: Do we have a disaster plan? Do we have a security response plan? Do we have a "security has been comprimised" plan? Do we have a business continuance plan? Do we have the ability to pick up from ground zero and return to business in a reasonable time with a reasonable effort? You take down the confrontational approach causing dissent and you create a positive "Can do!" environtment which allows you to help management (who wants to prove their worth) develop business cases for spending more money, looking better, and doing things "the right way". A friend actually got his company to perform the tasks of putting on paper some of the steps and *COSTS* associated with the idea of starting a second datacenter up to handle their traffic if the first one was distroyed. They were STUNNED at the costs, time, etc., and actually began to listen to him when he suggested things "for the good of all." Just my mind dribbles. Good luck! -- << MCT >> Michael C Tiernan. http://www.linkedin.com/in/mtiernan ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
Re: [lopsa-tech] Help with Kickstart policy
I'm unable to address the problem you're presenting however, I would like to hear, once sorted out, how you approach the solution. Yea, we all know: Present Business Case, Implement Changes, Live life to the fullest I am just saying that I (and who knows how many others) may benefit from learning from someone more experienced in the process of putting together a business case argument about something like this. I know that when asked "Why?" about some of these things, my mind goes blank because I have never thought about the problem from the point of view of someone who doesn't think of it as obvious. Thanks for reading. :) -- << MCT >> Michael C Tiernan. http://www.linkedin.com/in/mtiernan ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
Re: [lopsa-tech] Tech Digest, Vol 54, Issue 15
On Fri, Apr 16, 2010 at 3:00 PM, wrote: > Today's Topics: > 1. Re: Tech Digest, Vol 54, Issue 7 (Michael Tiernan) > 2. Re: Server lifts (Skylar Thompson) > 3. Re: Tech Digest, Vol 54, Issue 7 (Allan West) My apologies to everyone for this ending up on the list. I was sure I'd checked. -- << MCT >> Michael C Tiernan. http://www.linkedin.com/in/mtiernan ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
Re: [lopsa-tech] Tech Digest, Vol 54, Issue 7
> Researchers at The University of Texas - Pan American are in the pilot survey > stage > of an academic research project concerning ethics and technology across > industries. > We are looking for individuals who work in a technology-related capacity to > validate > the data collection method. I *think* I'm willing to participate but I'd like to hear a bit more about the whole thing before I say yes. -- << MCT >> Michael C Tiernan. http://www.linkedin.com/in/mtiernan ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
Re: [lopsa-tech] ext2 on /tmp
- Original Message - Date: Sat, 20 Mar 2010 11:28:52 -0600 From: Yves Dorfsman Subject: [lopsa-tech] ext2 on /tmp To: tech@lopsa.org On Linux, if you split /tmp from the other filesystems, do you tend to make it ext2 since it's only for temporary files, and speed is more important? What could be a drawback of doing that? I've been doing it this way for a little while as an experiment but having heard some of the counter points here I may change that since the speeds are not as significant during operation as boot. ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
Re: [lopsa-tech] DNS functional testing
Another tool that saved me a lot of headaches is 'nslint' http://freshmeat.net/projects/nslint/ I used it with a reasonably clever makefile to keep all my DNS zones (that I inherited) from falling apart. (More than they already were.) -- << MCT >> Michael C Tiernan. http://www.linkedin.com/in/mtiernan ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
Re: [lopsa-tech] Swap sizing in Linux HPC cluster nodes.
First off, to everyone in this discussion, thank you for actually explaining things, it's very helpful to learn *why* certain things are done. > Date: Fri, 4 Sep 2009 21:37:01 -0400 > From: Edward Ned Harvey > Subject: Re: [lopsa-tech] Swap sizing in Linux HPC cluster nodes. > If you see the number of buffers has gone to zero [...] > Take a bunch of samples on live systems. If someone was to do samplings like this, what tools would you suggest? I am sure the usual tools, top, free, sar, etc. are useful but I'm just wondering if there's anything else that you prefer when doing this sort of data collection. -- << MCT >> Michael C Tiernan. http://www.linkedin.com/in/mtiernan ___ Tech mailing list Tech@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
