Been working on getting my server setup. Besides it being haunted by ghosts. its going pretty good
Network Map
2 Likes
I really should show mine but its way too complex and whenever I go to make one it starts to span multiple pages makes my head hurt so I always end up putting it off lol
1 Like
kek. Mine is really simple but the ethernet cords running everywhere makes it feel super complex
1 Like
its not networking unless you have a rats nest of unintrusive Ethernet cables running everywhere lol
1 Like
Couple days ago did some more exploring around.
Otherwise pretty much been gaming and working out. Did go to a local comic book store though yesterday which was neat. How about you all?
1 Like
lel nothin, got a couple days off one of my jobs but might lose pay have to see i guess
yeah
thinking about maybe making a gtk wrapper for my media server(just the actual server part)
main advantaged easier to start, in that it will run itself then. but then might lose the ability to parse/do pipes and stuff with logging output, so might have to make new logging output options/might have to redo that stuff anyways not sure :x
whatchu think for logging functions and stuff?
@Dje4321
like just output to console, output to a log, mostly just for error messages, status update maybe
For the https://0cd.xyz site I just log all errors to console together with HTTP requests to file with logrotate on the logs directory to cycle through and compress the them on the server and has worked pretty good so far for me.
1 Like
currently just puts all the shit in console, and if wanted, could do pipes and whatever from there
but not sure how would work if i go to gtk, probably have to redo bunch/all the messages, so it prints to the screen, and the console but dunno yet lel
doesnt really do anything that useful other than that it would give you a window to look at to see the messages i guess
i would do what @Michael recommend but you could also be lazy and do this
./program.x86_64 | tee -a $(date +%y-%m-%d-%H-%M).log
Will copy stdout and place it in a timestamped file in the following format. Assuming your using bash.
YEAR-MONTH-DAY-HOUR-MINUTE.log
1 Like
well since the error is usually visually obvious, its just to tell you what happened making it not go,
like if list points to a file it cant find, different message, than if it just cant open the file
like if the file itself wasnt accessible, or the list, etc could be lazy and do like > output.txt
since we dont care if what happened the other times it has run so we can just overwrite
Today’s mind blowing discovery:
ATi’s fglrx was authored by S3 graphics.
1 Like
neat. Same driver my 2006 imac uses
also welcome back
1 Like
Also the tattoo outline was actually not bad at all but holy fuck the shading hurt lol. Worth it though.
3 Likes
1-2 needles vs 13 XD
2 Likes
and having to go the same areas like 4-6 times for the darkly shading parts that are blended into lighter shading.
1 Like