Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Re: SourceSafe

by mjeaton (Hermit)
on Sep 18, 2001 at 17:53 UTC ( #113123=note: print w/replies, xml ) Need Help??

in reply to Automating SourceSafe with Perl

A few years ago, I wrote a couple of Perl programs to automate our VB build process. I ended up using makefiles that simply used the commandline ss.exe to check-in, check-out files. I wrote a Perl program that would create the makefiles based on the contents of the VBP.
Another Perl program actually iterated through all the directories (based on a starting director) and looked for makefiles. When it found one, it would execute nmake.
The whole thing was very cool, cause it did logging, etc. Since this is my first post here, I'm not sure what I would need to do to post the code.

Replies are listed 'Best First'.
Re: Re: SourceSafe
by indiandownunder (Initiate) on Oct 14, 2003 at 20:30 UTC
    Apologies for "restarting" an old thread. I am really interested in the Perl code you mention and would appreciate having a look at it. Wonder if it would be possible for you to dig this up and send it to me. TIA

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://113123]
[oiskuu]: The useful bits that relate to your process can be found under /proc/self. What information are you thinking of? Tty name?
[tye]: I just daemonized and getlogin() still knew who I had been.
[tye]: perhaps loginuid ? Not that I concede that something not being in /proc means it is not useful.
[Corion]: tye: That's really interesting, but maybe it is because getlogin() returns the name, or the uid, so if that user has been replaced by another user with the same uid in the meantime, that's no problem to the system...
[davido]: or on ubuntu /var/run/utmp
[Corion]: Otherwise, I would imagine that a user with a process still alive would lock that information in memory.
[davido]: so last -f /var/run/utmp on ubuntu provides similar (though more verbose) info
[oiskuu]: glibc getlogin just does ttyname() and falls back on getutline(); it's not security related at all. (reminds me of sendmail and remote finger services of the naive early spam era)
[Corion]: But yes, "who started this process" is interesting information :)
[tye]: no, I really believe that "login user" was added as a fundamental bit of info about each process in order to enhance the usefulness of auditing

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (8)
As of 2017-06-23 19:36 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (554 votes). Check out past polls.