| |
| |
| |
|
Page: 1 2 3 4 5
Comments:
<0> yea, it shows / being /dev/hdk2, and /c being /dev/sda1, proc, devpts, and usbfs
<1> hmm that's pretty odd heh
<0> i've spent a lot of time searching and the only thing i can find is that people run --recheck and it works for them
<2> does anyone have experience with the RealVNC X extension (libvnc.so)?
<2> it seems to work but I have no idea where to specify the p***word
<3> Demi-god_: type vnc, then hit tab a couple times
<1> doesn't make a lot of sense. if it sees it I'd think it would be fine. as I said, I've only seen sata drives with scsii designations, but who knows
<2> bash: vnc: command not found
<2> ah
<3> Demi-god_: What part of "then hit tab a couple times"....
<3> :)
<0> maybe it's because i have actual scsi drives in the system that it didn't default to scsi naming
<2> but
<2> what then?
<2> I already tried vncp***wd
<3> then look at the commands it gives you
<3> You ran that as the user you want to login as?
<1> blued: I don't know man. never run across this one before
<2> umm, maybe you have misunderstood
<2> I'm talking about an X server module
<3> and?
<2> that allows me to see what's going on on the real screen
<0> IdiotStic thanks for the effort
<3> okay, and?
<2> just like windows
<2> so how do I specify the p***word to that module
<3> ...vncp***word
<2> didn't work
<2> and I don't see why it would
<3> and I repeat... You ran that as the user you want to login as?
<4> i just installed suse and my sound isnt working, even on cds
<4> i went to alsamixer and unmuted everything
<2> login? the system might be in the login screen
<2> and that's what I expect to see through vnc when I connect
<5> hmm... is it just me or does Linux (using ext3) not log when a filesystem is full? Is this configurable? Has it always been this way?
<2> exactly what's happening on the real screen
<3> so figure out how to get vnc to use gdm
<2> huh?
<2> I'm *NOT* running a standalone vnc server, I know how THAT works
<2> I have no problem with that setup
<1> pooleb: if the filesystem is full I doubt it can log it anywhere :)
<2> what does this have to do with gdm?
<3> I've asked you a question twice, and you've ignored it
<5> It could log it remotely.
<2> vnc does not ask for a user name
<2> I ran vncp***wd as root
<3> good, now run it as the user who you want to login as
<0> you login as the user you want your vncserver to be ran as, and give it a commandline argument of a file containing the plaintext p***word you want to use
<2> blued, maybe you missed the line where I explained that I'm not running a standalone vnc server
<2> but an X server module
<3> Demi-god_: If you aren't going to listen, don't both asking a question
<2> alright, I have just one user account
<2> and I ran vncp***wd on that one
<0> running vncp***wd still creates a file in the userdir .vnc/ called p***wd that's encryped p***word
<0> your X module should then read this p***word just like the standalone serverr does
<2> how does it know which user's homedir to read it from?
<3> because you give it a friggen username
<2> where?
<3> ...
<0> because you are esupposed to be logged in as that user when you RUN vncp***wd
<2> "No p***word configured for VNC Auth"
<2> says vnc when I try connecting
<3> give it a username
<2> WHERE
<0> you login as the user, then you run vncp***wd
<3> in the client
<0> that's how you give the module the p***word
<2> there is no place to enter a user name in the client
<2> never has been
<0> whatever user the module is ran as (so whatever user X is ran as) is the user you are going to be logged in on
<2> the X server is running as root of course
<0> then you shall be logged in as root, type vncp***wd <file>
<2> as I already said, I did that
<2> but it didn't help
<0> check /root/.vnc
<0> do you see the file p***wd in there?
<2> the module is supposed to give me a view of displayy :0
<2> yes, it's there
<0> did you try reloading X after the file was created (so after you ran vncp***wd)?
<2> hm, no
<2> nope, same error
<0> i would be under the ***umption that the module would gett the p***word the same way the standalone server does. that's all i did when i ran mine
<2> yeah, I have experience with that setup without any problems whatsoever
<2> but this module thing is giving me a headache...no documentation anywhere
<2> and not even google can give me an answer
<0> is there a way to add options, like command line arguments, to the module when it's ran?
<2> Xorg.conf
<2> but I have no idea what to add
<2> since there's no docs
<0> then try adding -rfbauth /root/.vnc/p***wd
<6> has anyone setup secure nfs?
<6> any decent alteratives?
<2> I really don't think that p***word goes to any individual user's home dir
<2> Qwell was so obsessed with users and logins, but this setup has NOTHING to do with them
<0> well the p***word is different for every user that vnc is ran under, so i would ***ume it does
<0> and looking at the vncserver script it runs -rfbauth $vncUserDir/p***wd with the X server
<2> I'm NOT using the vncserver script
<0> i know, but chances are the module is setup similarly, since they both are realvnc
<0> and if you can give the module options like that, it would make sense that the option names and arguments would be the same.
<2> but I already proved it didn't work with $vncUserDir/p***wd
<2> maybe some other realvnc man pages will give a clue
<0> you only proved that the module didn't search there without any options telling it to
<3> Did you read any documentation about this?
<6> dry
<6> martini pls
<2> Qwell, I would have if there were any
<3> BS
<0> modules are often meant for designers, and so documentation is few and far between
<3> http://gentoo-wiki.com/HOWTO_Use_TightVNC_W/_JPEG_Compression_to_connect_to_existing_X_Sessions
<3> 2 seconds with google
<6> thats fast
<2> where does it tell me how to specify the p***word
<3> ...
<6> *starts the stop watch*
<0> do a search for "p***wd"
<2> ok this looks promising
<5> Okay, this problem is lame. Lets switch to "Why does Linux not log messages to syslog when its ext3 filesystem is full". ;-)
<0> my guess would be because the filesystem is full, so it can't write new data to it
<2> either that or you failed to mention something :)
<5> It should at least try. There are many cases where the filesystem that is full is not the filesystem where the logs are being written. Either due to /var being on a different partition or due to syslog being setup for remote logging.
<7> that's a syslog daemon issue
<5> Solaris, *BSD's, etc log... is there really no option to make Linux/ext3 do the same?
<7> some syslog daemons won't log so much that they overtake the proc or io, either.
<5> It is not a syslog issue. There are no syslog messages being sent.
<7> yes it is, because it doesn't happen with socklog or syslog-ng or metalog.
<2> the X vnc thingy worked..kinda
<2> crashed my X server
<5> You sure about that?
<7> i'm positive
<2> damn, it crashed the entire box
<5> Linux's syslogd does not write all messages? It is filtering out log lines sent to it before it outputs? WTF?
<7> if you're talking about /dev/log, it has nothing to do with the filesystem.
<7> syslogd is not linux's, it's whatever app you install to read from /dev/log
<5> I'm sure you can understand that I'm referring the default sys/klogd installed on 99.99% of the Linux distros.
<7> i believe that is what you're referring to, and it's a horrible log system, imo.
<7> i haven't used it in 6 or 7 years.
<6> secure nfs
<6> is it a pain in the ***?
<6> not much documentaiton on this
<7> secure nfs? kind of.
<6> sounds like it is
<7> the kerberos setup is the PITA.
<6> pita?
<7> we use sfs instead.
<6> pain in the ***
<6> got it
<7> it's faster than secure nfs, and much easier to set up.
<8> no, the bread
<6> i'll check it up
Return to
#linuxhelp
or
Go to some related
logs:
ddgirls passes
#slackware
#delphi
wintaks trial
#windowsxp
#3dsmax
#windowsxp
#computers
#flash
crankers the legend
|
|