similar to: Questions on smbclient messaging

Thankyou for taking the time to read this ... We have large PC userbase and a not-so-large (but equally loud) Unix user base. We have a requirement to "PopUp" information windows on ALL our user's screens with an absolute minimum of manual intervention (ie type the message once and then forget it). We can manage the Unix X servers but can't seem to find a UNIX application that

I'm having a hell of a time mounting Samba shares under Linux. Both server and client are running kernel v 2.2.1x on otherwise RedHat v6.0 systems. The machine running the Samba (v2.0.5a) server is working great. Directories and printers are easily accessable from Win98 and OS/2. It's Linux as a SMB *client* that is giving me problems. I can easily mount shares from a command prompt

Hi, I have a linux (redhat 6.0) print server and I am running samba 2.0.3-8 serving win95 machines. I would like the print server to send a message to the win95 when a print job is completed. To do that, I run winpopup on win95. However, if win95 users close winpopup, they do not receive any message. Is there any more realiable method to communicate with win95 machines? I would appreciate any

Some of the files on my linux box have the character ':' in their name. Viewing them over the network via smb, samba seems to replace the ':' with a '~'. The real problem is that these files cannot be copied/moved at all (error messages appear). Has anyone else encountered this issue? And is there a fix or workaround? (please don't tell me I need to rename all my

I have looked around a lot and couldn't find anything on this. can some one please help? > I have RedHat Linux and have mounted shared drives from WINNT 4.0 SP4. > Samba version v2.0.5a. > > I am having this problem when we mount a shared winnt drive on linux. > the timestamps look all messed up. I am not sure if I did not setup it up > properly or what. Any help

Can someone please point me to an overview on how printing works with Samba v2.0.5a? As far as I can tell, there are 3 directories involved when printing to a Samba-shared printer on a Linux system: /tmp/ /var/spool/samba /var/spool/lpd/printername/ I was under the impression that incoming files were written to /tmp, then copied to the printer-specific directory, then printed. Obviously

Hi LLVM-Devs, I am in the process of updating our out-of-tree implementation from v5.0 to v6.0 RC3, and while it builds and mostly runs, I am having trouble with a small number of tests where the 'WorklistMap' in 'DAGCombiner::Run' never becomes empty. This is resulting in a runaway state of continuous heap allocation until the process exhausts all system memory. But I can't

Hi LLVM-Devs, When I try to configure LLVM v6.0 RC2 (SVN Rev #324869) on Windows (I haven't yet had a chance to try on Linux), I get a series of errors such as this: CMake Error at cmake/modules/AddLLVM.cmake:1333 (add_dependencies): The dependency target "(" of target "check-all" does not exist. Call Stack (most recent call first): CMakeLists.txt:937

Maybe it's caused by the space after the X86 argument? Can you try removing all the -D flags, and see if that works? Then add them one by one to see which is the culprit? -Dimitry > On 17 Feb 2018, at 23:11, Martin J. O'Riordan via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi LLVM-Devs, > > When I try to configure LLVM v6.0 RC2 (SVN Rev #324869) on Windows

Martin: I suspect this is an issue with post-DAG legalization store merging in the DAGCombiner. If you have a custom lowered type the DAGCombiner may end up merging a set of stores and immediately splitting them up in legalization. You should be able to disable this pass universally by overriding mergeStoresAfterLegalization() or conditionally for cases that shouldn't match with

We discovered what is happening. SDAGCombiner essentially looks at various combinations of nodes to do with vectors, and when it can, it creates a vector shuffle. The problem is, that our vector shuffle lowering builds new trees with vector element, or vector sub-vector insert sequences. The generic DAGCombiner, reconstructs these into a new shuffle, and so the loop continues - we reduce it,

Just wondering if there is a way to send a WinPopup message to a user (using username). I have had a look at smbclient but it appears to only allow sending messages to a computer name. Thanks in advance, Russell Kliese

From the smb.conf help document regarding the "message command" field:- >You could make this command send mail, or whatever else takes your fancy. >Please let us know of any really interesting ideas you have. First, my question:- Does Samba do anything in particular with the standard output of the program specified here? What would it take to have it WinPopUp-ed back to the

Hi, if I do the following: ssh -X localhost su - another_user xterm I get: X connection to ming:10.0 broken (explicit kill or server shutdown). Where what is really wanted was something like: Xlib: connection to ":0.0" refused by server Xlib: Client is not authorized to connect to Server xterm Xt error: Can't open display: :0.0 'tis easy to reproduce the bug, but the debug

Martin: It sounds like you are doing is more akin to shuffle selection than fusion and therefore it's a better fit for instruction selection than DAGCombining. Try movign it to <Target>ISelDAGToDAG's Select (or potentially PreprocessISelDAG). Th -Nirav On Tue, Mar 6, 2018 at 4:05 PM Martin J. O'Riordan <MartinO at theheart.ie> wrote: > We discovered what is

Hello all, $XAUTHORITY location has moved from under /tmp to ~/.Xauthority in 2.9p2. The commit message was: --- remove xauth-cookie-in-tmp handling. use default $XAUTHORITY, since we do already trust $HOME/.ssh you can use .ssh/sshrc and .ssh/environment if you want to customize the location of the xauth cookies --- The latter is true, but can only be enabled in per-user basis as far as I see.

Before I start I should say that I will pay $2000US to get the information or code I seek. I need code or protocol specs to be able to send winpopup messages. It cannot be done via mail slots because it has to work over the internet at large. If you type in "net send x.x.x.x hello" on any windows nt or xp machines it will send a winpopup using UDP ports 137 and then 135 (also 1031 and

Hello i am sending winpopup messages throught (smbclient -M) and it seem to work fine but i dont recieve anything at my w98 machines. For example, i do: ---------------------- jorge@tagoror:~> smbclient -M ALFA added interface ip=192.201.11.67 bcast=192.201.11.255 nmask=255.255.255.0 added interface ip=192.201.11.1 bcast=192.201.11.255 nmask=255.255.255.0 Got a positive name query response

Greetings- Perhaps slightly OT, but still involving the SMB/CIFS protocol: I am searching for an application which would allow a Linux client (Ubuntu) to send/receive WinPopup messages. The only one I have located thus far is LinPopup. However, it depends on the Samba (server) package. I do not want to deploy a bazillion Samba servers! TIA! -- Michael Lueck Lueck Data Systems

Hi there. how do I send a winpopup message to a machine knowing its IP only? I tryed witch 'smbclient -M ' but I need the netbios for that machine... -- Enrique Iglesias Rodriguez System Administrator http://www.intelideas.net Madrid, Spain -- CtrInt